table of contents
other versions
- wheezy 1:1.7.10.4-1+wheezy3
- wheezy-backports 1:1.9.1-1~bpo70+2
- jessie 1:2.1.4-2.1+deb8u2
- jessie-backports 1:2.11.0-3~bpo8+1
- testing 1:2.11.0-3
- unstable 1:2.11.0-4
- experimental 1:2.13.1+next.20170610-1
GIT-STATUS(1) | Git Manual | GIT-STATUS(1) |
NAME¶
git-status - Show the working tree statusSYNOPSIS¶
git status [<options>...] [--] [<pathspec>...]
DESCRIPTION¶
Displays paths that have differences between the index file and the current HEAD commit, paths that have differences between the working tree and the index file, and paths in the working tree that are not tracked by git (and are not ignored by gitignore(5)). The first are what you would commit by running git commit; the second and third are what you could commit by running git add before running git commit.OPTIONS¶
-s, --shortGive the output in the short-format.
-b, --branch
Show the branch and tracking info even in
short-format.
--porcelain
Give the output in an easy-to-parse format for
scripts. This is similar to the short output, but will remain stable across
git versions and regardless of user configuration. See below for
details.
-u[<mode>], --untracked-files[=<mode>]
Show untracked files.
The mode parameter is optional (defaults to all), and is used to specify
the handling of untracked files; when -u is not used, the default is
normal, i.e. show untracked files and directories.
The possible options are:
--ignore-submodules[=<when>]
•
no - Show no untracked files
•
normal - Shows untracked files and directories
•
all - Also shows individual files in untracked directories.
The default can be changed using the status.showUntrackedFiles configuration
variable documented in git-config(1).
Ignore changes to submodules when looking for
changes. <when> can be either "none", "untracked",
"dirty" or "all", which is the default. Using
"none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded in
the superproject and can be used to override any settings of the ignore
option in git-config(1) or gitmodules(5). When
"untracked" is used submodules are not considered dirty when they
only contain untracked content (but they are still scanned for modified
content). Using "dirty" ignores all changes to the work tree of
submodules, only changes to the commits stored in the superproject are shown
(this was the behavior before 1.7.0). Using "all" hides all changes
to submodules (and suppresses the output of submodule summaries when the
config option status.submodulesummary is set).
--ignored
Show ignored files as well.
-z
Terminate entries with NUL, instead of LF.
This implies the --porcelain output format if no other format is given.
OUTPUT¶
The output from this command is designed to be used as a commit template comment, and all the output lines are prefixed with #. The default, long format, is designed to be human readable, verbose and descriptive. Its contents and format are subject to change at any time.Short Format¶
In the short-format, the status of each path is shown asXY PATH1 -> PATH2
•' ' = unmodified
•
M = modified
•
A = added
•
D = deleted
•
R = renamed
•
C = copied
•
U = updated but unmerged
X Y Meaning ------------------------------------------------- [MD] not updated M [ MD] updated in index A [ MD] added to index D [ M] deleted from index R [ MD] renamed in index C [ MD] copied in index [MARC] index and work tree matches [ MARC] M work tree changed since index [ MARC] D deleted in work tree ------------------------------------------------- D D unmerged, both deleted A U unmerged, added by us U D unmerged, deleted by them U A unmerged, added by them D U unmerged, deleted by us A A unmerged, both added U U unmerged, both modified ------------------------------------------------- ? ? untracked ! ! ignored -------------------------------------------------
Porcelain Format¶
The porcelain format is similar to the short format, but is guaranteed not to change in a backwards-incompatible way between git versions or based on user configuration. This makes it ideal for parsing by scripts. The description of the short format above also describes the porcelain format, with a few exceptions: 1.The user’s color.status configuration
is not respected; color will always be off.
2.The user’s status.relativePaths
configuration is not respected; paths shown will always be relative to the
repository root.
CONFIGURATION¶
The command honors color.status (or status.color — they mean the same thing and the latter is kept for backward compatibility) and color.status.<slot> configuration variables to colorize its output.SEE ALSO¶
gitignore(5)GIT¶
Part of the git(1) suite03/19/2016 | Git 1.7.10.4 |