Use git-update-index to temporarily ignore changes to files that are already under version control: git update-index –assume-unchanged <files> To undo that use: git update-index –no-assume-unchanged <files> Also have a look at the skip-worktree and no-skip-worktree options for update-index if you need this to persist past a git-reset
You can create your own .gitignore using git config –global core.excludesfile $HOME/.gitignore Then put your desired entries in that file.
This depends on the behavior of your shell. Git doesn’t do any work to determine how to expand these. In general, * matches any single file or folder: /a/*/z matches /a/b/z matches /a/c/z doesn’t match /a/b/c/z ** matches any string of folders: /a/**/z matches /a/b/z matches /a/b/c/z matches /a/b/c/d/e/f/g/h/i/z doesn’t match /a/b/c/z/d.pr0n Combine ** with … Read more
Just add a pattern to .gitignore .* !/.gitignore Edit: Added the .gitignore file itself (matters if it is not yet commited).
I do not think a Git commit can record an intention like “stop tracking this file, but do not delete it”. Enacting such an intention will require intervention outside Git in any repositories that merge (or rebase onto) a commit that deletes the file. Save a Copy, Apply Deletion, Restore Probably the easiest thing to … Read more
I’m guessing this folder has been checked into git before? Run git rm -r –cached <folder> and check again.
Your .gitignore is working, but it still tracks the files because they were already in the index. To stop this you have to do : git rm -r –cached .idea/ When you commit the .idea/ directory will be removed from your git repository and the following commits will ignore the .idea/ directory. PS: You could … Read more
Make sure that your .gitignore is in the root of the working directory, and in that directory run git status and copy the path to the file from the status output and paste it into the .gitignore. If that doesn’t work, then it’s likely that your file is already tracked by Git. You can confirm … Read more
EDIT: I’ve recently found git-filter-repo. It may be a better choice. Perhaps a good idea to investigate the rationale and filter-branch gotchas for yourself, but they wouldn’t have affected my use-case below. This method makes Git completely forget ignored files (past/present/future), but does not delete anything from working directory (even when re-pulled from remote). This … Read more
You can’t easily just ignore changes to particular lines of a file, I’m afraid, so you’re probably stuck with having a separate configuration file. Below I’ve listed two typical ways of dealing with this, and one slightly more exotic one: Have a sample configuration file in git Here, you would keep a file config.sample in … Read more