Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.7.0 01/04/16
- 2.5.2 → 2.6.5 no changes
- 2.5.1 08/28/15
- 2.5.0 07/27/15
- 2.4.10 no changes
- 2.4.9 09/04/15
- 2.4.1 → 2.4.8 no changes
- 2.4.0 04/30/15
- 2.3.9 09/04/15
- 2.3.1 → 2.3.8 no changes
- 2.3.0 02/05/15
- 2.2.0 → 2.2.2 no changes
- 2.1.4 12/17/14
- 2.0.1 → 2.1.3 no changes
- 2.0.0 05/28/14
- 1.9.1 → 1.9.5 no changes
- 1.9.0 02/14/14
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 11/08/13
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 04/07/13
- 1.8.0 → 188.8.131.52 no changes
- 184.108.40.206 10/17/12
- 220.127.116.11 → 18.104.22.168 no changes
- 1.7.12 08/20/12
gitignore - Specifies intentionally untracked files to ignore
$HOME/.config/git/ignore, $GIT_DIR/info/exclude, .gitignore
gitignore file specifies intentionally untracked files that
Git should ignore.
Files already tracked by Git are not affected; see the NOTES
below for details.
Each line in a
gitignore file specifies a pattern.
When deciding whether to ignore a path, Git normally checks
gitignore patterns from multiple sources, with the following
order of precedence, from highest to lowest (within one level of
precedence, the last matching pattern decides the outcome):
Patterns read from the command line for those commands that support them.
Patterns read from a
.gitignorefile in the same directory as the path, or in any parent directory, with patterns in the higher level files (up to the toplevel of the work tree) being overridden by those in lower level files down to the directory containing the file. These patterns match relative to the location of the
.gitignorefile. A project normally includes such
.gitignorefiles in its repository, containing patterns for files generated as part of the project build.
Patterns read from
Patterns read from the file specified by the configuration variable core.excludesFile.
Which file to place a pattern in depends on how the pattern is meant to be used.
Patterns which should be version-controlled and distributed to other repositories via clone (i.e., files that all developers will want to ignore) should go into a
Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary files that live inside the repository but are specific to one user’s workflow) should go into the
Patterns which a user wants Git to ignore in all situations (e.g., backup or temporary files generated by the user’s editor of choice) generally go into a file specified by
core.excludesFilein the user’s
~/.gitconfig. Its default value is $XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore is used instead.
The underlying Git plumbing tools, such as
git ls-files and git read-tree, read
gitignore patterns specified by command-line options, or from
files specified by command-line options. Higher-level Git
tools, such as git status and git add,
use patterns from the sources specified above.
A blank line matches no files, so it can serve as a separator for readability.
A line starting with # serves as a comment. Put a backslash ("
\") in front of the first hash for patterns that begin with a hash.
Trailing spaces are ignored unless they are quoted with backslash ("
An optional prefix "
!" which negates the pattern; any matching file excluded by a previous pattern will become included again. Put a backslash ("
\") in front of the first "
!" for patterns that begin with a literal "
!", for example, "
\!important!.txt". It is possible to re-include a file if a parent directory of that file is excluded if certain conditions are met. See section NOTES for detail.
If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory. In other words,
foo/will match a directory
fooand paths underneath it, but will not match a regular file or a symbolic link
foo(this is consistent with the way how pathspec works in general in Git).
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
.gitignorefile (relative to the toplevel of the work tree if not from a
Otherwise, Git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname. For example, "Documentation/*.html" matches "Documentation/git.html" but not "Documentation/ppc/ppc.html" or "tools/perf/Documentation/perf.html".
A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
Two consecutive asterisks ("
**") in patterns matched against
full pathname may have special meaning:
A leading "
**" followed by a slash means match in all directories. For example, "
**/foo" matches file or directory "
foo" anywhere, the same as pattern "
**/foo/bar" matches file or directory "
bar" anywhere that is directly under directory "
A trailing "
/**" matches everything inside. For example, "
abc/**" matches all files inside directory "
abc", relative to the location of the
.gitignorefile, with infinite depth.
A slash followed by two consecutive asterisks then a slash matches zero or more directories. For example, "
a/**/b" matches "
a/x/y/b" and so on.
Other consecutive asterisks are considered invalid.
The purpose of gitignore files is to ensure that certain files not tracked by Git remain untracked.
To stop tracking a file that is currently tracked, use git rm --cached.
To re-include files or directories when their parent directory is excluded, the following conditions must be met:
The rules to exclude a directory and re-include a subset back must be in the same .gitignore file.
The directory part in the re-include rules must be literal (i.e. no wildcards)
The rules to exclude the parent directory must not end with a trailing slash.
The rules to exclude the parent directory must have at least one slash.
$ 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 [...]
$ 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 ignoring
Example to exclude everything except a specific directory
/* - without the slash, the wildcard would also exclude
$ cat .gitignore # exclude everything except directory foo/bar /* !/foo /foo/* !/foo/bar
Part of the git suite