| blob | 5b7b9bc69f5eaffbd76a55dd761ed38a01e93bb7 |
1 '\" t
2 .\" Title: git-status
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
5 .\" Date: 2024-10-04
6 .\" Manual: Git Manual
7 .\" Source: Git 2.47.0.rc1.33.g90fe3800b9
8 .\" Language: English
9 .\"
10 .TH "GIT\-STATUS" "1" "2024-10-04" "Git 2\&.47\&.0\&.rc1\&.33\&.g9" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 .ie \n(.g .ds Aq \(aq
19 .el .ds Aq '
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
24 .nh
25 .\" disable justification (adjust text to left margin only)
26 .ad l
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
30 .SH "NAME"
31 git-status \- Show the working tree status
32 .SH "SYNOPSIS"
33 .sp
34 .nf
35 \fIgit status\fR [<options>] [\-\-] [<pathspec>\&...\:]
36 .fi
37 .SH "DESCRIPTION"
38 .sp
39 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 \fBgitignore\fR(5))\&. The first are what you \fIwould\fR commit by running \fBgit commit\fR; the second and third are what you \fIcould\fR commit by running \fIgit add\fR before running \fBgit commit\fR\&.
40 .SH "OPTIONS"
41 .PP
42 \-s, \-\-short
43 .RS 4
44 Give the output in the short\-format\&.
45 .RE
46 .PP
47 \-b, \-\-branch
48 .RS 4
49 Show the branch and tracking info even in short\-format\&.
50 .RE
51 .PP
52 \-\-show\-stash
53 .RS 4
54 Show the number of entries currently stashed away\&.
55 .RE
56 .PP
57 \-\-porcelain[=<version>]
58 .RS 4
59 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\&.
60 .sp
61 The version parameter is used to specify the format version\&. This is optional and defaults to the original version
62 \fIv1\fR
63 format\&.
64 .RE
65 .PP
66 \-\-long
67 .RS 4
68 Give the output in the long\-format\&. This is the default\&.
69 .RE
70 .PP
71 \-v, \-\-verbose
72 .RS 4
73 In addition to the names of files that have been changed, also show the textual changes that are staged to be committed (i\&.e\&., like the output of
74 \fBgit diff \-\-cached\fR)\&. If
75 \fB\-v\fR
76 is specified twice, then also show the changes in the working tree that have not yet been staged (i\&.e\&., like the output of
77 \fBgit diff\fR)\&.
78 .RE
79 .PP
80 \-u[<mode>], \-\-untracked\-files[=<mode>]
81 .RS 4
82 Show untracked files\&.
83 .sp
84 The mode parameter is used to specify the handling of untracked files\&. It is optional: it defaults to
85 \fIall\fR, and if specified, it must be stuck to the option (e\&.g\&.
86 \fB\-uno\fR, but not
87 \fB\-u no\fR)\&.
88 .sp
89 The possible options are:
90 .sp
91 .RS 4
92 .ie n \{\
93 \h'-04'\(bu\h'+03'\c
94 .\}
95 .el \{\
96 .sp -1
97 .IP \(bu 2.3
98 .\}
99 \fIno\fR
100 \- Show no untracked files\&.
101 .RE
102 .sp
103 .RS 4
104 .ie n \{\
105 \h'-04'\(bu\h'+03'\c
106 .\}
107 .el \{\
108 .sp -1
109 .IP \(bu 2.3
110 .\}
111 \fInormal\fR
112 \- Shows untracked files and directories\&.
113 .RE
114 .sp
115 .RS 4
116 .ie n \{\
117 \h'-04'\(bu\h'+03'\c
118 .\}
119 .el \{\
120 .sp -1
121 .IP \(bu 2.3
122 .\}
123 \fIall\fR
124 \- Also shows individual files in untracked directories\&.
125 .RE
126 .sp
127 When
128 \fB\-u\fR
129 option is not used, untracked files and directories are shown (i\&.e\&. the same as specifying
130 \fBnormal\fR), to help you avoid forgetting to add newly created files\&. Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree\&. Consider enabling untracked cache and split index if supported (see
131 \fBgit update\-index \-\-untracked\-cache\fR
132 and
133 \fBgit update\-index \-\-split\-index\fR), Otherwise you can use
134 \fBno\fR
135 to have
136 \fBgit status\fR
137 return more quickly without showing untracked files\&. All usual spellings for Boolean value
138 \fBtrue\fR
139 are taken as
140 \fBnormal\fR
141 and
142 \fBfalse\fR
143 as
144 \fBno\fR\&.
145 .sp
146 The default can be changed using the status\&.showUntrackedFiles configuration variable documented in
147 \fBgit-config\fR(1)\&.
148 .RE
149 .PP
150 \-\-ignore\-submodules[=<when>]
151 .RS 4
152 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
153 \fIignore\fR
154 option in
155 \fBgit-config\fR(1)
156 or
157 \fBgitmodules\fR(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
158 \fBstatus\&.submoduleSummary\fR
159 is set)\&.
160 .RE
161 .PP
162 \-\-ignored[=<mode>]
163 .RS 4
164 Show ignored files as well\&.
165 .sp
166 The mode parameter is used to specify the handling of ignored files\&. It is optional: it defaults to
167 \fItraditional\fR\&.
168 .sp
169 The possible options are:
170 .sp
171 .RS 4
172 .ie n \{\
173 \h'-04'\(bu\h'+03'\c
174 .\}
175 .el \{\
176 .sp -1
177 .IP \(bu 2.3
178 .\}
179 \fItraditional\fR
180 \- Shows ignored files and directories, unless \-\-untracked\-files=all is specified, in which case individual files in ignored directories are displayed\&.
181 .RE
182 .sp
183 .RS 4
184 .ie n \{\
185 \h'-04'\(bu\h'+03'\c
186 .\}
187 .el \{\
188 .sp -1
189 .IP \(bu 2.3
190 .\}
191 \fIno\fR
192 \- Show no ignored files\&.
193 .RE
194 .sp
195 .RS 4
196 .ie n \{\
197 \h'-04'\(bu\h'+03'\c
198 .\}
199 .el \{\
200 .sp -1
201 .IP \(bu 2.3
202 .\}
203 \fImatching\fR
204 \- Shows ignored files and directories matching an ignore pattern\&.
205 .RE
206 .sp
207 When
208 \fImatching\fR
209 mode is specified, paths that explicitly match an ignored pattern are shown\&. If a directory matches an ignore pattern, then it is shown, but not paths contained in the ignored directory\&. If a directory does not match an ignore pattern, but all contents are ignored, then the directory is not shown, but all contents are shown\&.
210 .RE
211 .PP
212 \-z
213 .RS 4
214 Terminate entries with NUL, instead of LF\&. This implies the
215 \fB\-\-porcelain=v1\fR
216 output format if no other format is given\&.
217 .RE
218 .PP
219 \-\-column[=<options>], \-\-no\-column
220 .RS 4
221 Display untracked files in columns\&. See configuration variable
222 \fBcolumn\&.status\fR
223 for option syntax\&.
224 \fB\-\-column\fR
225 and
226 \fB\-\-no\-column\fR
227 without options are equivalent to
228 \fIalways\fR
229 and
230 \fInever\fR
231 respectively\&.
232 .RE
233 .PP
234 \-\-ahead\-behind, \-\-no\-ahead\-behind
235 .RS 4
236 Display or do not display detailed ahead/behind counts for the branch relative to its upstream branch\&. Defaults to true\&.
237 .RE
238 .PP
239 \-\-renames, \-\-no\-renames
240 .RS 4
241 Turn on/off rename detection regardless of user configuration\&. See also
242 \fBgit-diff\fR(1)
243 \fB\-\-no\-renames\fR\&.
244 .RE
245 .PP
246 \-\-find\-renames[=<n>]
247 .RS 4
248 Turn on rename detection, optionally setting the similarity threshold\&. See also
249 \fBgit-diff\fR(1)
250 \fB\-\-find\-renames\fR\&.
251 .RE
252 .PP
253 <pathspec>\&...\:
254 .RS 4
255 See the
256 \fIpathspec\fR
257 entry in
258 \fBgitglossary\fR(7)\&.
259 .RE
260 .SH "OUTPUT"
261 .sp
262 The output from this command is designed to be used as a commit template comment\&. The default, long format, is designed to be human readable, verbose and descriptive\&. Its contents and format are subject to change at any time\&.
263 .sp
264 The paths mentioned in the output, unlike many other Git commands, are made relative to the current directory if you are working in a subdirectory (this is on purpose, to help cutting and pasting)\&. See the status\&.relativePaths config option below\&.
265 .SS "Short Format"
266 .sp
267 In the short\-format, the status of each path is shown as one of these forms
268 .sp
269 .if n \{\
270 .RS 4
271 .\}
272 .nf
273 XY PATH
274 XY ORIG_PATH \-> PATH
275 .fi
276 .if n \{\
277 .RE
278 .\}
279 .sp
280 where \fBORIG_PATH\fR is where the renamed/copied contents came from\&. \fBORIG_PATH\fR is only shown when the entry is renamed or copied\&. The \fBXY\fR is a two\-letter status code\&.
281 .sp
282 The fields (including the \fB\->\fR) are separated from each other by a single space\&. If a filename contains whitespace or other nonprintable characters, that field will be quoted in the manner of a C string literal: surrounded by ASCII double quote (34) characters, and with interior special characters backslash\-escaped\&.
283 .sp
284 There are three different types of states that are shown using this format, and each one uses the \fBXY\fR syntax differently:
285 .sp
286 .RS 4
287 .ie n \{\
288 \h'-04'\(bu\h'+03'\c
289 .\}
290 .el \{\
291 .sp -1
292 .IP \(bu 2.3
293 .\}
294 When a merge is occurring and the merge was successful, or outside of a merge situation,
295 \fBX\fR
296 shows the status of the index and
297 \fBY\fR
298 shows the status of the working tree\&.
299 .RE
300 .sp
301 .RS 4
302 .ie n \{\
303 \h'-04'\(bu\h'+03'\c
304 .\}
305 .el \{\
306 .sp -1
307 .IP \(bu 2.3
308 .\}
309 When a merge conflict has occurred and has not yet been resolved,
310 \fBX\fR
311 and
312 \fBY\fR
313 show the state introduced by each head of the merge, relative to the common ancestor\&. These paths are said to be
314 \fIunmerged\fR\&.
315 .RE
316 .sp
317 .RS 4
318 .ie n \{\
319 \h'-04'\(bu\h'+03'\c
320 .\}
321 .el \{\
322 .sp -1
323 .IP \(bu 2.3
324 .\}
325 When a path is untracked,
326 \fBX\fR
327 and
328 \fBY\fR
329 are always the same, since they are unknown to the index\&.
330 \fB??\fR
331 is used for untracked paths\&. Ignored files are not listed unless
332 \fB\-\-ignored\fR
333 is used; if it is, ignored files are indicated by
334 \fB!!\fR\&.
335 .RE
336 .sp
337 Note that the term \fImerge\fR here also includes rebases using the default \fB\-\-merge\fR strategy, cherry\-picks, and anything else using the merge machinery\&.
338 .sp
339 In the following table, these three classes are shown in separate sections, and these characters are used for \fBX\fR and \fBY\fR fields for the first two sections that show tracked paths:
340 .sp
341 .RS 4
342 .ie n \{\
343 \h'-04'\(bu\h'+03'\c
344 .\}
345 .el \{\
346 .sp -1
347 .IP \(bu 2.3
348 .\}
349 \*(Aq \*(Aq = unmodified
350 .RE
351 .sp
352 .RS 4
353 .ie n \{\
354 \h'-04'\(bu\h'+03'\c
355 .\}
356 .el \{\
357 .sp -1
358 .IP \(bu 2.3
359 .\}
360 \fIM\fR
361 = modified
362 .RE
363 .sp
364 .RS 4
365 .ie n \{\
366 \h'-04'\(bu\h'+03'\c
367 .\}
368 .el \{\
369 .sp -1
370 .IP \(bu 2.3
371 .\}
372 \fIT\fR
373 = file type changed (regular file, symbolic link or submodule)
374 .RE
375 .sp
376 .RS 4
377 .ie n \{\
378 \h'-04'\(bu\h'+03'\c
379 .\}
380 .el \{\
381 .sp -1
382 .IP \(bu 2.3
383 .\}
384 \fIA\fR
385 = added
386 .RE
387 .sp
388 .RS 4
389 .ie n \{\
390 \h'-04'\(bu\h'+03'\c
391 .\}
392 .el \{\
393 .sp -1
394 .IP \(bu 2.3
395 .\}
396 \fID\fR
397 = deleted
398 .RE
399 .sp
400 .RS 4
401 .ie n \{\
402 \h'-04'\(bu\h'+03'\c
403 .\}
404 .el \{\
405 .sp -1
406 .IP \(bu 2.3
407 .\}
408 \fIR\fR
409 = renamed
410 .RE
411 .sp
412 .RS 4
413 .ie n \{\
414 \h'-04'\(bu\h'+03'\c
415 .\}
416 .el \{\
417 .sp -1
418 .IP \(bu 2.3
419 .\}
420 \fIC\fR
421 = copied (if config option status\&.renames is set to "copies")
422 .RE
423 .sp
424 .RS 4
425 .ie n \{\
426 \h'-04'\(bu\h'+03'\c
427 .\}
428 .el \{\
429 .sp -1
430 .IP \(bu 2.3
431 .\}
432 \fIU\fR
433 = updated but unmerged
434 .RE
435 .sp
436 .if n \{\
437 .RS 4
438 .\}
439 .nf
440 X Y Meaning
441 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
442 [AMD] not updated
443 M [ MTD] updated in index
444 T [ MTD] type changed in index
445 A [ MTD] added to index
446 D deleted from index
447 R [ MTD] renamed in index
448 C [ MTD] copied in index
449 [MTARC] index and work tree matches
450 [ MTARC] M work tree changed since index
451 [ MTARC] T type changed in work tree since index
452 [ MTARC] D deleted in work tree
453 R renamed in work tree
454 C copied in work tree
455 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
456 D D unmerged, both deleted
457 A U unmerged, added by us
458 U D unmerged, deleted by them
459 U A unmerged, added by them
460 D U unmerged, deleted by us
461 A A unmerged, both added
462 U U unmerged, both modified
463 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
464 ? ? untracked
465 ! ! ignored
466 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
467 .fi
468 .if n \{\
469 .RE
470 .\}
471 .sp
472 Submodules have more state and instead report
473 .sp
474 .RS 4
475 .ie n \{\
476 \h'-04'\(bu\h'+03'\c
477 .\}
478 .el \{\
479 .sp -1
480 .IP \(bu 2.3
481 .\}
482 \fIM\fR
483 = the submodule has a different HEAD than recorded in the index
484 .RE
485 .sp
486 .RS 4
487 .ie n \{\
488 \h'-04'\(bu\h'+03'\c
489 .\}
490 .el \{\
491 .sp -1
492 .IP \(bu 2.3
493 .\}
494 \fIm\fR
495 = the submodule has modified content
496 .RE
497 .sp
498 .RS 4
499 .ie n \{\
500 \h'-04'\(bu\h'+03'\c
501 .\}
502 .el \{\
503 .sp -1
504 .IP \(bu 2.3
505 .\}
506 \fI?\fR
507 = the submodule has untracked files
508 .RE
509 .sp
510 This is since modified content or untracked files in a submodule cannot be added via \fBgit add\fR in the superproject to prepare a commit\&.
511 .sp
512 \fIm\fR and \fI?\fR are applied recursively\&. For example if a nested submodule in a submodule contains an untracked file, this is reported as \fI?\fR as well\&.
513 .sp
514 If \-b is used the short\-format status is preceded by a line
515 .sp
516 .if n \{\
517 .RS 4
518 .\}
519 .nf
520 ## branchname tracking info
521 .fi
522 .if n \{\
523 .RE
524 .\}
525 .SS "Porcelain Format Version 1"
526 .sp
527 Version 1 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:
528 .sp
529 .RS 4
530 .ie n \{\
531 \h'-04' 1.\h'+01'\c
532 .\}
533 .el \{\
534 .sp -1
535 .IP " 1." 4.2
536 .\}
537 The user\(cqs color\&.status configuration is not respected; color will always be off\&.
538 .RE
539 .sp
540 .RS 4
541 .ie n \{\
542 \h'-04' 2.\h'+01'\c
543 .\}
544 .el \{\
545 .sp -1
546 .IP " 2." 4.2
547 .\}
548 The user\(cqs status\&.relativePaths configuration is not respected; paths shown will always be relative to the repository root\&.
549 .RE
550 .sp
551 There is also an alternate \-z format recommended for machine parsing\&. In that format, the status field is the same, but some other things change\&. First, the \fI\->\fR is omitted from rename entries and the field order is reversed (e\&.g \fIfrom \-> to\fR becomes \fIto from\fR)\&. Second, a NUL (ASCII 0) follows each filename, replacing space as a field separator and the terminating newline (but a space still separates the status field from the first filename)\&. Third, filenames containing special characters are not specially formatted; no quoting or backslash\-escaping is performed\&.
552 .sp
553 Any submodule changes are reported as modified \fBM\fR instead of \fBm\fR or single \fB?\fR\&.
554 .SS "Porcelain Format Version 2"
555 .sp
556 Version 2 format adds more detailed information about the state of the worktree and changed items\&. Version 2 also defines an extensible set of easy to parse optional headers\&.
557 .sp
558 Header lines start with "#" and are added in response to specific command line arguments\&. Parsers should ignore headers they don\(cqt recognize\&.
559 .sp
560 .it 1 an-trap
561 .nr an-no-space-flag 1
562 .nr an-break-flag 1
563 .br
564 .ps +1
565 \fBBranch Headers\fR
566 .RS 4
567 .sp
568 If \fB\-\-branch\fR is given, a series of header lines are printed with information about the current branch\&.
569 .sp
570 .if n \{\
571 .RS 4
572 .\}
573 .nf
574 Line Notes
575 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
576 # branch\&.oid <commit> | (initial) Current commit\&.
577 # branch\&.head <branch> | (detached) Current branch\&.
578 # branch\&.upstream <upstream\-branch> If upstream is set\&.
579 # branch\&.ab +<ahead> \-<behind> If upstream is set and
580 the commit is present\&.
581 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
582 .fi
583 .if n \{\
584 .RE
585 .\}
586 .RE
587 .sp
588 .it 1 an-trap
589 .nr an-no-space-flag 1
590 .nr an-break-flag 1
591 .br
592 .ps +1
593 \fBStash Information\fR
594 .RS 4
595 .sp
596 If \fB\-\-show\-stash\fR is given, one line is printed showing the number of stash entries if non\-zero:
597 .sp
598 .if n \{\
599 .RS 4
600 .\}
601 .nf
602 # stash <N>
603 .fi
604 .if n \{\
605 .RE
606 .\}
607 .RE
608 .sp
609 .it 1 an-trap
610 .nr an-no-space-flag 1
611 .nr an-break-flag 1
612 .br
613 .ps +1
614 \fBChanged Tracked Entries\fR
615 .RS 4
616 .sp
617 Following the headers, a series of lines are printed for tracked entries\&. One of three different line formats may be used to describe an entry depending on the type of change\&. Tracked entries are printed in an undefined order; parsers should allow for a mixture of the 3 line types in any order\&.
618 .sp
619 Ordinary changed entries have the following format:
620 .sp
621 .if n \{\
622 .RS 4
623 .\}
624 .nf
625 1 <XY> <sub> <mH> <mI> <mW> <hH> <hI> <path>
626 .fi
627 .if n \{\
628 .RE
629 .\}
630 .sp
631 Renamed or copied entries have the following format:
632 .sp
633 .if n \{\
634 .RS 4
635 .\}
636 .nf
637 2 <XY> <sub> <mH> <mI> <mW> <hH> <hI> <X><score> <path><sep><origPath>
638 .fi
639 .if n \{\
640 .RE
641 .\}
642 .sp
643 .if n \{\
644 .RS 4
645 .\}
646 .nf
647 Field Meaning
648 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
649 <XY> A 2 character field containing the staged and
650 unstaged XY values described in the short format,
651 with unchanged indicated by a "\&." rather than
652 a space\&.
653 <sub> A 4 character field describing the submodule state\&.
654 "N\&.\&.\&." when the entry is not a submodule\&.
655 "S<c><m><u>" when the entry is a submodule\&.
656 <c> is "C" if the commit changed; otherwise "\&."\&.
657 <m> is "M" if it has tracked changes; otherwise "\&."\&.
658 <u> is "U" if there are untracked changes; otherwise "\&."\&.
659 <mH> The octal file mode in HEAD\&.
660 <mI> The octal file mode in the index\&.
661 <mW> The octal file mode in the worktree\&.
662 <hH> The object name in HEAD\&.
663 <hI> The object name in the index\&.
664 <X><score> The rename or copy score (denoting the percentage
665 of similarity between the source and target of the
666 move or copy)\&. For example "R100" or "C75"\&.
667 <path> The pathname\&. In a renamed/copied entry, this
668 is the target path\&.
669 <sep> When the `\-z` option is used, the 2 pathnames are separated
670 with a NUL (ASCII 0x00) byte; otherwise, a tab (ASCII 0x09)
671 byte separates them\&.
672 <origPath> The pathname in the commit at HEAD or in the index\&.
673 This is only present in a renamed/copied entry, and
674 tells where the renamed/copied contents came from\&.
675 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
676 .fi
677 .if n \{\
678 .RE
679 .\}
680 .sp
681 Unmerged entries have the following format; the first character is a "u" to distinguish from ordinary changed entries\&.
682 .sp
683 .if n \{\
684 .RS 4
685 .\}
686 .nf
687 u <XY> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>
688 .fi
689 .if n \{\
690 .RE
691 .\}
692 .sp
693 .if n \{\
694 .RS 4
695 .\}
696 .nf
697 Field Meaning
698 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
699 <XY> A 2 character field describing the conflict type
700 as described in the short format\&.
701 <sub> A 4 character field describing the submodule state
702 as described above\&.
703 <m1> The octal file mode in stage 1\&.
704 <m2> The octal file mode in stage 2\&.
705 <m3> The octal file mode in stage 3\&.
706 <mW> The octal file mode in the worktree\&.
707 <h1> The object name in stage 1\&.
708 <h2> The object name in stage 2\&.
709 <h3> The object name in stage 3\&.
710 <path> The pathname\&.
711 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
712 .fi
713 .if n \{\
714 .RE
715 .\}
716 .RE
717 .sp
718 .it 1 an-trap
719 .nr an-no-space-flag 1
720 .nr an-break-flag 1
721 .br
722 .ps +1
723 \fBOther Items\fR
724 .RS 4
725 .sp
726 Following the tracked entries (and if requested), a series of lines will be printed for untracked and then ignored items found in the worktree\&.
727 .sp
728 Untracked items have the following format:
729 .sp
730 .if n \{\
731 .RS 4
732 .\}
733 .nf
734 ? <path>
735 .fi
736 .if n \{\
737 .RE
738 .\}
739 .sp
740 Ignored items have the following format:
741 .sp
742 .if n \{\
743 .RS 4
744 .\}
745 .nf
746 ! <path>
747 .fi
748 .if n \{\
749 .RE
750 .\}
751 .RE
752 .sp
753 .it 1 an-trap
754 .nr an-no-space-flag 1
755 .nr an-break-flag 1
756 .br
757 .ps +1
758 \fBPathname Format Notes and -z\fR
759 .RS 4
760 .sp
761 When the \fB\-z\fR option is given, pathnames are printed as is and without any quoting and lines are terminated with a NUL (ASCII 0x00) byte\&.
762 .sp
763 Without the \fB\-z\fR option, pathnames with "unusual" characters are quoted as explained for the configuration variable \fBcore\&.quotePath\fR (see \fBgit-config\fR(1))\&.
764 .RE
765 .SH "CONFIGURATION"
766 .sp
767 The command honors \fBcolor\&.status\fR (or \fBstatus\&.color\fR \(em they mean the same thing and the latter is kept for backward compatibility) and \fBcolor\&.status\&.<slot>\fR configuration variables to colorize its output\&.
768 .sp
769 If the config variable \fBstatus\&.relativePaths\fR is set to false, then all paths shown are relative to the repository root, not to the current directory\&.
770 .sp
771 If \fBstatus\&.submoduleSummary\fR is set to a non zero number or true (identical to \-1 or an unlimited number), the submodule summary will be enabled for the long format and a summary of commits for modified submodules will be shown (see \-\-summary\-limit option of \fBgit-submodule\fR(1))\&. Please note that the summary output from the status command will be suppressed for all submodules when \fBdiff\&.ignoreSubmodules\fR is set to \fIall\fR or only for those submodules where \fBsubmodule\&.<name>\&.ignore=all\fR\&. To also view the summary for ignored submodules you can either use the \-\-ignore\-submodules=dirty command line option or the \fIgit submodule summary\fR command, which shows a similar output but does not honor these settings\&.
772 .SH "BACKGROUND REFRESH"
773 .sp
774 By default, \fBgit status\fR will automatically refresh the index, updating the cached stat information from the working tree and writing out the result\&. Writing out the updated index is an optimization that isn\(cqt strictly necessary (\fBstatus\fR computes the values for itself, but writing them out is just to save subsequent programs from repeating our computation)\&. When \fBstatus\fR is run in the background, the lock held during the write may conflict with other simultaneous processes, causing them to fail\&. Scripts running \fBstatus\fR in the background should consider using \fBgit \-\-no\-optional\-locks status\fR (see \fBgit\fR(1) for details)\&.
775 .SH "UNTRACKED FILES AND PERFORMANCE"
776 .sp
777 \fBgit status\fR can be very slow in large worktrees if/when it needs to search for untracked files and directories\&. There are many configuration options available to speed this up by either avoiding the work or making use of cached results from previous Git commands\&. There is no single optimum set of settings right for everyone\&. We\(cqll list a summary of the relevant options to help you, but before going into the list, you may want to run \fBgit status\fR again, because your configuration may already be caching \fBgit status\fR results, so it could be faster on subsequent runs\&.
778 .sp
779 .RS 4
780 .ie n \{\
781 \h'-04'\(bu\h'+03'\c
782 .\}
783 .el \{\
784 .sp -1
785 .IP \(bu 2.3
786 .\}
787 The
788 \fB\-\-untracked\-files=no\fR
789 flag or the
790 \fBstatus\&.showUntrackedFiles=no\fR
791 config (see above for both): indicate that
792 \fBgit status\fR
793 should not report untracked files\&. This is the fastest option\&.
794 \fBgit status\fR
795 will not list the untracked files, so you need to be careful to remember if you create any new files and manually
796 \fBgit add\fR
797 them\&.
798 .RE
799 .sp
800 .RS 4
801 .ie n \{\
802 \h'-04'\(bu\h'+03'\c
803 .\}
804 .el \{\
805 .sp -1
806 .IP \(bu 2.3
807 .\}
808 \fBadvice\&.statusUoption=false\fR
809 (see
810 \fBgit-config\fR(1)): setting this variable to
811 \fBfalse\fR
812 disables the warning message given when enumerating untracked files takes more than 2 seconds\&. In a large project, it may take longer and the user may have already accepted the trade off (e\&.g\&. using "\-uno" may not be an acceptable option for the user), in which case, there is no point issuing the warning message, and in such a case, disabling the warning may be the best\&.
813 .RE
814 .sp
815 .RS 4
816 .ie n \{\
817 \h'-04'\(bu\h'+03'\c
818 .\}
819 .el \{\
820 .sp -1
821 .IP \(bu 2.3
822 .\}
823 \fBcore\&.untrackedCache=true\fR
824 (see
825 \fBgit-update-index\fR(1)): enable the untracked cache feature and only search directories that have been modified since the previous
826 \fBgit status\fR
827 command\&. Git remembers the set of untracked files within each directory and assumes that if a directory has not been modified, then the set of untracked files within has not changed\&. This is much faster than enumerating the contents of every directory, but still not without cost, because Git still has to search for the set of modified directories\&. The untracked cache is stored in the
828 \fB\&.git/index\fR
829 file\&. The reduced cost of searching for untracked files is offset slightly by the increased size of the index and the cost of keeping it up\-to\-date\&. That reduced search time is usually worth the additional size\&.
830 .RE
831 .sp
832 .RS 4
833 .ie n \{\
834 \h'-04'\(bu\h'+03'\c
835 .\}
836 .el \{\
837 .sp -1
838 .IP \(bu 2.3
839 .\}
840 \fBcore\&.untrackedCache=true\fR
841 and
842 \fBcore\&.fsmonitor=true\fR
843 or
844 \fBcore\&.fsmonitor=<hook\-command\-pathname>\fR
845 (see
846 \fBgit-update-index\fR(1)): enable both the untracked cache and FSMonitor features and only search directories that have been modified since the previous
847 \fBgit status\fR
848 command\&. This is faster than using just the untracked cache alone because Git can also avoid searching for modified directories\&. Git only has to enumerate the exact set of directories that have changed recently\&. While the FSMonitor feature can be enabled without the untracked cache, the benefits are greatly reduced in that case\&.
849 .RE
850 .sp
851 Note that after you turn on the untracked cache and/or FSMonitor features it may take a few \fBgit status\fR commands for the various caches to warm up before you see improved command times\&. This is normal\&.
852 .SH "SEE ALSO"
853 .sp
854 \fBgitignore\fR(5)
855 .SH "GIT"
856 .sp
857 Part of the \fBgit\fR(1) suite