Git is probably already tracking the file. From the gitignore docs: To stop tracking a file that is currently tracked, use git rm –cached. Use this, replacing [project] and [username] with your info: git rm –cached [project].xcodeproj/project.xcworkspace/xcuserdata/[username].xcuserdatad/UserInterfaceState.xcuserstate git commit -m “Removed file that shouldn’t be tracked” Alternatively you can use the -a option to git … Read more
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
.gitignore only ignores files that are not part of the repository yet. If you already git added some files, their changes will still be tracked. To remove those files from your repository (but not from your file system) use git rm –cached on them.
git check-ignore -v filename See the man page for more details. Original answer follows: git does not currently provide anything like this. But after seeing your question I did some googling and found that back in 2009 this feature was requested and partially implemented. After reading the thread, I realised it would not be too … Read more
Second Update The FAQ is not available anymore. From the documentation of shrinkwrap: If you wish to lock down the specific bytes included in a package, for example to have 100% confidence in being able to reproduce a deployment or build, then you ought to check your dependencies into source control, or pursue some other … Read more
Use: *.dll #Exclude all dlls !foo.dll #Except for foo.dll From gitignore: An optional prefix ! which negates the pattern; any matching file excluded by a previous pattern will become included again. If a negated pattern matches, this will override lower precedence patterns sources.
Sure, I do exactly this from time to time using git update-index –assume-unchanged [<file> …] To undo and start tracking again (if you forgot what files were untracked, see this question): git update-index –no-assume-unchanged [<file> …] Relevant documentation: –[no-]assume-unchanged When this flag is specified, the object names recorded for the paths are not updated. Instead, … Read more
git rm –cached -r somedir Will stage the deletion of the directory, but doesn’t touch anything on disk. This works also for a file, like: git rm –cached somefile.ext Afterwards you may want to add somedir/ or somefile.ext to your .gitignore file so that git doesn’t try to add it back.
Put .gitignore in the working directory. It doesn’t work if you put it in the .git (repository) directory. $ ls -1d .git* .git .gitignore
This answer solved my problem: First of all, commit all pending changes. Then run this command: git rm -r –cached . This removes everything from the index, then just run: git add . Commit it: git commit -m “.gitignore is now working” Please be careful, when you push this to a repository and pull from … Read more