Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.tar.gz #5

Open
LoganDark opened this issue Oct 25, 2018 · 8 comments
Open

.tar.gz #5

LoganDark opened this issue Oct 25, 2018 · 8 comments

Comments

@LoganDark
Copy link

workspace.tar.gz should be the root of the repo. Apparently, it contains another Git repository. I think you should just push that repository here instead of a Git repository containing a file containing another Git repository.

@LanceB98
Copy link
Member

workspace.tar.gz contains Eclipse specific metadata that we want new users to have but should not be tracked by git. It does not contain a git repo.

@LoganDark
Copy link
Author

LoganDark commented Oct 25, 2018

Then why not make it one so you can have version control on the actual project files, rather than the entire archive?

Also, haven't you heard of .gitignore? You can use this method to provide starting metadata for new users (just instruct them to name eclipse.example to .eclipse or whatever Eclipse does)

Additionally, if you don't want to manually rename something, I think you can use this to preserve files but not track new changes.

skip-worktree is more than that: even where git knows that the file has been modified (or needs to be modified by a reset --hard or the like), it will pretend it has not been, using the version from the index instead. This persists until the index is discarded.

--skip-worktree is useful when you instruct git not to touch a specific file ever because developers should change it. For example, if the main repository upstream hosts some production-ready configuration files and you don’t want to accidentally commit changes to those files, --skip-worktree is exactly what you want.

@LanceB98
Copy link
Member

About two years ago, we were doing that, but we had the problem of eclipse changing those files with literally every commit, making merging a huge pain.

WIth regards to that method, that's essentially what we're already doing.

@LoganDark
Copy link
Author

LoganDark commented Oct 25, 2018

You ignored half of my comment.

Those files do not get changed with --skip-worktree. git DOES NOT TRACK THEM. I repeat, git commit does not change those files. Eclipse can change it all it wants, but git will not put the changes in the repository.

@LanceB98
Copy link
Member

sorry, I didn't see your edits (I posted a comment before refreshing). Give me a moment to look at them.

@LoganDark
Copy link
Author

Okay, ty :P

@LanceB98
Copy link
Member

Yeah, --skip-worktree sounds perfect for this use case.

@LoganDark
Copy link
Author

Alright, feel free to close this issue once you've switched over. :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants