Put this .gitignore into the folder, then git add .gitignore. * !.gitignore The * line tells git to ignore all files in the folder, but !.gitignore tells git to still include the .gitignore file. This way, your local repository and any other clones of the repository all get both the empty folder and the .gitignore … Read more
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.
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
git check-ignore Use git check-ignore command to debug your gitignore file (exclude files). For example: $ git check-ignore -v config.php .gitignore:2:src config.php The above output details about the matching pattern (if any) for each given pathname (including line). So maybe your file extension is not ignored, but the whole directory. The returned format is: <source> … 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.
I think that what you actually want to do is: aaa/* !aaa/ccc You’re telling it “don’t look in aaa” so it never even examines the path aaa/ccc. If you use the wildcard, it still reads the contents of aaa, then each entry matches the wildcard and is ignored, except aaa/ccc which gets put back in.
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
As Nathan said, cleaning up those files (un-tracking them) is the smart move. But if you must ignore tracked files (which is not the native Git way when it comes to ignoring files: Git only ignores non-tracked files), you can setup a process copying the content of files you want to ignore, and restoring on … Read more
Placement of .gitignore depends if the files need to be ignored for just one repo or for all your repos. For one repo, place it in the root of your repo. When you create a .gitignore file in an existing repo, or add files that were already in the repo, you have to make sure … Read more
I haven’t had need to try this myself, but from my reading of TFM it looks like a negated pattern would do what you want. You can override entries in .gitignore with later negated entries. Thus you could do something like: *.c !frob_*.c !custom.c To have it ignore all .c files except custom.c and anything … Read more