The porcelain format, with a few exceptions:ġ. The description of the short format above also describes The porcelain format is similar to the short format, but is guaranteed not to change in aīackwards-incompatible way between Git versions or based on user configuration. If -b is used the short-format status is preceded by a line Ignored files are not listed, unless -ignored option is in effect, in which case XY are For paths that do not have merge conflicts, X shows the status of the index, and Y With interior special characters backslash-escaped.įor paths with merge conflicts, X and Y show the modification states of each side of the In the manner of a C string literal: surrounded by ASCII double quote (34) characters, and If aįilename contains whitespace or other nonprintable characters, that field will be quoted The fields (including the ->) are separated from each other by a single space. Where PATH1 is the path in the HEAD, and the " -> PATH2" part is shown only when PATH1Ĭorresponds to a different path in the index/worktree (i.e. In the short-format, the status of each path is shown as See the status.relativePaths config option below. The current directory if you are working in a subdirectory (this is on purpose, to helpĬutting and pasting). The paths mentioned in the output, unlike many other Git commands, are made relative to Its contents and format are subject to change at any The default, long format, is designed to be human The output from this command is designed to be used as a commit template comment, and all Option syntax.-column and -no-column without options are equivalent to always and See configuration variable column.status for This implies the -porcelain output formatĭisplay untracked files in columns. Terminate entries with NUL, instead of LF. Submodules (and suppresses the output of submodule summaries when the config option Shown (this was the behavior before 1.7.0). Work tree of submodules, only changes to the commits stored in the superproject are They are still scanned for modified content). Used submodules are not considered dirty when they only contain untracked content (but Settings of the ignore option in git-config(1) or gitmodules(5). Submodule modified when it either contains untracked or modified files or its HEADĭiffers from the commit recorded in the superproject and can be used to override any "untracked", "dirty" or "all", which is the default. Ignore changes to submodules when looking for changes. The default can be changed using the status.showUntrackedFiles configuration Return more quickly without showing untracked files. Mode may take some time in a large working tree. Because it takes extra work to find untracked files in the filesystem, this Same as specifying normal), to help you avoid forgetting to add newly createdįiles. When -u option is not used, untracked files and directories are shown (i.e. all - Also shows individual files in untracked directories.normal - Shows untracked files and directories. The mode parameter is optional (defaults to all), and is used to specify the handling Output, but will remain stable across Git versions and regardless of user Give the output in an easy-to-parse format for scripts. Show the branch and tracking info even in short-format. The firstĪre what you would commit by running git commit the second and third are what you couldĬommit by running git add before running git commit. Working tree that are not tracked by Git (and are not ignored by gitignore(5)). Paths that have differences between the working tree and the index file, and paths in the Git-status - Show the working tree statusĭisplays paths that have differences between the index file and the current HEAD commit,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |