6 git-status - Show the working tree status
11 'git-status' <options>...
15 Displays paths that have differences between the index file and the
16 current HEAD commit, paths that have differences between the working
17 tree and the index file, and paths in the working tree that are not
18 tracked by git (and are not ignored by gitlink:gitignore[5]). The first
19 are what you _would_ commit by running `git commit`; the second and
20 third are what you _could_ commit by running `git add` before running
23 The command takes the same set of options as `git-commit`; it
24 shows what would be committed if the same options are given to
27 If there is no path that is different between the index file and
28 the current HEAD commit (i.e., there is nothing to commit by running
29 `git-commit`), the command exits with non-zero status.
34 The output from this command is designed to be used as a commit
35 template comment, and all the output lines are prefixed with '#'.
37 The paths mentioned in the output, unlike many other git commands, are
38 made relative to the current directory if you are working in a
39 subdirectory (this is on purpose, to help cutting and pasting). See
40 the status.relativePaths config option below.
46 The command honors `color.status` (or `status.color` -- they
47 mean the same thing and the latter is kept for backward
48 compatibility) and `color.status.<slot>` configuration variables
49 to colorize its output.
51 If the config variable `status.relativePaths` is set to false, then all
52 paths shown are relative to the repository root, not to the current
61 Written by Linus Torvalds <torvalds@osdl.org> and
62 Junio C Hamano <junkio@cox.net>.
66 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
70 Part of the gitlink:git[7] suite