| 1 | status.relativePaths:: |
| 2 | By default, linkgit:git-status[1] shows paths relative to the |
| 3 | current directory. Setting this variable to `false` shows paths |
| 4 | relative to the repository root (this was the default for Git |
| 5 | prior to v1.5.4). |
| 6 | |
| 7 | status.short:: |
| 8 | Set to true to enable --short by default in linkgit:git-status[1]. |
| 9 | The option --no-short takes precedence over this variable. |
| 10 | |
| 11 | status.branch:: |
| 12 | Set to true to enable --branch by default in linkgit:git-status[1]. |
| 13 | The option --no-branch takes precedence over this variable. |
| 14 | |
| 15 | status.aheadBehind:: |
| 16 | Set to true to enable `--ahead-behind` and false to enable |
| 17 | `--no-ahead-behind` by default in linkgit:git-status[1] for |
| 18 | non-porcelain status formats. Defaults to true. |
| 19 | |
| 20 | status.compareBranches:: |
| 21 | A space-separated list of branch comparison specifiers to use in |
| 22 | linkgit:git-status[1]. Currently, only `@{upstream}` and `@{push}` |
| 23 | are supported. They are interpreted as `branch@{upstream}` and |
| 24 | `branch@{push}` for the current branch. |
| 25 | + |
| 26 | If not set, the default behavior is equivalent to `@{upstream}`, which |
| 27 | compares against the configured upstream tracking branch. |
| 28 | + |
| 29 | The entries are shown in the order they appear in the configuration. |
| 30 | Duplicate entries that resolve to the same ref are suppressed after |
| 31 | their first occurrence, so `@{push} @{upstream} @{push}` shows at |
| 32 | most two comparisons. When `@{upstream}` and `@{push}` resolve to |
| 33 | the same remote-tracking branch, only one comparison is shown. |
| 34 | + |
| 35 | Example: |
| 36 | + |
| 37 | ---- |
| 38 | [status] |
| 39 | compareBranches = @{upstream} @{push} |
| 40 | ---- |
| 41 | + |
| 42 | This would show comparisons against both the configured upstream and push |
| 43 | tracking branches for the current branch. |
| 44 | |
| 45 | status.displayCommentPrefix:: |
| 46 | If set to true, linkgit:git-status[1] will insert a comment |
| 47 | prefix before each output line (starting with |
| 48 | `core.commentChar`, i.e. `#` by default). This was the |
| 49 | behavior of linkgit:git-status[1] in Git 1.8.4 and previous. |
| 50 | Defaults to false. |
| 51 | |
| 52 | status.renameLimit:: |
| 53 | The number of files to consider when performing rename detection |
| 54 | in linkgit:git-status[1] and linkgit:git-commit[1]. Defaults to |
| 55 | the value of diff.renameLimit. |
| 56 | |
| 57 | status.renames:: |
| 58 | Whether and how Git detects renames in linkgit:git-status[1] and |
| 59 | linkgit:git-commit[1] . If set to "false", rename detection is |
| 60 | disabled. If set to "true", basic rename detection is enabled. |
| 61 | If set to "copies" or "copy", Git will detect copies, as well. |
| 62 | Defaults to the value of diff.renames. |
| 63 | |
| 64 | status.showStash:: |
| 65 | If set to true, linkgit:git-status[1] will display the number of |
| 66 | entries currently stashed away. |
| 67 | Defaults to false. |
| 68 | |
| 69 | status.showUntrackedFiles:: |
| 70 | By default, linkgit:git-status[1] and linkgit:git-commit[1] show |
| 71 | files which are not currently tracked by Git. Directories which |
| 72 | contain only untracked files, are shown with the directory name |
| 73 | only. Showing untracked files means that Git needs to lstat() all |
| 74 | the files in the whole repository, which might be slow on some |
| 75 | systems. So, this variable controls how the commands display |
| 76 | the untracked files. Possible values are: |
| 77 | + |
| 78 | -- |
| 79 | * `no` - Show no untracked files. |
| 80 | * `normal` - Show untracked files and directories. |
| 81 | * `all` - Show also individual files in untracked directories. |
| 82 | -- |
| 83 | + |
| 84 | If this variable is not specified, it defaults to 'normal'. |
| 85 | All usual spellings for Boolean value `true` are taken as `normal` |
| 86 | and `false` as `no`. |
| 87 | This variable can be overridden with the -u|--untracked-files option |
| 88 | of linkgit:git-status[1] and linkgit:git-commit[1]. |
| 89 | |
| 90 | status.submoduleSummary:: |
| 91 | Defaults to false. |
| 92 | If this is set to a non-zero number or true (identical to -1 or an |
| 93 | unlimited number), the submodule summary will be enabled and a |
| 94 | summary of commits for modified submodules will be shown (see |
| 95 | --summary-limit option of linkgit:git-submodule[1]). Please note |
| 96 | that the summary output command will be suppressed for all |
| 97 | submodules when `diff.ignoreSubmodules` is set to 'all' or only |
| 98 | for those submodules where `submodule.<name>.ignore=all`. The only |
| 99 | exception to that rule is that status and commit will show staged |
| 100 | submodule changes. To |
| 101 | also view the summary for ignored submodules you can either use |
| 102 | the --ignore-submodules=dirty command-line option or the 'git |
| 103 | submodule summary' command, which shows a similar output but does |
| 104 | not honor these settings. |