From the documentation: If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the .gitignore file (relative to the toplevel of the work tree if not from a .gitignore file). A leading slash matches the … Read more
See man git-add: -f, –force Allow adding otherwise ignored files. So run this git add –force my/ignore/file.foo
You can remove them from the repository manually: git rm –cached file1 file2 dir/file3 Or, if you have a lot of files: git rm –cached `git ls-files -i -c –exclude-from=.gitignore` But this doesn’t seem to work in Git Bash on Windows. It produces an error message. The following works better: git ls-files -i -c –exclude-from=.gitignore … Read more
PATTERN FORMAT A blank line matches no files, so it can serve as a separator for readability. A line starting with # serves as a comment. 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 … Read more
Normally yes, .gitignore is useful for everyone who wants to work with the repository. On occasion you’ll want to ignore more private things (maybe you often create LOG or something. In those cases you probably don’t want to force that on anyone else.
The official support page should answer your question. So in your .gitignore you might ignore the files ending with .iws, and the workspace.xml and tasks.xml files.
Have you tried wildcards? Solution/*/bin/Debug Solution/*/bin/Release With version 1.8.2 of git, you can also use the ** wildcard to match any level of subdirectories: **/bin/Debug/ **/bin/Release/
Yes, you may put comments in there. They however must start at the beginning of a line. cf. http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository#Ignoring-Files The rules for the patterns you can put in the .gitignore file are as follows: – Blank lines or lines starting with # are ignored. […] The comment character is #, example: # no .a files … Read more
The files/folder in your version control will not just delete themselves just because you added them to the .gitignore. They are already in the repository and you have to remove them. You can just do that with this: Remember to commit everything you’ve changed before you do this! git rm -rf –cached . git add … Read more
The rules in your .gitignore file only apply to untracked files. Since the files under that directory were already committed in your repository, you have to unstage them, create a commit, and push that to GitHub: git rm -r –cached some-directory git commit -m ‘Remove the now ignored directory “some-directory”‘ git push origin master You … Read more