1git-status(1) 2============= 3 4NAME 5---- 6git-status - Show the working tree status 7 8 9SYNOPSIS 10-------- 11'git-status' <options>... 12 13DESCRIPTION 14----------- 15Examines paths in the working tree that has changes unrecorded 16to the index file, and changes between the index file and the 17current HEAD commit. The former paths are what you _could_ 18commit by running 'git add' before running 'git 19commit', and the latter paths are what you _would_ commit by 20running 'git commit'. 21 22If there is no path that is different between the index file and 23the current HEAD commit, the command exits with non-zero 24status. 25 26The command takes the same set of options as `git-commit`; it 27shows what would be committed if the same options are given to 28`git-commit`. 29 30If any paths have been touched in the working tree (that is, 31their modification times have changed) but their contents and 32permissions are identical to those in the index file, the command 33updates the index file. Running `git-status` can thus speed up 34subsequent operations such as `git-diff` if the working tree 35contains many paths that have been touched but not modified. 36 37 38OUTPUT 39------ 40The output from this command is designed to be used as a commit 41template comments, and all the output lines are prefixed with '#'. 42 43The paths mentioned in the output, unlike many other git commands, are 44made relative to the current directory, if you are working in a 45subdirectory (this is on purpose, to help cutting and pasting). See 46the status.relativePaths config option below. 47 48 49CONFIGURATION 50------------- 51 52The command honors `color.status` (or `status.color` -- they 53mean the same thing and the latter is kept for backward 54compatibility) and `color.status.<slot>` configuration variables 55to colorize its output. 56 57If the config variable `status.relativePaths` is set to false, then all 58paths shown are relative to the repository root, not to the current 59directory. 60 61See Also 62-------- 63gitlink:gitignore[5] 64 65Author 66------ 67Written by Linus Torvalds <torvalds@osdl.org> and 68Junio C Hamano <junkio@cox.net>. 69 70Documentation 71-------------- 72Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>. 73 74GIT 75--- 76Part of the gitlink:git[7] suite