I have a git repository that is ignoring image files as well as a few other files, but my .gitignore file only has it ignoring a config.php file. Is there some global ignore file somewhere that I can't seem to find? I have to specify files to add them now, and it's giving me this warning:
The following paths are ignored by one of your .gitignore files.
The contents of my ~/.gitconfig file are only my e-mail address.
git check-ignoreUse 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> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>
Or use the following command to print your .gitignore in user HOME and repository folder:
cat ~/.gitignore "$(git rev-parse --show-toplevel)"/.gitignore "$(git rev-parse --show-toplevel)"/.git/info/exclude
Alternatively use git add -f which allows adding otherwise ignored files.
See: man gitignore, man git-check-ignore for more details.
git check-ignore [options] pathname…
git check-ignore [options] --stdin
# Git is ignoring files that aren't in gitignore followed by the URL to this answer.
It might be good to know that your git configuration can contain a core.excludesfile which is a path to a file with additional patterns that are ignored. You can find out if you have such a configuration by running (in the problematic git repo):
git config core.excludesfile
If it prints a file path, look at the contents of that file for further information.
In my case I installed git via an old version of boxen which ignored the pattern 'Icon?' that in my case gave me the warning, mentioned in this question, for a folder icons (I'm on a case insensitive filesystem that's why Icon? matches icons).
Check these out:
Have you looked for other .gitignore files, as there can be many of them.
Also, look at REPO/.git/config to see if there is anything there.
Repo exclude Local per-repo rules can be added to the .git/info/exclude file in your repo. These rules are not committed with the repo so they are not shared with others. This method can be used for locally-generated files that you don’t expect other users to generate, like files created by your editor.
I had the same problem - a directory was being ignored by git with this error:
➭ git add app/views/admin/tags/
The following paths are ignored by one of your .gitignore files:
app/views/admin/tags
Use -f if you really want to add them.
fatal: no files added
I finally figured out my problem was a line in my ~/.gitignore_global:
TAGS
which was matching the path app/views/admin/tags. I fixed it by adding a leading slash to the global gitignore file
/TAGS
and git started tracking my directory again.
help directory which was being ignored. Luckily I found your answer quite quickly.
Commented
Sep 24, 2018 at 10:31
For me I accidentally had a wildcard in my ~/.gitignore_global file. Maybe check there?
Another thing to try: I had a directory B with its own .git repository nested under my project directory A (but not as a submodule). I made some changes to B, and wanted to make it into a bonafide submodule. I believe git A was automatically ignoring B because it contained its own repository (see Nested git repositories without submodules?). I renamed the B folder, and tried to clone it again as a submodule, and that was bringing me the misleading "ignored by .gitignore" error message. The solution was to delete .git out of B.
In my case it was the forward slash in my path causing the problem...
Not Work
/srv/bootstrap/
Work
srv/bootstrap/
.gitignore: skip-worktree and assume-unchangedA file may be ignored for the following reasons:
.gitignore (the combination of all of them)git update-index --skip-worktreegit update-index --assume-unchangedAdditionally, a file may be UNignored by if it is in .gitignore AND already staged in the index/cache.
To check for the enumerated cases above:
For the two cases of .gitignore excludes, compare the output of:
git check-ignore --verbose --non-matching --no-index file1 file2 file3git check-ignore --verbose --non-matching file1 file2 file3git ls-files file1 file2 file3 | grep -E '^S'
git ls-files file1 file2 file3 | grep -E '^[[:lower:]]'
The following aliases will cover all the cases listed above:
ignore = !"bash -c 'diff --unified=999999999 --color=always <(echo a; git check-ignore --verbose --non-matching --no-index . \"$@\") <(echo b; git check-ignore --verbose --non-matching . \"$@\")' - \"$@\" | tail -n+7; git hidden \"$@\" # Show ignore status of arguments. Files included by index are tagged with prepended '+'."
hidden = !"git ls-files -v -- \"$@\"| grep -E '^(S|[[:lower:]])' # S means update-index --skip-worktree, and lower first letter means --assume-unchanged."
The comment and final " are part of the line to be copied to your .gitconfig.
Usage:
git ignore file1 file2 file3
I was having the exact same problem as you. The only reply you got listed a few places to check, but none of them solved the problem for me, and from your comment I don't think for you either. I had no OTHER .gitignore files hiding lower in the directory tree; nothing in .git/config; nothing in .git/ingore/exclude
If you still have the problem, check this answer. It solved the issue for me
Basically, check for a ~/.gitignore file. Mine was called ~/.gitignore_global. I don't know when it was created (I certainly didn't make it), but I tried a ton of different git setup's when I first installed, so one of them must have put it there.
Hope his answer helps you as well!
Another reason for receiving this error message from git is when executing the git submodule add command while a previous git command has crashed and left the lock file (this can happen, for instance, when you use custom scripts which include git commands and you haven't noted the crash).
If you execute the command git commit instead, while none of the conditions have changed (git submodule add will keep yelling that your .gitignore files are to blame), you'll see another error report instead:
$ git commit -a
fatal: Unable to create '..../.git/index.lock': File exists.
If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.
and indeed deleting the lockfile:
rm .git/index.lock
resolves the issue. (This happens to git version 2.1.0.9736. It may be fixed in future git releases.)
Check you have permission to the folder. I have just run into this and it was because the folder was owned by the www-data user not the user I was logged in to the terminal as.
One more thing: if the directory you're in requires root access for writing or executing, make sure you're on the root user. I actually got a weird error where I was trying to add a submodule and git kept complaining that the path I was cloning into was being ignored by a git ignore file. Then I changed to root user, ran the submodule add again, and there was no problem.
Please also check ~/.gitignore and ~/.gitignore_global which might be created by some Git clients (e.g. Atlassian SourceTree on Mac OS X).
Make sure the .gitignore file is not ignoring itself.
A common mistake is adding a * rule to the .gitignore file to ignore every file in the current folder.
The solution to this is to add an exception to .gitignore:
*
!.gitignore
This way all files in the directory will be ignored, except .gitignore.
Check if you are on the right branch.
