2023-08-212023-06-012021-11-152021-08-162021-06-062019-08-112019-06-072018-12-092018-09-102019-12-062017-07-302017-05-052014-12-172014-12-17Agitignore file specifies intentionally untracked files thatGit should ignore.Files already tracked by Git are not affected; see the NOTESbelow for details.
Each line in agitignore file specifies a pattern.When deciding whether to ignore a path, Git normally checksgitignore patterns from multiple sources, with the followingorder of precedence, from highest to lowest (within one level ofprecedence, the last matching pattern decides the outcome):
Patterns read from the command line for those commands that supportthem.
Patterns read from a.gitignore file in the same directoryas the path, or in any parent directory (up to the top-level of the workingtree), with patterns in the higher level files being overridden by those inlower level files down to the directory containing the file. These patternsmatch relative to the location of the.gitignore file. A project normallyincludes such.gitignore files in its repository, containing patterns forfiles generated as part of the project build.
Patterns read from$GIT_DIR/info/exclude.
Patterns read from the file specified by the configurationvariablecore.excludesFile.
Which file to place a pattern in depends on how the pattern is meant tobe used.
Patterns which should be version-controlled and distributed toother repositories via clone (i.e., files that all developers will wantto ignore) should go into a.gitignore file.
Patterns which arespecific to a particular repository but which do not need to be sharedwith other related repositories (e.g., auxiliary files that live insidethe repository but are specific to one user’s workflow) should go intothe$GIT_DIR/info/exclude file.
Patterns which a user wants Git toignore in all situations (e.g., backup or temporary files generated bythe user’s editor of choice) generally go into a file specified bycore.excludesFile in the user’s~/.gitconfig. Its default value is$XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set orempty, $HOME/.config/git/ignore is used instead.
The underlying Git plumbing tools, such asgit ls-files andgit read-tree, readgitignore patterns specified by command-line options, or fromfiles specified by command-line options. Higher-level Gittools, such asgit status andgit add,use patterns from the sources specified above.
A blank line matches no files, so it can serve as a separatorfor readability.
A line starting with # serves as a comment.Put a backslash ("\") in front of the first hash for patternsthat begin with a hash.
Trailing spaces are ignored unless they are quoted with backslash("\").
An optional prefix "!" which negates the pattern; anymatching file excluded by a previous pattern will becomeincluded again. It is not possible to re-include a file if a parentdirectory of that file is excluded. Git doesn’t list excludeddirectories for performance reasons, so any patterns on containedfiles have no effect, no matter where they are defined.Put a backslash ("\") in front of the first "!" for patternsthat begin with a literal "!", for example, "\!important!.txt".
The slash "/" is used as the directory separator. Separators mayoccur at the beginning, middle or end of the.gitignore search pattern.
If there is a separator at the beginning or middle (or both) of thepattern, then the pattern is relative to the directory level of theparticular.gitignore file itself. Otherwise the pattern may alsomatch at any level below the.gitignore level.
If there is a separator at the end of the pattern then the patternwill only match directories, otherwise the pattern can match bothfiles and directories.
For example, a patterndoc/frotz/ matchesdoc/frotz directory,but nota/doc/frotz directory; howeverfrotz/ matchesfrotzanda/frotz that is a directory (all paths are relative fromthe.gitignore file).
An asterisk "*" matches anything except a slash.The character "?" matches any one character except "/".The range notation, e.g.[a-zA-Z], can be used to matchone of the characters in a range. See fnmatch(3) and theFNM_PATHNAME flag for a more detailed description.
Two consecutive asterisks ("**") in patterns matched againstfull pathname may have special meaning:
A leading "**" followed by a slash means match in alldirectories. For example, "**/foo" matches file or directory"foo" anywhere, the same as pattern "foo". "**/foo/bar"matches file or directory "bar" anywhere that is directlyunder directory "foo".
A trailing "/**" matches everything inside. For example,"abc/**" matches all files inside directory "abc", relativeto the location of the.gitignore file, with infinite depth.
A slash followed by two consecutive asterisks then a slashmatches zero or more directories. For example, "a/**/b"matches "a/b", "a/x/b", "a/x/y/b" and so on.
Other consecutive asterisks are considered regular asterisks andwill match according to the previous rules.
The optional configuration variablecore.excludesFile indicates a path to afile containing patterns of file names to exclude, similar to$GIT_DIR/info/exclude. Patterns in the exclude file are used in addition tothose in$GIT_DIR/info/exclude.
The purpose of gitignore files is to ensure that certain filesnot tracked by Git remain untracked.
To stop tracking a file that is currently tracked, usegit rm --cached to remove the file from the index. The filenamecan then be added to the.gitignore file to stop the file frombeing reintroduced in later commits.
Git does not follow symbolic links when accessing a.gitignore file inthe working tree. This keeps behavior consistent when the file isaccessed from the index or a tree versus from the filesystem.
The patternhello.* matches any file or directorywhose name begins withhello.. If one wants to restrictthis only to the directory and not in its subdirectories,one can prepend the pattern with a slash, i.e./hello.*;the pattern now matcheshello.txt,hello.c but nota/hello.java.
The patternfoo/ will match a directoryfoo andpaths underneath it, but will not match a regular fileor a symbolic linkfoo (this is consistent with theway how pathspec works in general in Git)
The patterndoc/frotz and/doc/frotz have the same effectin any.gitignore file. In other words, a leading slashis not relevant if there is already a middle slash inthe pattern.
The patternfoo/*, matchesfoo/test.json(a regular file),foo/bar (a directory), but it does not matchfoo/bar/hello.c (a regular file), as the asterisk in thepattern does not matchbar/hello.c which has a slash in it.
$ git status [...] # Untracked files: [...] # Documentation/foo.html # Documentation/gitignore.html # file.o # lib.a # src/internal.o [...] $ cat .git/info/exclude # ignore objects and archives, anywhere in the tree. *.[oa] $ cat Documentation/.gitignore # ignore generated html files, *.html # except foo.html which is maintained by hand !foo.html $ git status [...] # Untracked files: [...] # Documentation/foo.html [...]
Another example:
$ cat .gitignore vmlinux* $ ls arch/foo/kernel/vm* arch/foo/kernel/vmlinux.lds.S $ echo '!/vmlinux*' >arch/foo/kernel/.gitignore
The second .gitignore prevents Git from ignoringarch/foo/kernel/vmlinux.lds.S.
Example to exclude everything except a specific directoryfoo/bar(note the/* - without the slash, the wildcard would also excludeeverything withinfoo/bar):
$ cat .gitignore # exclude everything except directory foo/bar /* !/foo /foo/* !/foo/bar
Part of thegit[1] suite