1CONFIGURATION FILE 2------------------ 3 4The Git configuration file contains a number of variables that affect 5the Git commands' behavior. The `.git/config` file in each repository 6is used to store the configuration for that repository, and 7`$HOME/.gitconfig` is used to store a per-user configuration as 8fallback values for the `.git/config` file. The file `/etc/gitconfig` 9can be used to store a system-wide default configuration. 10 11The configuration variables are used by both the Git plumbing 12and the porcelains. The variables are divided into sections, wherein 13the fully qualified variable name of the variable itself is the last 14dot-separated segment and the section name is everything before the last 15dot. The variable names are case-insensitive, allow only alphanumeric 16characters and `-`, and must start with an alphabetic character. Some 17variables may appear multiple times; we say then that the variable is 18multivalued. 19 20Syntax 21~~~~~~ 22 23The syntax is fairly flexible and permissive; whitespaces are mostly 24ignored. The '#' and ';' characters begin comments to the end of line, 25blank lines are ignored. 26 27The file consists of sections and variables. A section begins with 28the name of the section in square brackets and continues until the next 29section begins. Section names are case-insensitive. Only alphanumeric 30characters, `-` and `.` are allowed in section names. Each variable 31must belong to some section, which means that there must be a section 32header before the first setting of a variable. 33 34Sections can be further divided into subsections. To begin a subsection 35put its name in double quotes, separated by space from the section name, 36in the section header, like in the example below: 37 38-------- 39 [section "subsection"] 40 41-------- 42 43Subsection names are case sensitive and can contain any characters except 44newline and the null byte. Doublequote `"` and backslash can be included 45by escaping them as `\"` and `\\`, respectively. Backslashes preceding 46other characters are dropped when reading; for example, `\t` is read as 47`t` and `\0` is read as `0` Section headers cannot span multiple lines. 48Variables may belong directly to a section or to a given subsection. You 49can have `[section]` if you have `[section "subsection"]`, but you don't 50need to. 51 52There is also a deprecated `[section.subsection]` syntax. With this 53syntax, the subsection name is converted to lower-case and is also 54compared case sensitively. These subsection names follow the same 55restrictions as section names. 56 57All the other lines (and the remainder of the line after the section 58header) are recognized as setting variables, in the form 59'name = value' (or just 'name', which is a short-hand to say that 60the variable is the boolean "true"). 61The variable names are case-insensitive, allow only alphanumeric characters 62and `-`, and must start with an alphabetic character. 63 64A line that defines a value can be continued to the next line by 65ending it with a `\`; the backquote and the end-of-line are 66stripped. Leading whitespaces after 'name =', the remainder of the 67line after the first comment character '#' or ';', and trailing 68whitespaces of the line are discarded unless they are enclosed in 69double quotes. Internal whitespaces within the value are retained 70verbatim. 71 72Inside double quotes, double quote `"` and backslash `\` characters 73must be escaped: use `\"` for `"` and `\\` for `\`. 74 75The following escape sequences (beside `\"` and `\\`) are recognized: 76`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 77and `\b` for backspace (BS). Other char escape sequences (including octal 78escape sequences) are invalid. 79 80 81Includes 82~~~~~~~~ 83 84The `include` and `includeIf` sections allow you to include config 85directives from another source. These sections behave identically to 86each other with the exception that `includeIf` sections may be ignored 87if their condition does not evaluate to true; see "Conditional includes" 88below. 89 90You can include a config file from another by setting the special 91`include.path` (or `includeIf.*.path`) variable to the name of the file 92to be included. The variable takes a pathname as its value, and is 93subject to tilde expansion. These variables can be given multiple times. 94 95The contents of the included file are inserted immediately, as if they 96had been found at the location of the include directive. If the value of the 97variable is a relative path, the path is considered to 98be relative to the configuration file in which the include directive 99was found. See below for examples. 100 101Conditional includes 102~~~~~~~~~~~~~~~~~~~~ 103 104You can include a config file from another conditionally by setting a 105`includeIf.<condition>.path` variable to the name of the file to be 106included. 107 108The condition starts with a keyword followed by a colon and some data 109whose format and meaning depends on the keyword. Supported keywords 110are: 111 112`gitdir`:: 113 114 The data that follows the keyword `gitdir:` is used as a glob 115 pattern. If the location of the .git directory matches the 116 pattern, the include condition is met. 117+ 118The .git location may be auto-discovered, or come from `$GIT_DIR` 119environment variable. If the repository is auto discovered via a .git 120file (e.g. from submodules, or a linked worktree), the .git location 121would be the final location where the .git directory is, not where the 122.git file is. 123+ 124The pattern can contain standard globbing wildcards and two additional 125ones, `**/` and `/**`, that can match multiple path components. Please 126refer to linkgit:gitignore[5] for details. For convenience: 127 128 * If the pattern starts with `~/`, `~` will be substituted with the 129 content of the environment variable `HOME`. 130 131 * If the pattern starts with `./`, it is replaced with the directory 132 containing the current config file. 133 134 * If the pattern does not start with either `~/`, `./` or `/`, `**/` 135 will be automatically prepended. For example, the pattern `foo/bar` 136 becomes `**/foo/bar` and would match `/any/path/to/foo/bar`. 137 138 * If the pattern ends with `/`, `**` will be automatically added. For 139 example, the pattern `foo/` becomes `foo/**`. In other words, it 140 matches "foo" and everything inside, recursively. 141 142`gitdir/i`:: 143 This is the same as `gitdir` except that matching is done 144 case-insensitively (e.g. on case-insensitive file sytems) 145 146A few more notes on matching via `gitdir` and `gitdir/i`: 147 148 * Symlinks in `$GIT_DIR` are not resolved before matching. 149 150 * Both the symlink & realpath versions of paths will be matched 151 outside of `$GIT_DIR`. E.g. if ~/git is a symlink to 152 /mnt/storage/git, both `gitdir:~/git` and `gitdir:/mnt/storage/git` 153 will match. 154+ 155This was not the case in the initial release of this feature in 156v2.13.0, which only matched the realpath version. Configuration that 157wants to be compatible with the initial release of this feature needs 158to either specify only the realpath version, or both versions. 159 160 * Note that "../" is not special and will match literally, which is 161 unlikely what you want. 162 163Example 164~~~~~~~ 165 166 # Core variables 167 [core] 168 ; Don't trust file modes 169 filemode = false 170 171 # Our diff algorithm 172 [diff] 173 external = /usr/local/bin/diff-wrapper 174 renames = true 175 176 [branch "devel"] 177 remote = origin 178 merge = refs/heads/devel 179 180 # Proxy settings 181 [core] 182 gitProxy="ssh" for "kernel.org" 183 gitProxy=default-proxy ; for the rest 184 185 [include] 186 path = /path/to/foo.inc ; include by absolute path 187 path = foo.inc ; find "foo.inc" relative to the current file 188 path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory 189 190 ; include if $GIT_DIR is /path/to/foo/.git 191 [includeIf "gitdir:/path/to/foo/.git"] 192 path = /path/to/foo.inc 193 194 ; include for all repositories inside /path/to/group 195 [includeIf "gitdir:/path/to/group/"] 196 path = /path/to/foo.inc 197 198 ; include for all repositories inside $HOME/to/group 199 [includeIf "gitdir:~/to/group/"] 200 path = /path/to/foo.inc 201 202 ; relative paths are always relative to the including 203 ; file (if the condition is true); their location is not 204 ; affected by the condition 205 [includeIf "gitdir:/path/to/group/"] 206 path = foo.inc 207 208Values 209~~~~~~ 210 211Values of many variables are treated as a simple string, but there 212are variables that take values of specific types and there are rules 213as to how to spell them. 214 215boolean:: 216 217 When a variable is said to take a boolean value, many 218 synonyms are accepted for 'true' and 'false'; these are all 219 case-insensitive. 220 221 true;; Boolean true literals are `yes`, `on`, `true`, 222 and `1`. Also, a variable defined without `= <value>` 223 is taken as true. 224 225 false;; Boolean false literals are `no`, `off`, `false`, 226 `0` and the empty string. 227+ 228When converting value to the canonical form using `--bool` type 229specifier, 'git config' will ensure that the output is "true" or 230"false" (spelled in lowercase). 231 232integer:: 233 The value for many variables that specify various sizes can 234 be suffixed with `k`, `M`,... to mean "scale the number by 235 1024", "by 1024x1024", etc. 236 237color:: 238 The value for a variable that takes a color is a list of 239 colors (at most two, one for foreground and one for background) 240 and attributes (as many as you want), separated by spaces. 241+ 242The basic colors accepted are `normal`, `black`, `red`, `green`, `yellow`, 243`blue`, `magenta`, `cyan` and `white`. The first color given is the 244foreground; the second is the background. 245+ 246Colors may also be given as numbers between 0 and 255; these use ANSI 247256-color mode (but note that not all terminals may support this). If 248your terminal supports it, you may also specify 24-bit RGB values as 249hex, like `#ff0ab3`. 250+ 251The accepted attributes are `bold`, `dim`, `ul`, `blink`, `reverse`, 252`italic`, and `strike` (for crossed-out or "strikethrough" letters). 253The position of any attributes with respect to the colors 254(before, after, or in between), doesn't matter. Specific attributes may 255be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`, 256`no-ul`, etc). 257+ 258An empty color string produces no color effect at all. This can be used 259to avoid coloring specific elements without disabling color entirely. 260+ 261For git's pre-defined color slots, the attributes are meant to be reset 262at the beginning of each item in the colored output. So setting 263`color.decorate.branch` to `black` will paint that branch name in a 264plain `black`, even if the previous thing on the same output line (e.g. 265opening parenthesis before the list of branch names in `log --decorate` 266output) is set to be painted with `bold` or some other attribute. 267However, custom log formats may do more complicated and layered 268coloring, and the negated forms may be useful there. 269 270pathname:: 271 A variable that takes a pathname value can be given a 272 string that begins with "`~/`" or "`~user/`", and the usual 273 tilde expansion happens to such a string: `~/` 274 is expanded to the value of `$HOME`, and `~user/` to the 275 specified user's home directory. 276 277 278Variables 279~~~~~~~~~ 280 281Note that this list is non-comprehensive and not necessarily complete. 282For command-specific variables, you will find a more detailed description 283in the appropriate manual page. 284 285Other git-related tools may and do use their own variables. When 286inventing new variables for use in your own tool, make sure their 287names do not conflict with those that are used by Git itself and 288other popular tools, and describe them in your documentation. 289 290 291advice.*:: 292 These variables control various optional help messages designed to 293 aid new users. All 'advice.*' variables default to 'true', and you 294 can tell Git that you do not need help by setting these to 'false': 295+ 296-- 297 pushUpdateRejected:: 298 Set this variable to 'false' if you want to disable 299 'pushNonFFCurrent', 300 'pushNonFFMatching', 'pushAlreadyExists', 301 'pushFetchFirst', and 'pushNeedsForce' 302 simultaneously. 303 pushNonFFCurrent:: 304 Advice shown when linkgit:git-push[1] fails due to a 305 non-fast-forward update to the current branch. 306 pushNonFFMatching:: 307 Advice shown when you ran linkgit:git-push[1] and pushed 308 'matching refs' explicitly (i.e. you used ':', or 309 specified a refspec that isn't your current branch) and 310 it resulted in a non-fast-forward error. 311 pushAlreadyExists:: 312 Shown when linkgit:git-push[1] rejects an update that 313 does not qualify for fast-forwarding (e.g., a tag.) 314 pushFetchFirst:: 315 Shown when linkgit:git-push[1] rejects an update that 316 tries to overwrite a remote ref that points at an 317 object we do not have. 318 pushNeedsForce:: 319 Shown when linkgit:git-push[1] rejects an update that 320 tries to overwrite a remote ref that points at an 321 object that is not a commit-ish, or make the remote 322 ref point at an object that is not a commit-ish. 323 statusHints:: 324 Show directions on how to proceed from the current 325 state in the output of linkgit:git-status[1], in 326 the template shown when writing commit messages in 327 linkgit:git-commit[1], and in the help message shown 328 by linkgit:git-checkout[1] when switching branch. 329 statusUoption:: 330 Advise to consider using the `-u` option to linkgit:git-status[1] 331 when the command takes more than 2 seconds to enumerate untracked 332 files. 333 commitBeforeMerge:: 334 Advice shown when linkgit:git-merge[1] refuses to 335 merge to avoid overwriting local changes. 336 resolveConflict:: 337 Advice shown by various commands when conflicts 338 prevent the operation from being performed. 339 implicitIdentity:: 340 Advice on how to set your identity configuration when 341 your information is guessed from the system username and 342 domain name. 343 detachedHead:: 344 Advice shown when you used linkgit:git-checkout[1] to 345 move to the detach HEAD state, to instruct how to create 346 a local branch after the fact. 347 checkoutAmbiguousRemoteBranchName:: 348 Advice shown when the argument to 349 linkgit:git-checkout[1] ambiguously resolves to a 350 remote tracking branch on more than one remote in 351 situations where an unambiguous argument would have 352 otherwise caused a remote-tracking branch to be 353 checked out. See the `checkout.defaultRemote` 354 configuration variable for how to set a given remote 355 to used by default in some situations where this 356 advice would be printed. 357 amWorkDir:: 358 Advice that shows the location of the patch file when 359 linkgit:git-am[1] fails to apply it. 360 rmHints:: 361 In case of failure in the output of linkgit:git-rm[1], 362 show directions on how to proceed from the current state. 363 addEmbeddedRepo:: 364 Advice on what to do when you've accidentally added one 365 git repo inside of another. 366 ignoredHook:: 367 Advice shown if a hook is ignored because the hook is not 368 set as executable. 369 waitingForEditor:: 370 Print a message to the terminal whenever Git is waiting for 371 editor input from the user. 372-- 373 374core.fileMode:: 375 Tells Git if the executable bit of files in the working tree 376 is to be honored. 377+ 378Some filesystems lose the executable bit when a file that is 379marked as executable is checked out, or checks out a 380non-executable file with executable bit on. 381linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 382to see if it handles the executable bit correctly 383and this variable is automatically set as necessary. 384+ 385A repository, however, may be on a filesystem that handles 386the filemode correctly, and this variable is set to 'true' 387when created, but later may be made accessible from another 388environment that loses the filemode (e.g. exporting ext4 via 389CIFS mount, visiting a Cygwin created repository with 390Git for Windows or Eclipse). 391In such a case it may be necessary to set this variable to 'false'. 392See linkgit:git-update-index[1]. 393+ 394The default is true (when core.filemode is not specified in the config file). 395 396core.hideDotFiles:: 397 (Windows-only) If true, mark newly-created directories and files whose 398 name starts with a dot as hidden. If 'dotGitOnly', only the `.git/` 399 directory is hidden, but no other files starting with a dot. The 400 default mode is 'dotGitOnly'. 401 402core.ignoreCase:: 403 Internal variable which enables various workarounds to enable 404 Git to work better on filesystems that are not case sensitive, 405 like APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing 406 finds "makefile" when Git expects "Makefile", Git will assume 407 it is really the same file, and continue to remember it as 408 "Makefile". 409+ 410The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 411will probe and set core.ignoreCase true if appropriate when the repository 412is created. 413+ 414Git relies on the proper configuration of this variable for your operating 415and file system. Modifying this value may result in unexpected behavior. 416 417core.precomposeUnicode:: 418 This option is only used by Mac OS implementation of Git. 419 When core.precomposeUnicode=true, Git reverts the unicode decomposition 420 of filenames done by Mac OS. This is useful when sharing a repository 421 between Mac OS and Linux or Windows. 422 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 423 When false, file names are handled fully transparent by Git, 424 which is backward compatible with older versions of Git. 425 426core.protectHFS:: 427 If set to true, do not allow checkout of paths that would 428 be considered equivalent to `.git` on an HFS+ filesystem. 429 Defaults to `true` on Mac OS, and `false` elsewhere. 430 431core.protectNTFS:: 432 If set to true, do not allow checkout of paths that would 433 cause problems with the NTFS filesystem, e.g. conflict with 434 8.3 "short" names. 435 Defaults to `true` on Windows, and `false` elsewhere. 436 437core.fsmonitor:: 438 If set, the value of this variable is used as a command which 439 will identify all files that may have changed since the 440 requested date/time. This information is used to speed up git by 441 avoiding unnecessary processing of files that have not changed. 442 See the "fsmonitor-watchman" section of linkgit:githooks[5]. 443 444core.trustctime:: 445 If false, the ctime differences between the index and the 446 working tree are ignored; useful when the inode change time 447 is regularly modified by something outside Git (file system 448 crawlers and some backup systems). 449 See linkgit:git-update-index[1]. True by default. 450 451core.splitIndex:: 452 If true, the split-index feature of the index will be used. 453 See linkgit:git-update-index[1]. False by default. 454 455core.untrackedCache:: 456 Determines what to do about the untracked cache feature of the 457 index. It will be kept, if this variable is unset or set to 458 `keep`. It will automatically be added if set to `true`. And 459 it will automatically be removed, if set to `false`. Before 460 setting it to `true`, you should check that mtime is working 461 properly on your system. 462 See linkgit:git-update-index[1]. `keep` by default. 463 464core.checkStat:: 465 Determines which stat fields to match between the index 466 and work tree. The user can set this to 'default' or 467 'minimal'. Default (or explicitly 'default'), is to check 468 all fields, including the sub-second part of mtime and ctime. 469 470core.quotePath:: 471 Commands that output paths (e.g. 'ls-files', 'diff'), will 472 quote "unusual" characters in the pathname by enclosing the 473 pathname in double-quotes and escaping those characters with 474 backslashes in the same way C escapes control characters (e.g. 475 `\t` for TAB, `\n` for LF, `\\` for backslash) or bytes with 476 values larger than 0x80 (e.g. octal `\302\265` for "micro" in 477 UTF-8). If this variable is set to false, bytes higher than 478 0x80 are not considered "unusual" any more. Double-quotes, 479 backslash and control characters are always escaped regardless 480 of the setting of this variable. A simple space character is 481 not considered "unusual". Many commands can output pathnames 482 completely verbatim using the `-z` option. The default value 483 is true. 484 485core.eol:: 486 Sets the line ending type to use in the working directory for 487 files that have the `text` property set when core.autocrlf is false. 488 Alternatives are 'lf', 'crlf' and 'native', which uses the platform's 489 native line ending. The default value is `native`. See 490 linkgit:gitattributes[5] for more information on end-of-line 491 conversion. 492 493core.safecrlf:: 494 If true, makes Git check if converting `CRLF` is reversible when 495 end-of-line conversion is active. Git will verify if a command 496 modifies a file in the work tree either directly or indirectly. 497 For example, committing a file followed by checking out the 498 same file should yield the original file in the work tree. If 499 this is not the case for the current setting of 500 `core.autocrlf`, Git will reject the file. The variable can 501 be set to "warn", in which case Git will only warn about an 502 irreversible conversion but continue the operation. 503+ 504CRLF conversion bears a slight chance of corrupting data. 505When it is enabled, Git will convert CRLF to LF during commit and LF to 506CRLF during checkout. A file that contains a mixture of LF and 507CRLF before the commit cannot be recreated by Git. For text 508files this is the right thing to do: it corrects line endings 509such that we have only LF line endings in the repository. 510But for binary files that are accidentally classified as text the 511conversion can corrupt data. 512+ 513If you recognize such corruption early you can easily fix it by 514setting the conversion type explicitly in .gitattributes. Right 515after committing you still have the original file in your work 516tree and this file is not yet corrupted. You can explicitly tell 517Git that this file is binary and Git will handle the file 518appropriately. 519+ 520Unfortunately, the desired effect of cleaning up text files with 521mixed line endings and the undesired effect of corrupting binary 522files cannot be distinguished. In both cases CRLFs are removed 523in an irreversible way. For text files this is the right thing 524to do because CRLFs are line endings, while for binary files 525converting CRLFs corrupts data. 526+ 527Note, this safety check does not mean that a checkout will generate a 528file identical to the original file for a different setting of 529`core.eol` and `core.autocrlf`, but only for the current one. For 530example, a text file with `LF` would be accepted with `core.eol=lf` 531and could later be checked out with `core.eol=crlf`, in which case the 532resulting file would contain `CRLF`, although the original file 533contained `LF`. However, in both work trees the line endings would be 534consistent, that is either all `LF` or all `CRLF`, but never mixed. A 535file with mixed line endings would be reported by the `core.safecrlf` 536mechanism. 537 538core.autocrlf:: 539 Setting this variable to "true" is the same as setting 540 the `text` attribute to "auto" on all files and core.eol to "crlf". 541 Set to true if you want to have `CRLF` line endings in your 542 working directory and the repository has LF line endings. 543 This variable can be set to 'input', 544 in which case no output conversion is performed. 545 546core.checkRoundtripEncoding:: 547 A comma and/or whitespace separated list of encodings that Git 548 performs UTF-8 round trip checks on if they are used in an 549 `working-tree-encoding` attribute (see linkgit:gitattributes[5]). 550 The default value is `SHIFT-JIS`. 551 552core.symlinks:: 553 If false, symbolic links are checked out as small plain files that 554 contain the link text. linkgit:git-update-index[1] and 555 linkgit:git-add[1] will not change the recorded type to regular 556 file. Useful on filesystems like FAT that do not support 557 symbolic links. 558+ 559The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 560will probe and set core.symlinks false if appropriate when the repository 561is created. 562 563core.gitProxy:: 564 A "proxy command" to execute (as 'command host port') instead 565 of establishing direct connection to the remote server when 566 using the Git protocol for fetching. If the variable value is 567 in the "COMMAND for DOMAIN" format, the command is applied only 568 on hostnames ending with the specified domain string. This variable 569 may be set multiple times and is matched in the given order; 570 the first match wins. 571+ 572Can be overridden by the `GIT_PROXY_COMMAND` environment variable 573(which always applies universally, without the special "for" 574handling). 575+ 576The special string `none` can be used as the proxy command to 577specify that no proxy be used for a given domain pattern. 578This is useful for excluding servers inside a firewall from 579proxy use, while defaulting to a common proxy for external domains. 580 581core.sshCommand:: 582 If this variable is set, `git fetch` and `git push` will 583 use the specified command instead of `ssh` when they need to 584 connect to a remote system. The command is in the same form as 585 the `GIT_SSH_COMMAND` environment variable and is overridden 586 when the environment variable is set. 587 588core.ignoreStat:: 589 If true, Git will avoid using lstat() calls to detect if files have 590 changed by setting the "assume-unchanged" bit for those tracked files 591 which it has updated identically in both the index and working tree. 592+ 593When files are modified outside of Git, the user will need to stage 594the modified files explicitly (e.g. see 'Examples' section in 595linkgit:git-update-index[1]). 596Git will not normally detect changes to those files. 597+ 598This is useful on systems where lstat() calls are very slow, such as 599CIFS/Microsoft Windows. 600+ 601False by default. 602 603core.preferSymlinkRefs:: 604 Instead of the default "symref" format for HEAD 605 and other symbolic reference files, use symbolic links. 606 This is sometimes needed to work with old scripts that 607 expect HEAD to be a symbolic link. 608 609core.bare:: 610 If true this repository is assumed to be 'bare' and has no 611 working directory associated with it. If this is the case a 612 number of commands that require a working directory will be 613 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 614+ 615This setting is automatically guessed by linkgit:git-clone[1] or 616linkgit:git-init[1] when the repository was created. By default a 617repository that ends in "/.git" is assumed to be not bare (bare = 618false), while all other repositories are assumed to be bare (bare 619= true). 620 621core.worktree:: 622 Set the path to the root of the working tree. 623 If `GIT_COMMON_DIR` environment variable is set, core.worktree 624 is ignored and not used for determining the root of working tree. 625 This can be overridden by the `GIT_WORK_TREE` environment 626 variable and the `--work-tree` command-line option. 627 The value can be an absolute path or relative to the path to 628 the .git directory, which is either specified by --git-dir 629 or GIT_DIR, or automatically discovered. 630 If --git-dir or GIT_DIR is specified but none of 631 --work-tree, GIT_WORK_TREE and core.worktree is specified, 632 the current working directory is regarded as the top level 633 of your working tree. 634+ 635Note that this variable is honored even when set in a configuration 636file in a ".git" subdirectory of a directory and its value differs 637from the latter directory (e.g. "/path/to/.git/config" has 638core.worktree set to "/different/path"), which is most likely a 639misconfiguration. Running Git commands in the "/path/to" directory will 640still use "/different/path" as the root of the work tree and can cause 641confusion unless you know what you are doing (e.g. you are creating a 642read-only snapshot of the same index to a location different from the 643repository's usual working tree). 644 645core.logAllRefUpdates:: 646 Enable the reflog. Updates to a ref <ref> is logged to the file 647 "`$GIT_DIR/logs/<ref>`", by appending the new and old 648 SHA-1, the date/time and the reason of the update, but 649 only when the file exists. If this configuration 650 variable is set to `true`, missing "`$GIT_DIR/logs/<ref>`" 651 file is automatically created for branch heads (i.e. under 652 `refs/heads/`), remote refs (i.e. under `refs/remotes/`), 653 note refs (i.e. under `refs/notes/`), and the symbolic ref `HEAD`. 654 If it is set to `always`, then a missing reflog is automatically 655 created for any ref under `refs/`. 656+ 657This information can be used to determine what commit 658was the tip of a branch "2 days ago". 659+ 660This value is true by default in a repository that has 661a working directory associated with it, and false by 662default in a bare repository. 663 664core.repositoryFormatVersion:: 665 Internal variable identifying the repository format and layout 666 version. 667 668core.sharedRepository:: 669 When 'group' (or 'true'), the repository is made shareable between 670 several users in a group (making sure all the files and objects are 671 group-writable). When 'all' (or 'world' or 'everybody'), the 672 repository will be readable by all users, additionally to being 673 group-shareable. When 'umask' (or 'false'), Git will use permissions 674 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 675 files in the repository will have this mode value. '0xxx' will override 676 user's umask value (whereas the other options will only override 677 requested parts of the user's umask value). Examples: '0660' will make 678 the repo read/write-able for the owner and group, but inaccessible to 679 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 680 repository that is group-readable but not group-writable. 681 See linkgit:git-init[1]. False by default. 682 683core.warnAmbiguousRefs:: 684 If true, Git will warn you if the ref name you passed it is ambiguous 685 and might match multiple refs in the repository. True by default. 686 687core.compression:: 688 An integer -1..9, indicating a default compression level. 689 -1 is the zlib default. 0 means no compression, 690 and 1..9 are various speed/size tradeoffs, 9 being slowest. 691 If set, this provides a default to other compression variables, 692 such as `core.looseCompression` and `pack.compression`. 693 694core.looseCompression:: 695 An integer -1..9, indicating the compression level for objects that 696 are not in a pack file. -1 is the zlib default. 0 means no 697 compression, and 1..9 are various speed/size tradeoffs, 9 being 698 slowest. If not set, defaults to core.compression. If that is 699 not set, defaults to 1 (best speed). 700 701core.packedGitWindowSize:: 702 Number of bytes of a pack file to map into memory in a 703 single mapping operation. Larger window sizes may allow 704 your system to process a smaller number of large pack files 705 more quickly. Smaller window sizes will negatively affect 706 performance due to increased calls to the operating system's 707 memory manager, but may improve performance when accessing 708 a large number of large pack files. 709+ 710Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 711MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 712be reasonable for all users/operating systems. You probably do 713not need to adjust this value. 714+ 715Common unit suffixes of 'k', 'm', or 'g' are supported. 716 717core.packedGitLimit:: 718 Maximum number of bytes to map simultaneously into memory 719 from pack files. If Git needs to access more than this many 720 bytes at once to complete an operation it will unmap existing 721 regions to reclaim virtual address space within the process. 722+ 723Default is 256 MiB on 32 bit platforms and 32 TiB (effectively 724unlimited) on 64 bit platforms. 725This should be reasonable for all users/operating systems, except on 726the largest projects. You probably do not need to adjust this value. 727+ 728Common unit suffixes of 'k', 'm', or 'g' are supported. 729 730core.deltaBaseCacheLimit:: 731 Maximum number of bytes to reserve for caching base objects 732 that may be referenced by multiple deltified objects. By storing the 733 entire decompressed base objects in a cache Git is able 734 to avoid unpacking and decompressing frequently used base 735 objects multiple times. 736+ 737Default is 96 MiB on all platforms. This should be reasonable 738for all users/operating systems, except on the largest projects. 739You probably do not need to adjust this value. 740+ 741Common unit suffixes of 'k', 'm', or 'g' are supported. 742 743core.bigFileThreshold:: 744 Files larger than this size are stored deflated, without 745 attempting delta compression. Storing large files without 746 delta compression avoids excessive memory usage, at the 747 slight expense of increased disk usage. Additionally files 748 larger than this size are always treated as binary. 749+ 750Default is 512 MiB on all platforms. This should be reasonable 751for most projects as source code and other text files can still 752be delta compressed, but larger binary media files won't be. 753+ 754Common unit suffixes of 'k', 'm', or 'g' are supported. 755 756core.excludesFile:: 757 Specifies the pathname to the file that contains patterns to 758 describe paths that are not meant to be tracked, in addition 759 to '.gitignore' (per-directory) and '.git/info/exclude'. 760 Defaults to `$XDG_CONFIG_HOME/git/ignore`. 761 If `$XDG_CONFIG_HOME` is either not set or empty, `$HOME/.config/git/ignore` 762 is used instead. See linkgit:gitignore[5]. 763 764core.askPass:: 765 Some commands (e.g. svn and http interfaces) that interactively 766 ask for a password can be told to use an external program given 767 via the value of this variable. Can be overridden by the `GIT_ASKPASS` 768 environment variable. If not set, fall back to the value of the 769 `SSH_ASKPASS` environment variable or, failing that, a simple password 770 prompt. The external program shall be given a suitable prompt as 771 command-line argument and write the password on its STDOUT. 772 773core.attributesFile:: 774 In addition to '.gitattributes' (per-directory) and 775 '.git/info/attributes', Git looks into this file for attributes 776 (see linkgit:gitattributes[5]). Path expansions are made the same 777 way as for `core.excludesFile`. Its default value is 778 `$XDG_CONFIG_HOME/git/attributes`. If `$XDG_CONFIG_HOME` is either not 779 set or empty, `$HOME/.config/git/attributes` is used instead. 780 781core.hooksPath:: 782 By default Git will look for your hooks in the 783 '$GIT_DIR/hooks' directory. Set this to different path, 784 e.g. '/etc/git/hooks', and Git will try to find your hooks in 785 that directory, e.g. '/etc/git/hooks/pre-receive' instead of 786 in '$GIT_DIR/hooks/pre-receive'. 787+ 788The path can be either absolute or relative. A relative path is 789taken as relative to the directory where the hooks are run (see 790the "DESCRIPTION" section of linkgit:githooks[5]). 791+ 792This configuration variable is useful in cases where you'd like to 793centrally configure your Git hooks instead of configuring them on a 794per-repository basis, or as a more flexible and centralized 795alternative to having an `init.templateDir` where you've changed 796default hooks. 797 798core.editor:: 799 Commands such as `commit` and `tag` that let you edit 800 messages by launching an editor use the value of this 801 variable when it is set, and the environment variable 802 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 803 804core.commentChar:: 805 Commands such as `commit` and `tag` that let you edit 806 messages consider a line that begins with this character 807 commented, and removes them after the editor returns 808 (default '#'). 809+ 810If set to "auto", `git-commit` would select a character that is not 811the beginning character of any line in existing commit messages. 812 813core.filesRefLockTimeout:: 814 The length of time, in milliseconds, to retry when trying to 815 lock an individual reference. Value 0 means not to retry at 816 all; -1 means to try indefinitely. Default is 100 (i.e., 817 retry for 100ms). 818 819core.packedRefsTimeout:: 820 The length of time, in milliseconds, to retry when trying to 821 lock the `packed-refs` file. Value 0 means not to retry at 822 all; -1 means to try indefinitely. Default is 1000 (i.e., 823 retry for 1 second). 824 825sequence.editor:: 826 Text editor used by `git rebase -i` for editing the rebase instruction file. 827 The value is meant to be interpreted by the shell when it is used. 828 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 829 When not configured the default commit message editor is used instead. 830 831core.pager:: 832 Text viewer for use by Git commands (e.g., 'less'). The value 833 is meant to be interpreted by the shell. The order of preference 834 is the `$GIT_PAGER` environment variable, then `core.pager` 835 configuration, then `$PAGER`, and then the default chosen at 836 compile time (usually 'less'). 837+ 838When the `LESS` environment variable is unset, Git sets it to `FRX` 839(if `LESS` environment variable is set, Git does not change it at 840all). If you want to selectively override Git's default setting 841for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 842be passed to the shell by Git, which will translate the final 843command to `LESS=FRX less -S`. The environment does not set the 844`S` option but the command line does, instructing less to truncate 845long lines. Similarly, setting `core.pager` to `less -+F` will 846deactivate the `F` option specified by the environment from the 847command-line, deactivating the "quit if one screen" behavior of 848`less`. One can specifically activate some flags for particular 849commands: for example, setting `pager.blame` to `less -S` enables 850line truncation only for `git blame`. 851+ 852Likewise, when the `LV` environment variable is unset, Git sets it 853to `-c`. You can override this setting by exporting `LV` with 854another value or setting `core.pager` to `lv +c`. 855 856core.whitespace:: 857 A comma separated list of common whitespace problems to 858 notice. 'git diff' will use `color.diff.whitespace` to 859 highlight them, and 'git apply --whitespace=error' will 860 consider them as errors. You can prefix `-` to disable 861 any of them (e.g. `-trailing-space`): 862+ 863* `blank-at-eol` treats trailing whitespaces at the end of the line 864 as an error (enabled by default). 865* `space-before-tab` treats a space character that appears immediately 866 before a tab character in the initial indent part of the line as an 867 error (enabled by default). 868* `indent-with-non-tab` treats a line that is indented with space 869 characters instead of the equivalent tabs as an error (not enabled by 870 default). 871* `tab-in-indent` treats a tab character in the initial indent part of 872 the line as an error (not enabled by default). 873* `blank-at-eof` treats blank lines added at the end of file as an error 874 (enabled by default). 875* `trailing-space` is a short-hand to cover both `blank-at-eol` and 876 `blank-at-eof`. 877* `cr-at-eol` treats a carriage-return at the end of line as 878 part of the line terminator, i.e. with it, `trailing-space` 879 does not trigger if the character before such a carriage-return 880 is not a whitespace (not enabled by default). 881* `tabwidth=<n>` tells how many character positions a tab occupies; this 882 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 883 errors. The default tab width is 8. Allowed values are 1 to 63. 884 885core.fsyncObjectFiles:: 886 This boolean will enable 'fsync()' when writing object files. 887+ 888This is a total waste of time and effort on a filesystem that orders 889data writes properly, but can be useful for filesystems that do not use 890journalling (traditional UNIX filesystems) or that only journal metadata 891and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 892 893core.preloadIndex:: 894 Enable parallel index preload for operations like 'git diff' 895+ 896This can speed up operations like 'git diff' and 'git status' especially 897on filesystems like NFS that have weak caching semantics and thus 898relatively high IO latencies. When enabled, Git will do the 899index comparison to the filesystem data in parallel, allowing 900overlapping IO's. Defaults to true. 901 902core.createObject:: 903 You can set this to 'link', in which case a hardlink followed by 904 a delete of the source are used to make sure that object creation 905 will not overwrite existing objects. 906+ 907On some file system/operating system combinations, this is unreliable. 908Set this config setting to 'rename' there; However, This will remove the 909check that makes sure that existing object files will not get overwritten. 910 911core.notesRef:: 912 When showing commit messages, also show notes which are stored in 913 the given ref. The ref must be fully qualified. If the given 914 ref does not exist, it is not an error but means that no 915 notes should be printed. 916+ 917This setting defaults to "refs/notes/commits", and it can be overridden by 918the `GIT_NOTES_REF` environment variable. See linkgit:git-notes[1]. 919 920gc.commitGraph:: 921 If true, then gc will rewrite the commit-graph file when 922 linkgit:git-gc[1] is run. When using linkgit:git-gc[1] 923 '--auto' the commit-graph will be updated if housekeeping is 924 required. Default is false. See linkgit:git-commit-graph[1] 925 for details. 926 927core.useReplaceRefs:: 928 If set to `false`, behave as if the `--no-replace-objects` 929 option was given on the command line. See linkgit:git[1] and 930 linkgit:git-replace[1] for more information. 931 932core.sparseCheckout:: 933 Enable "sparse checkout" feature. See section "Sparse checkout" in 934 linkgit:git-read-tree[1] for more information. 935 936core.abbrev:: 937 Set the length object names are abbreviated to. If 938 unspecified or set to "auto", an appropriate value is 939 computed based on the approximate number of packed objects 940 in your repository, which hopefully is enough for 941 abbreviated object names to stay unique for some time. 942 The minimum length is 4. 943 944add.ignoreErrors:: 945add.ignore-errors (deprecated):: 946 Tells 'git add' to continue adding files when some files cannot be 947 added due to indexing errors. Equivalent to the `--ignore-errors` 948 option of linkgit:git-add[1]. `add.ignore-errors` is deprecated, 949 as it does not follow the usual naming convention for configuration 950 variables. 951 952alias.*:: 953 Command aliases for the linkgit:git[1] command wrapper - e.g. 954 after defining "alias.last = cat-file commit HEAD", the invocation 955 "git last" is equivalent to "git cat-file commit HEAD". To avoid 956 confusion and troubles with script usage, aliases that 957 hide existing Git commands are ignored. Arguments are split by 958 spaces, the usual shell quoting and escaping is supported. 959 A quote pair or a backslash can be used to quote them. 960+ 961If the alias expansion is prefixed with an exclamation point, 962it will be treated as a shell command. For example, defining 963"alias.new = !gitk --all --not ORIG_HEAD", the invocation 964"git new" is equivalent to running the shell command 965"gitk --all --not ORIG_HEAD". Note that shell commands will be 966executed from the top-level directory of a repository, which may 967not necessarily be the current directory. 968`GIT_PREFIX` is set as returned by running 'git rev-parse --show-prefix' 969from the original current directory. See linkgit:git-rev-parse[1]. 970 971am.keepcr:: 972 If true, git-am will call git-mailsplit for patches in mbox format 973 with parameter `--keep-cr`. In this case git-mailsplit will 974 not remove `\r` from lines ending with `\r\n`. Can be overridden 975 by giving `--no-keep-cr` from the command line. 976 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 977 978am.threeWay:: 979 By default, `git am` will fail if the patch does not apply cleanly. When 980 set to true, this setting tells `git am` to fall back on 3-way merge if 981 the patch records the identity of blobs it is supposed to apply to and 982 we have those blobs available locally (equivalent to giving the `--3way` 983 option from the command line). Defaults to `false`. 984 See linkgit:git-am[1]. 985 986apply.ignoreWhitespace:: 987 When set to 'change', tells 'git apply' to ignore changes in 988 whitespace, in the same way as the `--ignore-space-change` 989 option. 990 When set to one of: no, none, never, false tells 'git apply' to 991 respect all whitespace differences. 992 See linkgit:git-apply[1]. 993 994apply.whitespace:: 995 Tells 'git apply' how to handle whitespaces, in the same way 996 as the `--whitespace` option. See linkgit:git-apply[1]. 997 998blame.blankBoundary:: 999 Show blank commit object name for boundary commits in1000 linkgit:git-blame[1]. This option defaults to false.10011002blame.coloring::1003 This determines the coloring scheme to be applied to blame1004 output. It can be 'repeatedLines', 'highlightRecent',1005 or 'none' which is the default.10061007blame.date::1008 Specifies the format used to output dates in linkgit:git-blame[1].1009 If unset the iso format is used. For supported values,1010 see the discussion of the `--date` option at linkgit:git-log[1].10111012blame.showEmail::1013 Show the author email instead of author name in linkgit:git-blame[1].1014 This option defaults to false.10151016blame.showRoot::1017 Do not treat root commits as boundaries in linkgit:git-blame[1].1018 This option defaults to false.10191020branch.autoSetupMerge::1021 Tells 'git branch' and 'git checkout' to set up new branches1022 so that linkgit:git-pull[1] will appropriately merge from the1023 starting point branch. Note that even if this option is not set,1024 this behavior can be chosen per-branch using the `--track`1025 and `--no-track` options. The valid settings are: `false` -- no1026 automatic setup is done; `true` -- automatic setup is done when the1027 starting point is a remote-tracking branch; `always` --1028 automatic setup is done when the starting point is either a1029 local branch or remote-tracking1030 branch. This option defaults to true.10311032branch.autoSetupRebase::1033 When a new branch is created with 'git branch' or 'git checkout'1034 that tracks another branch, this variable tells Git to set1035 up pull to rebase instead of merge (see "branch.<name>.rebase").1036 When `never`, rebase is never automatically set to true.1037 When `local`, rebase is set to true for tracked branches of1038 other local branches.1039 When `remote`, rebase is set to true for tracked branches of1040 remote-tracking branches.1041 When `always`, rebase will be set to true for all tracking1042 branches.1043 See "branch.autoSetupMerge" for details on how to set up a1044 branch to track another branch.1045 This option defaults to never.10461047branch.<name>.remote::1048 When on branch <name>, it tells 'git fetch' and 'git push'1049 which remote to fetch from/push to. The remote to push to1050 may be overridden with `remote.pushDefault` (for all branches).1051 The remote to push to, for the current branch, may be further1052 overridden by `branch.<name>.pushRemote`. If no remote is1053 configured, or if you are not on any branch, it defaults to1054 `origin` for fetching and `remote.pushDefault` for pushing.1055 Additionally, `.` (a period) is the current local repository1056 (a dot-repository), see `branch.<name>.merge`'s final note below.10571058branch.<name>.pushRemote::1059 When on branch <name>, it overrides `branch.<name>.remote` for1060 pushing. It also overrides `remote.pushDefault` for pushing1061 from branch <name>. When you pull from one place (e.g. your1062 upstream) and push to another place (e.g. your own publishing1063 repository), you would want to set `remote.pushDefault` to1064 specify the remote to push to for all branches, and use this1065 option to override it for a specific branch.10661067branch.<name>.merge::1068 Defines, together with branch.<name>.remote, the upstream branch1069 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which1070 branch to merge and can also affect 'git push' (see push.default).1071 When in branch <name>, it tells 'git fetch' the default1072 refspec to be marked for merging in FETCH_HEAD. The value is1073 handled like the remote part of a refspec, and must match a1074 ref which is fetched from the remote given by1075 "branch.<name>.remote".1076 The merge information is used by 'git pull' (which at first calls1077 'git fetch') to lookup the default branch for merging. Without1078 this option, 'git pull' defaults to merge the first refspec fetched.1079 Specify multiple values to get an octopus merge.1080 If you wish to setup 'git pull' so that it merges into <name> from1081 another branch in the local repository, you can point1082 branch.<name>.merge to the desired branch, and use the relative path1083 setting `.` (a period) for branch.<name>.remote.10841085branch.<name>.mergeOptions::1086 Sets default options for merging into branch <name>. The syntax and1087 supported options are the same as those of linkgit:git-merge[1], but1088 option values containing whitespace characters are currently not1089 supported.10901091branch.<name>.rebase::1092 When true, rebase the branch <name> on top of the fetched branch,1093 instead of merging the default branch from the default remote when1094 "git pull" is run. See "pull.rebase" for doing this in a non1095 branch-specific manner.1096+1097When `merges`, pass the `--rebase-merges` option to 'git rebase'1098so that the local merge commits are included in the rebase (see1099linkgit:git-rebase[1] for details).1100+1101When preserve, also pass `--preserve-merges` along to 'git rebase'1102so that locally committed merge commits will not be flattened1103by running 'git pull'.1104+1105When the value is `interactive`, the rebase is run in interactive mode.1106+1107*NOTE*: this is a possibly dangerous operation; do *not* use1108it unless you understand the implications (see linkgit:git-rebase[1]1109for details).11101111branch.<name>.description::1112 Branch description, can be edited with1113 `git branch --edit-description`. Branch description is1114 automatically added in the format-patch cover letter or1115 request-pull summary.11161117browser.<tool>.cmd::1118 Specify the command to invoke the specified browser. The1119 specified command is evaluated in shell with the URLs passed1120 as arguments. (See linkgit:git-web{litdd}browse[1].)11211122browser.<tool>.path::1123 Override the path for the given tool that may be used to1124 browse HTML help (see `-w` option in linkgit:git-help[1]) or a1125 working repository in gitweb (see linkgit:git-instaweb[1]).11261127checkout.defaultRemote::1128 When you run 'git checkout <something>' and only have one1129 remote, it may implicitly fall back on checking out and1130 tracking e.g. 'origin/<something>'. This stops working as soon1131 as you have more than one remote with a '<something>'1132 reference. This setting allows for setting the name of a1133 preferred remote that should always win when it comes to1134 disambiguation. The typical use-case is to set this to1135 `origin`.1136+1137Currently this is used by linkgit:git-checkout[1] when 'git checkout1138<something>' will checkout the '<something>' branch on another remote,1139and by linkgit:git-worktree[1] when 'git worktree add' refers to a1140remote branch. This setting might be used for other checkout-like1141commands or functionality in the future.11421143clean.requireForce::1144 A boolean to make git-clean do nothing unless given -f,1145 -i or -n. Defaults to true.11461147color.advice::1148 A boolean to enable/disable color in hints (e.g. when a push1149 failed, see `advice.*` for a list). May be set to `always`,1150 `false` (or `never`) or `auto` (or `true`), in which case colors1151 are used only when the error output goes to a terminal. If1152 unset, then the value of `color.ui` is used (`auto` by default).11531154color.advice.hint::1155 Use customized color for hints.11561157color.blame.highlightRecent::1158 This can be used to color the metadata of a blame line depending1159 on age of the line.1160+1161This setting should be set to a comma-separated list of color and date settings,1162starting and ending with a color, the dates should be set from oldest to newest.1163The metadata will be colored given the colors if the the line was introduced1164before the given timestamp, overwriting older timestamped colors.1165+1166Instead of an absolute timestamp relative timestamps work as well, e.g.11672.weeks.ago is valid to address anything older than 2 weeks.1168+1169It defaults to 'blue,12 month ago,white,1 month ago,red', which colors1170everything older than one year blue, recent changes between one month and1171one year old are kept white, and lines introduced within the last month are1172colored red.11731174color.blame.repeatedLines::1175 Use the customized color for the part of git-blame output that1176 is repeated meta information per line (such as commit id,1177 author name, date and timezone). Defaults to cyan.11781179color.branch::1180 A boolean to enable/disable color in the output of1181 linkgit:git-branch[1]. May be set to `always`,1182 `false` (or `never`) or `auto` (or `true`), in which case colors are used1183 only when the output is to a terminal. If unset, then the1184 value of `color.ui` is used (`auto` by default).11851186color.branch.<slot>::1187 Use customized color for branch coloration. `<slot>` is one of1188 `current` (the current branch), `local` (a local branch),1189 `remote` (a remote-tracking branch in refs/remotes/),1190 `upstream` (upstream tracking branch), `plain` (other1191 refs).11921193color.diff::1194 Whether to use ANSI escape sequences to add color to patches.1195 If this is set to `always`, linkgit:git-diff[1],1196 linkgit:git-log[1], and linkgit:git-show[1] will use color1197 for all patches. If it is set to `true` or `auto`, those1198 commands will only use color when output is to the terminal.1199 If unset, then the value of `color.ui` is used (`auto` by1200 default).1201+1202This does not affect linkgit:git-format-patch[1] or the1203'git-diff-{asterisk}' plumbing commands. Can be overridden on the1204command line with the `--color[=<when>]` option.12051206diff.colorMoved::1207 If set to either a valid `<mode>` or a true value, moved lines1208 in a diff are colored differently, for details of valid modes1209 see '--color-moved' in linkgit:git-diff[1]. If simply set to1210 true the default color mode will be used. When set to false,1211 moved lines are not colored.12121213diff.colorMovedWS::1214 When moved lines are colored using e.g. the `diff.colorMoved` setting,1215 this option controls the `<mode>` how spaces are treated1216 for details of valid modes see '--color-moved-ws' in linkgit:git-diff[1].12171218color.diff.<slot>::1219 Use customized color for diff colorization. `<slot>` specifies1220 which part of the patch to use the specified color, and is one1221 of `context` (context text - `plain` is a historical synonym),1222 `meta` (metainformation), `frag`1223 (hunk header), 'func' (function in hunk header), `old` (removed lines),1224 `new` (added lines), `commit` (commit headers), `whitespace`1225 (highlighting whitespace errors), `oldMoved` (deleted lines),1226 `newMoved` (added lines), `oldMovedDimmed`, `oldMovedAlternative`,1227 `oldMovedAlternativeDimmed`, `newMovedDimmed`, `newMovedAlternative`1228 `newMovedAlternativeDimmed` (See the '<mode>'1229 setting of '--color-moved' in linkgit:git-diff[1] for details),1230 `contextDimmed`, `oldDimmed`, `newDimmed`, `contextBold`,1231 `oldBold`, and `newBold` (see linkgit:git-range-diff[1] for details).12321233color.decorate.<slot>::1234 Use customized color for 'git log --decorate' output. `<slot>` is one1235 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local1236 branches, remote-tracking branches, tags, stash and HEAD, respectively1237 and `grafted` for grafted commits.12381239color.grep::1240 When set to `always`, always highlight matches. When `false` (or1241 `never`), never. When set to `true` or `auto`, use color only1242 when the output is written to the terminal. If unset, then the1243 value of `color.ui` is used (`auto` by default).12441245color.grep.<slot>::1246 Use customized color for grep colorization. `<slot>` specifies which1247 part of the line to use the specified color, and is one of1248+1249--1250`context`;;1251 non-matching text in context lines (when using `-A`, `-B`, or `-C`)1252`filename`;;1253 filename prefix (when not using `-h`)1254`function`;;1255 function name lines (when using `-p`)1256`lineNumber`;;1257 line number prefix (when using `-n`)1258`column`;;1259 column number prefix (when using `--column`)1260`match`;;1261 matching text (same as setting `matchContext` and `matchSelected`)1262`matchContext`;;1263 matching text in context lines1264`matchSelected`;;1265 matching text in selected lines1266`selected`;;1267 non-matching text in selected lines1268`separator`;;1269 separators between fields on a line (`:`, `-`, and `=`)1270 and between hunks (`--`)1271--12721273color.interactive::1274 When set to `always`, always use colors for interactive prompts1275 and displays (such as those used by "git-add --interactive" and1276 "git-clean --interactive"). When false (or `never`), never.1277 When set to `true` or `auto`, use colors only when the output is1278 to the terminal. If unset, then the value of `color.ui` is1279 used (`auto` by default).12801281color.interactive.<slot>::1282 Use customized color for 'git add --interactive' and 'git clean1283 --interactive' output. `<slot>` may be `prompt`, `header`, `help`1284 or `error`, for four distinct types of normal output from1285 interactive commands.12861287color.pager::1288 A boolean to enable/disable colored output when the pager is in1289 use (default is true).12901291color.push::1292 A boolean to enable/disable color in push errors. May be set to1293 `always`, `false` (or `never`) or `auto` (or `true`), in which1294 case colors are used only when the error output goes to a terminal.1295 If unset, then the value of `color.ui` is used (`auto` by default).12961297color.push.error::1298 Use customized color for push errors.12991300color.remote::1301 If set, keywords at the start of the line are highlighted. The1302 keywords are "error", "warning", "hint" and "success", and are1303 matched case-insensitively. May be set to `always`, `false` (or1304 `never`) or `auto` (or `true`). If unset, then the value of1305 `color.ui` is used (`auto` by default).13061307color.remote.<slot>::1308 Use customized color for each remote keyword. `<slot>` may be1309 `hint`, `warning`, `success` or `error` which match the1310 corresponding keyword.13111312color.showBranch::1313 A boolean to enable/disable color in the output of1314 linkgit:git-show-branch[1]. May be set to `always`,1315 `false` (or `never`) or `auto` (or `true`), in which case colors are used1316 only when the output is to a terminal. If unset, then the1317 value of `color.ui` is used (`auto` by default).13181319color.status::1320 A boolean to enable/disable color in the output of1321 linkgit:git-status[1]. May be set to `always`,1322 `false` (or `never`) or `auto` (or `true`), in which case colors are used1323 only when the output is to a terminal. If unset, then the1324 value of `color.ui` is used (`auto` by default).13251326color.status.<slot>::1327 Use customized color for status colorization. `<slot>` is1328 one of `header` (the header text of the status message),1329 `added` or `updated` (files which are added but not committed),1330 `changed` (files which are changed but not added in the index),1331 `untracked` (files which are not tracked by Git),1332 `branch` (the current branch),1333 `nobranch` (the color the 'no branch' warning is shown in, defaulting1334 to red),1335 `localBranch` or `remoteBranch` (the local and remote branch names,1336 respectively, when branch and tracking information is displayed in the1337 status short-format), or1338 `unmerged` (files which have unmerged changes).13391340color.transport::1341 A boolean to enable/disable color when pushes are rejected. May be1342 set to `always`, `false` (or `never`) or `auto` (or `true`), in which1343 case colors are used only when the error output goes to a terminal.1344 If unset, then the value of `color.ui` is used (`auto` by default).13451346color.transport.rejected::1347 Use customized color when a push was rejected.13481349color.ui::1350 This variable determines the default value for variables such1351 as `color.diff` and `color.grep` that control the use of color1352 per command family. Its scope will expand as more commands learn1353 configuration to set a default for the `--color` option. Set it1354 to `false` or `never` if you prefer Git commands not to use1355 color unless enabled explicitly with some other configuration1356 or the `--color` option. Set it to `always` if you want all1357 output not intended for machine consumption to use color, to1358 `true` or `auto` (this is the default since Git 1.8.4) if you1359 want such output to use color when written to the terminal.13601361column.ui::1362 Specify whether supported commands should output in columns.1363 This variable consists of a list of tokens separated by spaces1364 or commas:1365+1366These options control when the feature should be enabled1367(defaults to 'never'):1368+1369--1370`always`;;1371 always show in columns1372`never`;;1373 never show in columns1374`auto`;;1375 show in columns if the output is to the terminal1376--1377+1378These options control layout (defaults to 'column'). Setting any1379of these implies 'always' if none of 'always', 'never', or 'auto' are1380specified.1381+1382--1383`column`;;1384 fill columns before rows1385`row`;;1386 fill rows before columns1387`plain`;;1388 show in one column1389--1390+1391Finally, these options can be combined with a layout option (defaults1392to 'nodense'):1393+1394--1395`dense`;;1396 make unequal size columns to utilize more space1397`nodense`;;1398 make equal size columns1399--14001401column.branch::1402 Specify whether to output branch listing in `git branch` in columns.1403 See `column.ui` for details.14041405column.clean::1406 Specify the layout when list items in `git clean -i`, which always1407 shows files and directories in columns. See `column.ui` for details.14081409column.status::1410 Specify whether to output untracked files in `git status` in columns.1411 See `column.ui` for details.14121413column.tag::1414 Specify whether to output tag listing in `git tag` in columns.1415 See `column.ui` for details.14161417commit.cleanup::1418 This setting overrides the default of the `--cleanup` option in1419 `git commit`. See linkgit:git-commit[1] for details. Changing the1420 default can be useful when you always want to keep lines that begin1421 with comment character `#` in your log message, in which case you1422 would do `git config commit.cleanup whitespace` (note that you will1423 have to remove the help lines that begin with `#` in the commit log1424 template yourself, if you do this).14251426commit.gpgSign::14271428 A boolean to specify whether all commits should be GPG signed.1429 Use of this option when doing operations such as rebase can1430 result in a large number of commits being signed. It may be1431 convenient to use an agent to avoid typing your GPG passphrase1432 several times.14331434commit.status::1435 A boolean to enable/disable inclusion of status information in the1436 commit message template when using an editor to prepare the commit1437 message. Defaults to true.14381439commit.template::1440 Specify the pathname of a file to use as the template for1441 new commit messages.14421443commit.verbose::1444 A boolean or int to specify the level of verbose with `git commit`.1445 See linkgit:git-commit[1].14461447credential.helper::1448 Specify an external helper to be called when a username or1449 password credential is needed; the helper may consult external1450 storage to avoid prompting the user for the credentials. Note1451 that multiple helpers may be defined. See linkgit:gitcredentials[7]1452 for details.14531454credential.useHttpPath::1455 When acquiring credentials, consider the "path" component of an http1456 or https URL to be important. Defaults to false. See1457 linkgit:gitcredentials[7] for more information.14581459credential.username::1460 If no username is set for a network authentication, use this username1461 by default. See credential.<context>.* below, and1462 linkgit:gitcredentials[7].14631464credential.<url>.*::1465 Any of the credential.* options above can be applied selectively to1466 some credentials. For example "credential.https://example.com.username"1467 would set the default username only for https connections to1468 example.com. See linkgit:gitcredentials[7] for details on how URLs are1469 matched.14701471credentialCache.ignoreSIGHUP::1472 Tell git-credential-cache--daemon to ignore SIGHUP, instead of quitting.14731474completion.commands::1475 This is only used by git-completion.bash to add or remove1476 commands from the list of completed commands. Normally only1477 porcelain commands and a few select others are completed. You1478 can add more commands, separated by space, in this1479 variable. Prefixing the command with '-' will remove it from1480 the existing list.14811482include::diff-config.txt[]14831484difftool.<tool>.path::1485 Override the path for the given tool. This is useful in case1486 your tool is not in the PATH.14871488difftool.<tool>.cmd::1489 Specify the command to invoke the specified diff tool.1490 The specified command is evaluated in shell with the following1491 variables available: 'LOCAL' is set to the name of the temporary1492 file containing the contents of the diff pre-image and 'REMOTE'1493 is set to the name of the temporary file containing the contents1494 of the diff post-image.14951496difftool.prompt::1497 Prompt before each invocation of the diff tool.14981499fastimport.unpackLimit::1500 If the number of objects imported by linkgit:git-fast-import[1]1501 is below this limit, then the objects will be unpacked into1502 loose object files. However if the number of imported objects1503 equals or exceeds this limit then the pack will be stored as a1504 pack. Storing the pack from a fast-import can make the import1505 operation complete faster, especially on slow filesystems. If1506 not set, the value of `transfer.unpackLimit` is used instead.15071508fetch.recurseSubmodules::1509 This option can be either set to a boolean value or to 'on-demand'.1510 Setting it to a boolean changes the behavior of fetch and pull to1511 unconditionally recurse into submodules when set to true or to not1512 recurse at all when set to false. When set to 'on-demand' (the default1513 value), fetch and pull will only recurse into a populated submodule1514 when its superproject retrieves a commit that updates the submodule's1515 reference.15161517fetch.fsckObjects::1518 If it is set to true, git-fetch-pack will check all fetched1519 objects. See `transfer.fsckObjects` for what's1520 checked. Defaults to false. If not set, the value of1521 `transfer.fsckObjects` is used instead.15221523fetch.fsck.<msg-id>::1524 Acts like `fsck.<msg-id>`, but is used by1525 linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See1526 the `fsck.<msg-id>` documentation for details.15271528fetch.fsck.skipList::1529 Acts like `fsck.skipList`, but is used by1530 linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See1531 the `fsck.skipList` documentation for details.15321533fetch.unpackLimit::1534 If the number of objects fetched over the Git native1535 transfer is below this1536 limit, then the objects will be unpacked into loose object1537 files. However if the number of received objects equals or1538 exceeds this limit then the received pack will be stored as1539 a pack, after adding any missing delta bases. Storing the1540 pack from a push can make the push operation complete faster,1541 especially on slow filesystems. If not set, the value of1542 `transfer.unpackLimit` is used instead.15431544fetch.prune::1545 If true, fetch will automatically behave as if the `--prune`1546 option was given on the command line. See also `remote.<name>.prune`1547 and the PRUNING section of linkgit:git-fetch[1].15481549fetch.pruneTags::1550 If true, fetch will automatically behave as if the1551 `refs/tags/*:refs/tags/*` refspec was provided when pruning,1552 if not set already. This allows for setting both this option1553 and `fetch.prune` to maintain a 1=1 mapping to upstream1554 refs. See also `remote.<name>.pruneTags` and the PRUNING1555 section of linkgit:git-fetch[1].15561557fetch.output::1558 Control how ref update status is printed. Valid values are1559 `full` and `compact`. Default value is `full`. See section1560 OUTPUT in linkgit:git-fetch[1] for detail.15611562fetch.negotiationAlgorithm::1563 Control how information about the commits in the local repository is1564 sent when negotiating the contents of the packfile to be sent by the1565 server. Set to "skipping" to use an algorithm that skips commits in an1566 effort to converge faster, but may result in a larger-than-necessary1567 packfile; The default is "default" which instructs Git to use the default algorithm1568 that never skips commits (unless the server has acknowledged it or one1569 of its descendants).1570 Unknown values will cause 'git fetch' to error out.1571+1572See also the `--negotiation-tip` option for linkgit:git-fetch[1].15731574format.attach::1575 Enable multipart/mixed attachments as the default for1576 'format-patch'. The value can also be a double quoted string1577 which will enable attachments as the default and set the1578 value as the boundary. See the --attach option in1579 linkgit:git-format-patch[1].15801581format.from::1582 Provides the default value for the `--from` option to format-patch.1583 Accepts a boolean value, or a name and email address. If false,1584 format-patch defaults to `--no-from`, using commit authors directly in1585 the "From:" field of patch mails. If true, format-patch defaults to1586 `--from`, using your committer identity in the "From:" field of patch1587 mails and including a "From:" field in the body of the patch mail if1588 different. If set to a non-boolean value, format-patch uses that1589 value instead of your committer identity. Defaults to false.15901591format.numbered::1592 A boolean which can enable or disable sequence numbers in patch1593 subjects. It defaults to "auto" which enables it only if there1594 is more than one patch. It can be enabled or disabled for all1595 messages by setting it to "true" or "false". See --numbered1596 option in linkgit:git-format-patch[1].15971598format.headers::1599 Additional email headers to include in a patch to be submitted1600 by mail. See linkgit:git-format-patch[1].16011602format.to::1603format.cc::1604 Additional recipients to include in a patch to be submitted1605 by mail. See the --to and --cc options in1606 linkgit:git-format-patch[1].16071608format.subjectPrefix::1609 The default for format-patch is to output files with the '[PATCH]'1610 subject prefix. Use this variable to change that prefix.16111612format.signature::1613 The default for format-patch is to output a signature containing1614 the Git version number. Use this variable to change that default.1615 Set this variable to the empty string ("") to suppress1616 signature generation.16171618format.signatureFile::1619 Works just like format.signature except the contents of the1620 file specified by this variable will be used as the signature.16211622format.suffix::1623 The default for format-patch is to output files with the suffix1624 `.patch`. Use this variable to change that suffix (make sure to1625 include the dot if you want it).16261627format.pretty::1628 The default pretty format for log/show/whatchanged command,1629 See linkgit:git-log[1], linkgit:git-show[1],1630 linkgit:git-whatchanged[1].16311632format.thread::1633 The default threading style for 'git format-patch'. Can be1634 a boolean value, or `shallow` or `deep`. `shallow` threading1635 makes every mail a reply to the head of the series,1636 where the head is chosen from the cover letter, the1637 `--in-reply-to`, and the first patch mail, in this order.1638 `deep` threading makes every mail a reply to the previous one.1639 A true boolean value is the same as `shallow`, and a false1640 value disables threading.16411642format.signOff::1643 A boolean value which lets you enable the `-s/--signoff` option of1644 format-patch by default. *Note:* Adding the Signed-off-by: line to a1645 patch should be a conscious act and means that you certify you have1646 the rights to submit this work under the same open source license.1647 Please see the 'SubmittingPatches' document for further discussion.16481649format.coverLetter::1650 A boolean that controls whether to generate a cover-letter when1651 format-patch is invoked, but in addition can be set to "auto", to1652 generate a cover-letter only when there's more than one patch.16531654format.outputDirectory::1655 Set a custom directory to store the resulting files instead of the1656 current working directory.16571658format.useAutoBase::1659 A boolean value which lets you enable the `--base=auto` option of1660 format-patch by default.16611662filter.<driver>.clean::1663 The command which is used to convert the content of a worktree1664 file to a blob upon checkin. See linkgit:gitattributes[5] for1665 details.16661667filter.<driver>.smudge::1668 The command which is used to convert the content of a blob1669 object to a worktree file upon checkout. See1670 linkgit:gitattributes[5] for details.16711672fsck.<msg-id>::1673 During fsck git may find issues with legacy data which1674 wouldn't be generated by current versions of git, and which1675 wouldn't be sent over the wire if `transfer.fsckObjects` was1676 set. This feature is intended to support working with legacy1677 repositories containing such data.1678+1679Setting `fsck.<msg-id>` will be picked up by linkgit:git-fsck[1], but1680to accept pushes of such data set `receive.fsck.<msg-id>` instead, or1681to clone or fetch it set `fetch.fsck.<msg-id>`.1682+1683The rest of the documentation discusses `fsck.*` for brevity, but the1684same applies for the corresponding `receive.fsck.*` and1685`fetch.<msg-id>.*`. variables.1686+1687Unlike variables like `color.ui` and `core.editor` the1688`receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>` variables will not1689fall back on the `fsck.<msg-id>` configuration if they aren't set. To1690uniformly configure the same fsck settings in different circumstances1691all three of them they must all set to the same values.1692+1693When `fsck.<msg-id>` is set, errors can be switched to warnings and1694vice versa by configuring the `fsck.<msg-id>` setting where the1695`<msg-id>` is the fsck message ID and the value is one of `error`,1696`warn` or `ignore`. For convenience, fsck prefixes the error/warning1697with the message ID, e.g. "missingEmail: invalid author/committer line1698- missing email" means that setting `fsck.missingEmail = ignore` will1699hide that issue.1700+1701In general, it is better to enumerate existing objects with problems1702with `fsck.skipList`, instead of listing the kind of breakages these1703problematic objects share to be ignored, as doing the latter will1704allow new instances of the same breakages go unnoticed.1705+1706Setting an unknown `fsck.<msg-id>` value will cause fsck to die, but1707doing the same for `receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>`1708will only cause git to warn.17091710fsck.skipList::1711 The path to a sorted list of object names (i.e. one SHA-1 per1712 line) that are known to be broken in a non-fatal way and should1713 be ignored. This feature is useful when an established project1714 should be accepted despite early commits containing errors that1715 can be safely ignored such as invalid committer email addresses.1716 Note: corrupt objects cannot be skipped with this setting.1717+1718Like `fsck.<msg-id>` this variable has corresponding1719`receive.fsck.skipList` and `fetch.fsck.skipList` variants.1720+1721Unlike variables like `color.ui` and `core.editor` the1722`receive.fsck.skipList` and `fetch.fsck.skipList` variables will not1723fall back on the `fsck.skipList` configuration if they aren't set. To1724uniformly configure the same fsck settings in different circumstances1725all three of them they must all set to the same values.17261727gc.aggressiveDepth::1728 The depth parameter used in the delta compression1729 algorithm used by 'git gc --aggressive'. This defaults1730 to 50.17311732gc.aggressiveWindow::1733 The window size parameter used in the delta compression1734 algorithm used by 'git gc --aggressive'. This defaults1735 to 250.17361737gc.auto::1738 When there are approximately more than this many loose1739 objects in the repository, `git gc --auto` will pack them.1740 Some Porcelain commands use this command to perform a1741 light-weight garbage collection from time to time. The1742 default value is 6700. Setting this to 0 disables it.17431744gc.autoPackLimit::1745 When there are more than this many packs that are not1746 marked with `*.keep` file in the repository, `git gc1747 --auto` consolidates them into one larger pack. The1748 default value is 50. Setting this to 0 disables it.17491750gc.autoDetach::1751 Make `git gc --auto` return immediately and run in background1752 if the system supports it. Default is true.17531754gc.bigPackThreshold::1755 If non-zero, all packs larger than this limit are kept when1756 `git gc` is run. This is very similar to `--keep-base-pack`1757 except that all packs that meet the threshold are kept, not1758 just the base pack. Defaults to zero. Common unit suffixes of1759 'k', 'm', or 'g' are supported.1760+1761Note that if the number of kept packs is more than gc.autoPackLimit,1762this configuration variable is ignored, all packs except the base pack1763will be repacked. After this the number of packs should go below1764gc.autoPackLimit and gc.bigPackThreshold should be respected again.17651766gc.logExpiry::1767 If the file gc.log exists, then `git gc --auto` won't run1768 unless that file is more than 'gc.logExpiry' old. Default is1769 "1.day". See `gc.pruneExpire` for more ways to specify its1770 value.17711772gc.packRefs::1773 Running `git pack-refs` in a repository renders it1774 unclonable by Git versions prior to 1.5.1.2 over dumb1775 transports such as HTTP. This variable determines whether1776 'git gc' runs `git pack-refs`. This can be set to `notbare`1777 to enable it within all non-bare repos or it can be set to a1778 boolean value. The default is `true`.17791780gc.pruneExpire::1781 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1782 Override the grace period with this config variable. The value1783 "now" may be used to disable this grace period and always prune1784 unreachable objects immediately, or "never" may be used to1785 suppress pruning. This feature helps prevent corruption when1786 'git gc' runs concurrently with another process writing to the1787 repository; see the "NOTES" section of linkgit:git-gc[1].17881789gc.worktreePruneExpire::1790 When 'git gc' is run, it calls1791 'git worktree prune --expire 3.months.ago'.1792 This config variable can be used to set a different grace1793 period. The value "now" may be used to disable the grace1794 period and prune `$GIT_DIR/worktrees` immediately, or "never"1795 may be used to suppress pruning.17961797gc.reflogExpire::1798gc.<pattern>.reflogExpire::1799 'git reflog expire' removes reflog entries older than1800 this time; defaults to 90 days. The value "now" expires all1801 entries immediately, and "never" suppresses expiration1802 altogether. With "<pattern>" (e.g.1803 "refs/stash") in the middle the setting applies only to1804 the refs that match the <pattern>.18051806gc.reflogExpireUnreachable::1807gc.<pattern>.reflogExpireUnreachable::1808 'git reflog expire' removes reflog entries older than1809 this time and are not reachable from the current tip;1810 defaults to 30 days. The value "now" expires all entries1811 immediately, and "never" suppresses expiration altogether.1812 With "<pattern>" (e.g. "refs/stash")1813 in the middle, the setting applies only to the refs that1814 match the <pattern>.18151816gc.rerereResolved::1817 Records of conflicted merge you resolved earlier are1818 kept for this many days when 'git rerere gc' is run.1819 You can also use more human-readable "1.month.ago", etc.1820 The default is 60 days. See linkgit:git-rerere[1].18211822gc.rerereUnresolved::1823 Records of conflicted merge you have not resolved are1824 kept for this many days when 'git rerere gc' is run.1825 You can also use more human-readable "1.month.ago", etc.1826 The default is 15 days. See linkgit:git-rerere[1].18271828gitcvs.commitMsgAnnotation::1829 Append this string to each commit message. Set to empty string1830 to disable this feature. Defaults to "via git-CVS emulator".18311832gitcvs.enabled::1833 Whether the CVS server interface is enabled for this repository.1834 See linkgit:git-cvsserver[1].18351836gitcvs.logFile::1837 Path to a log file where the CVS server interface well... logs1838 various stuff. See linkgit:git-cvsserver[1].18391840gitcvs.usecrlfattr::1841 If true, the server will look up the end-of-line conversion1842 attributes for files to determine the `-k` modes to use. If1843 the attributes force Git to treat a file as text,1844 the `-k` mode will be left blank so CVS clients will1845 treat it as text. If they suppress text conversion, the file1846 will be set with '-kb' mode, which suppresses any newline munging1847 the client might otherwise do. If the attributes do not allow1848 the file type to be determined, then `gitcvs.allBinary` is1849 used. See linkgit:gitattributes[5].18501851gitcvs.allBinary::1852 This is used if `gitcvs.usecrlfattr` does not resolve1853 the correct '-kb' mode to use. If true, all1854 unresolved files are sent to the client in1855 mode '-kb'. This causes the client to treat them1856 as binary files, which suppresses any newline munging it1857 otherwise might do. Alternatively, if it is set to "guess",1858 then the contents of the file are examined to decide if1859 it is binary, similar to `core.autocrlf`.18601861gitcvs.dbName::1862 Database used by git-cvsserver to cache revision information1863 derived from the Git repository. The exact meaning depends on the1864 used database driver, for SQLite (which is the default driver) this1865 is a filename. Supports variable substitution (see1866 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1867 Default: '%Ggitcvs.%m.sqlite'18681869gitcvs.dbDriver::1870 Used Perl DBI driver. You can specify any available driver1871 for this here, but it might not work. git-cvsserver is tested1872 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1873 reported *not* to work with 'DBD::mysql'. Experimental feature.1874 May not contain double colons (`:`). Default: 'SQLite'.1875 See linkgit:git-cvsserver[1].18761877gitcvs.dbUser, gitcvs.dbPass::1878 Database user and password. Only useful if setting `gitcvs.dbDriver`,1879 since SQLite has no concept of database users and/or passwords.1880 'gitcvs.dbUser' supports variable substitution (see1881 linkgit:git-cvsserver[1] for details).18821883gitcvs.dbTableNamePrefix::1884 Database table name prefix. Prepended to the names of any1885 database tables used, allowing a single database to be used1886 for several repositories. Supports variable substitution (see1887 linkgit:git-cvsserver[1] for details). Any non-alphabetic1888 characters will be replaced with underscores.18891890All gitcvs variables except for `gitcvs.usecrlfattr` and1891`gitcvs.allBinary` can also be specified as1892'gitcvs.<access_method>.<varname>' (where 'access_method'1893is one of "ext" and "pserver") to make them apply only for the given1894access method.18951896gitweb.category::1897gitweb.description::1898gitweb.owner::1899gitweb.url::1900 See linkgit:gitweb[1] for description.19011902gitweb.avatar::1903gitweb.blame::1904gitweb.grep::1905gitweb.highlight::1906gitweb.patches::1907gitweb.pickaxe::1908gitweb.remote_heads::1909gitweb.showSizes::1910gitweb.snapshot::1911 See linkgit:gitweb.conf[5] for description.19121913grep.lineNumber::1914 If set to true, enable `-n` option by default.19151916grep.column::1917 If set to true, enable the `--column` option by default.19181919grep.patternType::1920 Set the default matching behavior. Using a value of 'basic', 'extended',1921 'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,1922 `--fixed-strings`, or `--perl-regexp` option accordingly, while the1923 value 'default' will return to the default matching behavior.19241925grep.extendedRegexp::1926 If set to true, enable `--extended-regexp` option by default. This1927 option is ignored when the `grep.patternType` option is set to a value1928 other than 'default'.19291930grep.threads::1931 Number of grep worker threads to use.1932 See `grep.threads` in linkgit:git-grep[1] for more information.19331934grep.fallbackToNoIndex::1935 If set to true, fall back to git grep --no-index if git grep1936 is executed outside of a git repository. Defaults to false.19371938gpg.program::1939 Use this custom program instead of "`gpg`" found on `$PATH` when1940 making or verifying a PGP signature. The program must support the1941 same command-line interface as GPG, namely, to verify a detached1942 signature, "`gpg --verify $file - <$signature`" is run, and the1943 program is expected to signal a good signature by exiting with1944 code 0, and to generate an ASCII-armored detached signature, the1945 standard input of "`gpg -bsau $key`" is fed with the contents to be1946 signed, and the program is expected to send the result to its1947 standard output.19481949gpg.format::1950 Specifies which key format to use when signing with `--gpg-sign`.1951 Default is "openpgp" and another possible value is "x509".19521953gpg.<format>.program::1954 Use this to customize the program used for the signing format you1955 chose. (see `gpg.program` and `gpg.format`) `gpg.program` can still1956 be used as a legacy synonym for `gpg.openpgp.program`. The default1957 value for `gpg.x509.program` is "gpgsm".19581959gui.commitMsgWidth::1960 Defines how wide the commit message window is in the1961 linkgit:git-gui[1]. "75" is the default.19621963gui.diffContext::1964 Specifies how many context lines should be used in calls to diff1965 made by the linkgit:git-gui[1]. The default is "5".19661967gui.displayUntracked::1968 Determines if linkgit:git-gui[1] shows untracked files1969 in the file list. The default is "true".19701971gui.encoding::1972 Specifies the default encoding to use for displaying of1973 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1974 It can be overridden by setting the 'encoding' attribute1975 for relevant files (see linkgit:gitattributes[5]).1976 If this option is not set, the tools default to the1977 locale encoding.19781979gui.matchTrackingBranch::1980 Determines if new branches created with linkgit:git-gui[1] should1981 default to tracking remote branches with matching names or1982 not. Default: "false".19831984gui.newBranchTemplate::1985 Is used as suggested name when creating new branches using the1986 linkgit:git-gui[1].19871988gui.pruneDuringFetch::1989 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1990 performing a fetch. The default value is "false".19911992gui.trustmtime::1993 Determines if linkgit:git-gui[1] should trust the file modification1994 timestamp or not. By default the timestamps are not trusted.19951996gui.spellingDictionary::1997 Specifies the dictionary used for spell checking commit messages in1998 the linkgit:git-gui[1]. When set to "none" spell checking is turned1999 off.20002001gui.fastCopyBlame::2002 If true, 'git gui blame' uses `-C` instead of `-C -C` for original2003 location detection. It makes blame significantly faster on huge2004 repositories at the expense of less thorough copy detection.20052006gui.copyBlameThreshold::2007 Specifies the threshold to use in 'git gui blame' original location2008 detection, measured in alphanumeric characters. See the2009 linkgit:git-blame[1] manual for more information on copy detection.20102011gui.blamehistoryctx::2012 Specifies the radius of history context in days to show in2013 linkgit:gitk[1] for the selected commit, when the `Show History2014 Context` menu item is invoked from 'git gui blame'. If this2015 variable is set to zero, the whole history is shown.20162017guitool.<name>.cmd::2018 Specifies the shell command line to execute when the corresponding item2019 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is2020 mandatory for every tool. The command is executed from the root of2021 the working directory, and in the environment it receives the name of2022 the tool as `GIT_GUITOOL`, the name of the currently selected file as2023 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if2024 the head is detached, 'CUR_BRANCH' is empty).20252026guitool.<name>.needsFile::2027 Run the tool only if a diff is selected in the GUI. It guarantees2028 that 'FILENAME' is not empty.20292030guitool.<name>.noConsole::2031 Run the command silently, without creating a window to display its2032 output.20332034guitool.<name>.noRescan::2035 Don't rescan the working directory for changes after the tool2036 finishes execution.20372038guitool.<name>.confirm::2039 Show a confirmation dialog before actually running the tool.20402041guitool.<name>.argPrompt::2042 Request a string argument from the user, and pass it to the tool2043 through the `ARGS` environment variable. Since requesting an2044 argument implies confirmation, the 'confirm' option has no effect2045 if this is enabled. If the option is set to 'true', 'yes', or '1',2046 the dialog uses a built-in generic prompt; otherwise the exact2047 value of the variable is used.20482049guitool.<name>.revPrompt::2050 Request a single valid revision from the user, and set the2051 `REVISION` environment variable. In other aspects this option2052 is similar to 'argPrompt', and can be used together with it.20532054guitool.<name>.revUnmerged::2055 Show only unmerged branches in the 'revPrompt' subdialog.2056 This is useful for tools similar to merge or rebase, but not2057 for things like checkout or reset.20582059guitool.<name>.title::2060 Specifies the title to use for the prompt dialog. The default2061 is the tool name.20622063guitool.<name>.prompt::2064 Specifies the general prompt string to display at the top of2065 the dialog, before subsections for 'argPrompt' and 'revPrompt'.2066 The default value includes the actual command.20672068help.browser::2069 Specify the browser that will be used to display help in the2070 'web' format. See linkgit:git-help[1].20712072help.format::2073 Override the default help format used by linkgit:git-help[1].2074 Values 'man', 'info', 'web' and 'html' are supported. 'man' is2075 the default. 'web' and 'html' are the same.20762077help.autoCorrect::2078 Automatically correct and execute mistyped commands after2079 waiting for the given number of deciseconds (0.1 sec). If more2080 than one command can be deduced from the entered text, nothing2081 will be executed. If the value of this option is negative,2082 the corrected command will be executed immediately. If the2083 value is 0 - the command will be just shown but not executed.2084 This is the default.20852086help.htmlPath::2087 Specify the path where the HTML documentation resides. File system paths2088 and URLs are supported. HTML pages will be prefixed with this path when2089 help is displayed in the 'web' format. This defaults to the documentation2090 path of your Git installation.20912092http.proxy::2093 Override the HTTP proxy, normally configured using the 'http_proxy',2094 'https_proxy', and 'all_proxy' environment variables (see `curl(1)`). In2095 addition to the syntax understood by curl, it is possible to specify a2096 proxy string with a user name but no password, in which case git will2097 attempt to acquire one in the same way it does for other credentials. See2098 linkgit:gitcredentials[7] for more information. The syntax thus is2099 '[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden2100 on a per-remote basis; see remote.<name>.proxy21012102http.proxyAuthMethod::2103 Set the method with which to authenticate against the HTTP proxy. This2104 only takes effect if the configured proxy string contains a user name part2105 (i.e. is of the form 'user@host' or 'user@host:port'). This can be2106 overridden on a per-remote basis; see `remote.<name>.proxyAuthMethod`.2107 Both can be overridden by the `GIT_HTTP_PROXY_AUTHMETHOD` environment2108 variable. Possible values are:2109+2110--2111* `anyauth` - Automatically pick a suitable authentication method. It is2112 assumed that the proxy answers an unauthenticated request with a 4072113 status code and one or more Proxy-authenticate headers with supported2114 authentication methods. This is the default.2115* `basic` - HTTP Basic authentication2116* `digest` - HTTP Digest authentication; this prevents the password from being2117 transmitted to the proxy in clear text2118* `negotiate` - GSS-Negotiate authentication (compare the --negotiate option2119 of `curl(1)`)2120* `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`)2121--21222123http.emptyAuth::2124 Attempt authentication without seeking a username or password. This2125 can be used to attempt GSS-Negotiate authentication without specifying2126 a username in the URL, as libcurl normally requires a username for2127 authentication.21282129http.delegation::2130 Control GSSAPI credential delegation. The delegation is disabled2131 by default in libcurl since version 7.21.7. Set parameter to tell2132 the server what it is allowed to delegate when it comes to user2133 credentials. Used with GSS/kerberos. Possible values are:2134+2135--2136* `none` - Don't allow any delegation.2137* `policy` - Delegates if and only if the OK-AS-DELEGATE flag is set in the2138 Kerberos service ticket, which is a matter of realm policy.2139* `always` - Unconditionally allow the server to delegate.2140--214121422143http.extraHeader::2144 Pass an additional HTTP header when communicating with a server. If2145 more than one such entry exists, all of them are added as extra2146 headers. To allow overriding the settings inherited from the system2147 config, an empty value will reset the extra headers to the empty list.21482149http.cookieFile::2150 The pathname of a file containing previously stored cookie lines,2151 which should be used2152 in the Git http session, if they match the server. The file format2153 of the file to read cookies from should be plain HTTP headers or2154 the Netscape/Mozilla cookie file format (see `curl(1)`).2155 NOTE that the file specified with http.cookieFile is used only as2156 input unless http.saveCookies is set.21572158http.saveCookies::2159 If set, store cookies received during requests to the file specified by2160 http.cookieFile. Has no effect if http.cookieFile is unset.21612162http.sslVersion::2163 The SSL version to use when negotiating an SSL connection, if you2164 want to force the default. The available and default version2165 depend on whether libcurl was built against NSS or OpenSSL and the2166 particular configuration of the crypto library in use. Internally2167 this sets the 'CURLOPT_SSL_VERSION' option; see the libcurl2168 documentation for more details on the format of this option and2169 for the ssl version supported. Actually the possible values of2170 this option are:21712172 - sslv22173 - sslv32174 - tlsv12175 - tlsv1.02176 - tlsv1.12177 - tlsv1.22178 - tlsv1.321792180+2181Can be overridden by the `GIT_SSL_VERSION` environment variable.2182To force git to use libcurl's default ssl version and ignore any2183explicit http.sslversion option, set `GIT_SSL_VERSION` to the2184empty string.21852186http.sslCipherList::2187 A list of SSL ciphers to use when negotiating an SSL connection.2188 The available ciphers depend on whether libcurl was built against2189 NSS or OpenSSL and the particular configuration of the crypto2190 library in use. Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'2191 option; see the libcurl documentation for more details on the format2192 of this list.2193+2194Can be overridden by the `GIT_SSL_CIPHER_LIST` environment variable.2195To force git to use libcurl's default cipher list and ignore any2196explicit http.sslCipherList option, set `GIT_SSL_CIPHER_LIST` to the2197empty string.21982199http.sslVerify::2200 Whether to verify the SSL certificate when fetching or pushing2201 over HTTPS. Defaults to true. Can be overridden by the2202 `GIT_SSL_NO_VERIFY` environment variable.22032204http.sslCert::2205 File containing the SSL certificate when fetching or pushing2206 over HTTPS. Can be overridden by the `GIT_SSL_CERT` environment2207 variable.22082209http.sslKey::2210 File containing the SSL private key when fetching or pushing2211 over HTTPS. Can be overridden by the `GIT_SSL_KEY` environment2212 variable.22132214http.sslCertPasswordProtected::2215 Enable Git's password prompt for the SSL certificate. Otherwise2216 OpenSSL will prompt the user, possibly many times, if the2217 certificate or private key is encrypted. Can be overridden by the2218 `GIT_SSL_CERT_PASSWORD_PROTECTED` environment variable.22192220http.sslCAInfo::2221 File containing the certificates to verify the peer with when2222 fetching or pushing over HTTPS. Can be overridden by the2223 `GIT_SSL_CAINFO` environment variable.22242225http.sslCAPath::2226 Path containing files with the CA certificates to verify the peer2227 with when fetching or pushing over HTTPS. Can be overridden2228 by the `GIT_SSL_CAPATH` environment variable.22292230http.pinnedpubkey::2231 Public key of the https service. It may either be the filename of2232 a PEM or DER encoded public key file or a string starting with2233 'sha256//' followed by the base64 encoded sha256 hash of the2234 public key. See also libcurl 'CURLOPT_PINNEDPUBLICKEY'. git will2235 exit with an error if this option is set but not supported by2236 cURL.22372238http.sslTry::2239 Attempt to use AUTH SSL/TLS and encrypted data transfers2240 when connecting via regular FTP protocol. This might be needed2241 if the FTP server requires it for security reasons or you wish2242 to connect securely whenever remote FTP server supports it.2243 Default is false since it might trigger certificate verification2244 errors on misconfigured servers.22452246http.maxRequests::2247 How many HTTP requests to launch in parallel. Can be overridden2248 by the `GIT_HTTP_MAX_REQUESTS` environment variable. Default is 5.22492250http.minSessions::2251 The number of curl sessions (counted across slots) to be kept across2252 requests. They will not be ended with curl_easy_cleanup() until2253 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this2254 value will be capped at 1. Defaults to 1.22552256http.postBuffer::2257 Maximum size in bytes of the buffer used by smart HTTP2258 transports when POSTing data to the remote system.2259 For requests larger than this buffer size, HTTP/1.1 and2260 Transfer-Encoding: chunked is used to avoid creating a2261 massive pack file locally. Default is 1 MiB, which is2262 sufficient for most requests.22632264http.lowSpeedLimit, http.lowSpeedTime::2265 If the HTTP transfer speed is less than 'http.lowSpeedLimit'2266 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.2267 Can be overridden by the `GIT_HTTP_LOW_SPEED_LIMIT` and2268 `GIT_HTTP_LOW_SPEED_TIME` environment variables.22692270http.noEPSV::2271 A boolean which disables using of EPSV ftp command by curl.2272 This can helpful with some "poor" ftp servers which don't2273 support EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV`2274 environment variable. Default is false (curl will use EPSV).22752276http.userAgent::2277 The HTTP USER_AGENT string presented to an HTTP server. The default2278 value represents the version of the client Git such as git/1.7.1.2279 This option allows you to override this value to a more common value2280 such as Mozilla/4.0. This may be necessary, for instance, if2281 connecting through a firewall that restricts HTTP connections to a set2282 of common USER_AGENT strings (but not including those like git/1.7.1).2283 Can be overridden by the `GIT_HTTP_USER_AGENT` environment variable.22842285http.followRedirects::2286 Whether git should follow HTTP redirects. If set to `true`, git2287 will transparently follow any redirect issued by a server it2288 encounters. If set to `false`, git will treat all redirects as2289 errors. If set to `initial`, git will follow redirects only for2290 the initial request to a remote, but not for subsequent2291 follow-up HTTP requests. Since git uses the redirected URL as2292 the base for the follow-up requests, this is generally2293 sufficient. The default is `initial`.22942295http.<url>.*::2296 Any of the http.* options above can be applied selectively to some URLs.2297 For a config key to match a URL, each element of the config key is2298 compared to that of the URL, in the following order:2299+2300--2301. Scheme (e.g., `https` in `https://example.com/`). This field2302 must match exactly between the config key and the URL.23032304. Host/domain name (e.g., `example.com` in `https://example.com/`).2305 This field must match between the config key and the URL. It is2306 possible to specify a `*` as part of the host name to match all subdomains2307 at this level. `https://*.example.com/` for example would match2308 `https://foo.example.com/`, but not `https://foo.bar.example.com/`.23092310. Port number (e.g., `8080` in `http://example.com:8080/`).2311 This field must match exactly between the config key and the URL.2312 Omitted port numbers are automatically converted to the correct2313 default for the scheme before matching.23142315. Path (e.g., `repo.git` in `https://example.com/repo.git`). The2316 path field of the config key must match the path field of the URL2317 either exactly or as a prefix of slash-delimited path elements. This means2318 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only2319 match on a slash (`/`) boundary. Longer matches take precedence (so a config2320 key with path `foo/bar` is a better match to URL path `foo/bar` than a config2321 key with just path `foo/`).23222323. User name (e.g., `user` in `https://user@example.com/repo.git`). If2324 the config key has a user name it must match the user name in the2325 URL exactly. If the config key does not have a user name, that2326 config key will match a URL with any user name (including none),2327 but at a lower precedence than a config key with a user name.2328--2329+2330The list above is ordered by decreasing precedence; a URL that matches2331a config key's path is preferred to one that matches its user name. For example,2332if the URL is `https://user@example.com/foo/bar` a config key match of2333`https://example.com/foo` will be preferred over a config key match of2334`https://user@example.com`.2335+2336All URLs are normalized before attempting any matching (the password part,2337if embedded in the URL, is always ignored for matching purposes) so that2338equivalent URLs that are simply spelled differently will match properly.2339Environment variable settings always override any matches. The URLs that are2340matched against are those given directly to Git commands. This means any URLs2341visited as a result of a redirection do not participate in matching.23422343ssh.variant::2344 By default, Git determines the command line arguments to use2345 based on the basename of the configured SSH command (configured2346 using the environment variable `GIT_SSH` or `GIT_SSH_COMMAND` or2347 the config setting `core.sshCommand`). If the basename is2348 unrecognized, Git will attempt to detect support of OpenSSH2349 options by first invoking the configured SSH command with the2350 `-G` (print configuration) option and will subsequently use2351 OpenSSH options (if that is successful) or no options besides2352 the host and remote command (if it fails).2353+2354The config variable `ssh.variant` can be set to override this detection.2355Valid values are `ssh` (to use OpenSSH options), `plink`, `putty`,2356`tortoiseplink`, `simple` (no options except the host and remote command).2357The default auto-detection can be explicitly requested using the value2358`auto`. Any other value is treated as `ssh`. This setting can also be2359overridden via the environment variable `GIT_SSH_VARIANT`.2360+2361The current command-line parameters used for each variant are as2362follows:2363+2364--23652366* `ssh` - [-p port] [-4] [-6] [-o option] [username@]host command23672368* `simple` - [username@]host command23692370* `plink` or `putty` - [-P port] [-4] [-6] [username@]host command23712372* `tortoiseplink` - [-P port] [-4] [-6] -batch [username@]host command23732374--2375+2376Except for the `simple` variant, command-line parameters are likely to2377change as git gains new features.23782379i18n.commitEncoding::2380 Character encoding the commit messages are stored in; Git itself2381 does not care per se, but this information is necessary e.g. when2382 importing commits from emails or in the gitk graphical history2383 browser (and possibly at other places in the future or in other2384 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.23852386i18n.logOutputEncoding::2387 Character encoding the commit messages are converted to when2388 running 'git log' and friends.23892390imap::2391 The configuration variables in the 'imap' section are described2392 in linkgit:git-imap-send[1].23932394index.version::2395 Specify the version with which new index files should be2396 initialized. This does not affect existing repositories.23972398init.templateDir::2399 Specify the directory from which templates will be copied.2400 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)24012402instaweb.browser::2403 Specify the program that will be used to browse your working2404 repository in gitweb. See linkgit:git-instaweb[1].24052406instaweb.httpd::2407 The HTTP daemon command-line to start gitweb on your working2408 repository. See linkgit:git-instaweb[1].24092410instaweb.local::2411 If true the web server started by linkgit:git-instaweb[1] will2412 be bound to the local IP (127.0.0.1).24132414instaweb.modulePath::2415 The default module path for linkgit:git-instaweb[1] to use2416 instead of /usr/lib/apache2/modules. Only used if httpd2417 is Apache.24182419instaweb.port::2420 The port number to bind the gitweb httpd to. See2421 linkgit:git-instaweb[1].24222423interactive.singleKey::2424 In interactive commands, allow the user to provide one-letter2425 input with a single key (i.e., without hitting enter).2426 Currently this is used by the `--patch` mode of2427 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],2428 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this2429 setting is silently ignored if portable keystroke input2430 is not available; requires the Perl module Term::ReadKey.24312432interactive.diffFilter::2433 When an interactive command (such as `git add --patch`) shows2434 a colorized diff, git will pipe the diff through the shell2435 command defined by this configuration variable. The command may2436 mark up the diff further for human consumption, provided that it2437 retains a one-to-one correspondence with the lines in the2438 original diff. Defaults to disabled (no filtering).24392440log.abbrevCommit::2441 If true, makes linkgit:git-log[1], linkgit:git-show[1], and2442 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may2443 override this option with `--no-abbrev-commit`.24442445log.date::2446 Set the default date-time mode for the 'log' command.2447 Setting a value for log.date is similar to using 'git log''s2448 `--date` option. See linkgit:git-log[1] for details.24492450log.decorate::2451 Print out the ref names of any commits that are shown by the log2452 command. If 'short' is specified, the ref name prefixes 'refs/heads/',2453 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is2454 specified, the full ref name (including prefix) will be printed.2455 If 'auto' is specified, then if the output is going to a terminal,2456 the ref names are shown as if 'short' were given, otherwise no ref2457 names are shown. This is the same as the `--decorate` option2458 of the `git log`.24592460log.follow::2461 If `true`, `git log` will act as if the `--follow` option was used when2462 a single <path> is given. This has the same limitations as `--follow`,2463 i.e. it cannot be used to follow multiple files and does not work well2464 on non-linear history.24652466log.graphColors::2467 A list of colors, separated by commas, that can be used to draw2468 history lines in `git log --graph`.24692470log.showRoot::2471 If true, the initial commit will be shown as a big creation event.2472 This is equivalent to a diff against an empty tree.2473 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which2474 normally hide the root commit will now show it. True by default.24752476log.showSignature::2477 If true, makes linkgit:git-log[1], linkgit:git-show[1], and2478 linkgit:git-whatchanged[1] assume `--show-signature`.24792480log.mailmap::2481 If true, makes linkgit:git-log[1], linkgit:git-show[1], and2482 linkgit:git-whatchanged[1] assume `--use-mailmap`.24832484mailinfo.scissors::2485 If true, makes linkgit:git-mailinfo[1] (and therefore2486 linkgit:git-am[1]) act by default as if the --scissors option2487 was provided on the command-line. When active, this features2488 removes everything from the message body before a scissors2489 line (i.e. consisting mainly of ">8", "8<" and "-").24902491mailmap.file::2492 The location of an augmenting mailmap file. The default2493 mailmap, located in the root of the repository, is loaded2494 first, then the mailmap file pointed to by this variable.2495 The location of the mailmap file may be in a repository2496 subdirectory, or somewhere outside of the repository itself.2497 See linkgit:git-shortlog[1] and linkgit:git-blame[1].24982499mailmap.blob::2500 Like `mailmap.file`, but consider the value as a reference to a2501 blob in the repository. If both `mailmap.file` and2502 `mailmap.blob` are given, both are parsed, with entries from2503 `mailmap.file` taking precedence. In a bare repository, this2504 defaults to `HEAD:.mailmap`. In a non-bare repository, it2505 defaults to empty.25062507man.viewer::2508 Specify the programs that may be used to display help in the2509 'man' format. See linkgit:git-help[1].25102511man.<tool>.cmd::2512 Specify the command to invoke the specified man viewer. The2513 specified command is evaluated in shell with the man page2514 passed as argument. (See linkgit:git-help[1].)25152516man.<tool>.path::2517 Override the path for the given tool that may be used to2518 display help in the 'man' format. See linkgit:git-help[1].25192520include::merge-config.txt[]25212522mergetool.<tool>.path::2523 Override the path for the given tool. This is useful in case2524 your tool is not in the PATH.25252526mergetool.<tool>.cmd::2527 Specify the command to invoke the specified merge tool. The2528 specified command is evaluated in shell with the following2529 variables available: 'BASE' is the name of a temporary file2530 containing the common base of the files to be merged, if available;2531 'LOCAL' is the name of a temporary file containing the contents of2532 the file on the current branch; 'REMOTE' is the name of a temporary2533 file containing the contents of the file from the branch being2534 merged; 'MERGED' contains the name of the file to which the merge2535 tool should write the results of a successful merge.25362537mergetool.<tool>.trustExitCode::2538 For a custom merge command, specify whether the exit code of2539 the merge command can be used to determine whether the merge was2540 successful. If this is not set to true then the merge target file2541 timestamp is checked and the merge assumed to have been successful2542 if the file has been updated, otherwise the user is prompted to2543 indicate the success of the merge.25442545mergetool.meld.hasOutput::2546 Older versions of `meld` do not support the `--output` option.2547 Git will attempt to detect whether `meld` supports `--output`2548 by inspecting the output of `meld --help`. Configuring2549 `mergetool.meld.hasOutput` will make Git skip these checks and2550 use the configured value instead. Setting `mergetool.meld.hasOutput`2551 to `true` tells Git to unconditionally use the `--output` option,2552 and `false` avoids using `--output`.25532554mergetool.keepBackup::2555 After performing a merge, the original file with conflict markers2556 can be saved as a file with a `.orig` extension. If this variable2557 is set to `false` then this file is not preserved. Defaults to2558 `true` (i.e. keep the backup files).25592560mergetool.keepTemporaries::2561 When invoking a custom merge tool, Git uses a set of temporary2562 files to pass to the tool. If the tool returns an error and this2563 variable is set to `true`, then these temporary files will be2564 preserved, otherwise they will be removed after the tool has2565 exited. Defaults to `false`.25662567mergetool.writeToTemp::2568 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of2569 conflicting files in the worktree by default. Git will attempt2570 to use a temporary directory for these files when set `true`.2571 Defaults to `false`.25722573mergetool.prompt::2574 Prompt before each invocation of the merge resolution program.25752576notes.mergeStrategy::2577 Which merge strategy to choose by default when resolving notes2578 conflicts. Must be one of `manual`, `ours`, `theirs`, `union`, or2579 `cat_sort_uniq`. Defaults to `manual`. See "NOTES MERGE STRATEGIES"2580 section of linkgit:git-notes[1] for more information on each strategy.25812582notes.<name>.mergeStrategy::2583 Which merge strategy to choose when doing a notes merge into2584 refs/notes/<name>. This overrides the more general2585 "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES" section in2586 linkgit:git-notes[1] for more information on the available strategies.25872588notes.displayRef::2589 The (fully qualified) refname from which to show notes when2590 showing commit messages. The value of this variable can be set2591 to a glob, in which case notes from all matching refs will be2592 shown. You may also specify this configuration variable2593 several times. A warning will be issued for refs that do not2594 exist, but a glob that does not match any refs is silently2595 ignored.2596+2597This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`2598environment variable, which must be a colon separated list of refs or2599globs.2600+2601The effective value of "core.notesRef" (possibly overridden by2602GIT_NOTES_REF) is also implicitly added to the list of refs to be2603displayed.26042605notes.rewrite.<command>::2606 When rewriting commits with <command> (currently `amend` or2607 `rebase`) and this variable is set to `true`, Git2608 automatically copies your notes from the original to the2609 rewritten commit. Defaults to `true`, but see2610 "notes.rewriteRef" below.26112612notes.rewriteMode::2613 When copying notes during a rewrite (see the2614 "notes.rewrite.<command>" option), determines what to do if2615 the target commit already has a note. Must be one of2616 `overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`.2617 Defaults to `concatenate`.2618+2619This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`2620environment variable.26212622notes.rewriteRef::2623 When copying notes during a rewrite, specifies the (fully2624 qualified) ref whose notes should be copied. The ref may be a2625 glob, in which case notes in all matching refs will be copied.2626 You may also specify this configuration several times.2627+2628Does not have a default value; you must configure this variable to2629enable note rewriting. Set it to `refs/notes/commits` to enable2630rewriting for the default commit notes.2631+2632This setting can be overridden with the `GIT_NOTES_REWRITE_REF`2633environment variable, which must be a colon separated list of refs or2634globs.26352636pack.window::2637 The size of the window used by linkgit:git-pack-objects[1] when no2638 window size is given on the command line. Defaults to 10.26392640pack.depth::2641 The maximum delta depth used by linkgit:git-pack-objects[1] when no2642 maximum depth is given on the command line. Defaults to 50.2643 Maximum value is 4095.26442645pack.windowMemory::2646 The maximum size of memory that is consumed by each thread2647 in linkgit:git-pack-objects[1] for pack window memory when2648 no limit is given on the command line. The value can be2649 suffixed with "k", "m", or "g". When left unconfigured (or2650 set explicitly to 0), there will be no limit.26512652pack.compression::2653 An integer -1..9, indicating the compression level for objects2654 in a pack file. -1 is the zlib default. 0 means no2655 compression, and 1..9 are various speed/size tradeoffs, 9 being2656 slowest. If not set, defaults to core.compression. If that is2657 not set, defaults to -1, the zlib default, which is "a default2658 compromise between speed and compression (currently equivalent2659 to level 6)."2660+2661Note that changing the compression level will not automatically recompress2662all existing objects. You can force recompression by passing the -F option2663to linkgit:git-repack[1].26642665pack.deltaCacheSize::2666 The maximum memory in bytes used for caching deltas in2667 linkgit:git-pack-objects[1] before writing them out to a pack.2668 This cache is used to speed up the writing object phase by not2669 having to recompute the final delta result once the best match2670 for all objects is found. Repacking large repositories on machines2671 which are tight with memory might be badly impacted by this though,2672 especially if this cache pushes the system into swapping.2673 A value of 0 means no limit. The smallest size of 1 byte may be2674 used to virtually disable this cache. Defaults to 256 MiB.26752676pack.deltaCacheLimit::2677 The maximum size of a delta, that is cached in2678 linkgit:git-pack-objects[1]. This cache is used to speed up the2679 writing object phase by not having to recompute the final delta2680 result once the best match for all objects is found.2681 Defaults to 1000. Maximum value is 65535.26822683pack.threads::2684 Specifies the number of threads to spawn when searching for best2685 delta matches. This requires that linkgit:git-pack-objects[1]2686 be compiled with pthreads otherwise this option is ignored with a2687 warning. This is meant to reduce packing time on multiprocessor2688 machines. The required amount of memory for the delta search window2689 is however multiplied by the number of threads.2690 Specifying 0 will cause Git to auto-detect the number of CPU's2691 and set the number of threads accordingly.26922693pack.indexVersion::2694 Specify the default pack index version. Valid values are 1 for2695 legacy pack index used by Git versions prior to 1.5.2, and 2 for2696 the new pack index with capabilities for packs larger than 4 GB2697 as well as proper protection against the repacking of corrupted2698 packs. Version 2 is the default. Note that version 2 is enforced2699 and this config option ignored whenever the corresponding pack is2700 larger than 2 GB.2701+2702If you have an old Git that does not understand the version 2 `*.idx` file,2703cloning or fetching over a non native protocol (e.g. "http")2704that will copy both `*.pack` file and corresponding `*.idx` file from the2705other side may give you a repository that cannot be accessed with your2706older version of Git. If the `*.pack` file is smaller than 2 GB, however,2707you can use linkgit:git-index-pack[1] on the *.pack file to regenerate2708the `*.idx` file.27092710pack.packSizeLimit::2711 The maximum size of a pack. This setting only affects2712 packing to a file when repacking, i.e. the git:// protocol2713 is unaffected. It can be overridden by the `--max-pack-size`2714 option of linkgit:git-repack[1]. Reaching this limit results2715 in the creation of multiple packfiles; which in turn prevents2716 bitmaps from being created.2717 The minimum size allowed is limited to 1 MiB.2718 The default is unlimited.2719 Common unit suffixes of 'k', 'm', or 'g' are2720 supported.27212722pack.useBitmaps::2723 When true, git will use pack bitmaps (if available) when packing2724 to stdout (e.g., during the server side of a fetch). Defaults to2725 true. You should not generally need to turn this off unless2726 you are debugging pack bitmaps.27272728pack.writeBitmaps (deprecated)::2729 This is a deprecated synonym for `repack.writeBitmaps`.27302731pack.writeBitmapHashCache::2732 When true, git will include a "hash cache" section in the bitmap2733 index (if one is written). This cache can be used to feed git's2734 delta heuristics, potentially leading to better deltas between2735 bitmapped and non-bitmapped objects (e.g., when serving a fetch2736 between an older, bitmapped pack and objects that have been2737 pushed since the last gc). The downside is that it consumes 42738 bytes per object of disk space, and that JGit's bitmap2739 implementation does not understand it, causing it to complain if2740 Git and JGit are used on the same repository. Defaults to false.27412742pager.<cmd>::2743 If the value is boolean, turns on or off pagination of the2744 output of a particular Git subcommand when writing to a tty.2745 Otherwise, turns on pagination for the subcommand using the2746 pager specified by the value of `pager.<cmd>`. If `--paginate`2747 or `--no-pager` is specified on the command line, it takes2748 precedence over this option. To disable pagination for all2749 commands, set `core.pager` or `GIT_PAGER` to `cat`.27502751pretty.<name>::2752 Alias for a --pretty= format string, as specified in2753 linkgit:git-log[1]. Any aliases defined here can be used just2754 as the built-in pretty formats could. For example,2755 running `git config pretty.changelog "format:* %H %s"`2756 would cause the invocation `git log --pretty=changelog`2757 to be equivalent to running `git log "--pretty=format:* %H %s"`.2758 Note that an alias with the same name as a built-in format2759 will be silently ignored.27602761protocol.allow::2762 If set, provide a user defined default policy for all protocols which2763 don't explicitly have a policy (`protocol.<name>.allow`). By default,2764 if unset, known-safe protocols (http, https, git, ssh, file) have a2765 default policy of `always`, known-dangerous protocols (ext) have a2766 default policy of `never`, and all other protocols have a default2767 policy of `user`. Supported policies:2768+2769--27702771* `always` - protocol is always able to be used.27722773* `never` - protocol is never able to be used.27742775* `user` - protocol is only able to be used when `GIT_PROTOCOL_FROM_USER` is2776 either unset or has a value of 1. This policy should be used when you want a2777 protocol to be directly usable by the user but don't want it used by commands which2778 execute clone/fetch/push commands without user input, e.g. recursive2779 submodule initialization.27802781--27822783protocol.<name>.allow::2784 Set a policy to be used by protocol `<name>` with clone/fetch/push2785 commands. See `protocol.allow` above for the available policies.2786+2787The protocol names currently used by git are:2788+2789--2790 - `file`: any local file-based path (including `file://` URLs,2791 or local paths)27922793 - `git`: the anonymous git protocol over a direct TCP2794 connection (or proxy, if configured)27952796 - `ssh`: git over ssh (including `host:path` syntax,2797 `ssh://`, etc).27982799 - `http`: git over http, both "smart http" and "dumb http".2800 Note that this does _not_ include `https`; if you want to configure2801 both, you must do so individually.28022803 - any external helpers are named by their protocol (e.g., use2804 `hg` to allow the `git-remote-hg` helper)2805--28062807protocol.version::2808 Experimental. If set, clients will attempt to communicate with a2809 server using the specified protocol version. If unset, no2810 attempt will be made by the client to communicate using a2811 particular protocol version, this results in protocol version 02812 being used.2813 Supported versions:2814+2815--28162817* `0` - the original wire protocol.28182819* `1` - the original wire protocol with the addition of a version string2820 in the initial response from the server.28212822--28232824pull.ff::2825 By default, Git does not create an extra merge commit when merging2826 a commit that is a descendant of the current commit. Instead, the2827 tip of the current branch is fast-forwarded. When set to `false`,2828 this variable tells Git to create an extra merge commit in such2829 a case (equivalent to giving the `--no-ff` option from the command2830 line). When set to `only`, only such fast-forward merges are2831 allowed (equivalent to giving the `--ff-only` option from the2832 command line). This setting overrides `merge.ff` when pulling.28332834pull.rebase::2835 When true, rebase branches on top of the fetched branch, instead2836 of merging the default branch from the default remote when "git2837 pull" is run. See "branch.<name>.rebase" for setting this on a2838 per-branch basis.2839+2840When `merges`, pass the `--rebase-merges` option to 'git rebase'2841so that the local merge commits are included in the rebase (see2842linkgit:git-rebase[1] for details).2843+2844When preserve, also pass `--preserve-merges` along to 'git rebase'2845so that locally committed merge commits will not be flattened2846by running 'git pull'.2847+2848When the value is `interactive`, the rebase is run in interactive mode.2849+2850*NOTE*: this is a possibly dangerous operation; do *not* use2851it unless you understand the implications (see linkgit:git-rebase[1]2852for details).28532854pull.octopus::2855 The default merge strategy to use when pulling multiple branches2856 at once.28572858pull.twohead::2859 The default merge strategy to use when pulling a single branch.28602861push.default::2862 Defines the action `git push` should take if no refspec is2863 explicitly given. Different values are well-suited for2864 specific workflows; for instance, in a purely central workflow2865 (i.e. the fetch source is equal to the push destination),2866 `upstream` is probably what you want. Possible values are:2867+2868--28692870* `nothing` - do not push anything (error out) unless a refspec is2871 explicitly given. This is primarily meant for people who want to2872 avoid mistakes by always being explicit.28732874* `current` - push the current branch to update a branch with the same2875 name on the receiving end. Works in both central and non-central2876 workflows.28772878* `upstream` - push the current branch back to the branch whose2879 changes are usually integrated into the current branch (which is2880 called `@{upstream}`). This mode only makes sense if you are2881 pushing to the same repository you would normally pull from2882 (i.e. central workflow).28832884* `tracking` - This is a deprecated synonym for `upstream`.28852886* `simple` - in centralized workflow, work like `upstream` with an2887 added safety to refuse to push if the upstream branch's name is2888 different from the local one.2889+2890When pushing to a remote that is different from the remote you normally2891pull from, work as `current`. This is the safest option and is suited2892for beginners.2893+2894This mode has become the default in Git 2.0.28952896* `matching` - push all branches having the same name on both ends.2897 This makes the repository you are pushing to remember the set of2898 branches that will be pushed out (e.g. if you always push 'maint'2899 and 'master' there and no other branches, the repository you push2900 to will have these two branches, and your local 'maint' and2901 'master' will be pushed there).2902+2903To use this mode effectively, you have to make sure _all_ the2904branches you would push out are ready to be pushed out before2905running 'git push', as the whole point of this mode is to allow you2906to push all of the branches in one go. If you usually finish work2907on only one branch and push out the result, while other branches are2908unfinished, this mode is not for you. Also this mode is not2909suitable for pushing into a shared central repository, as other2910people may add new branches there, or update the tip of existing2911branches outside your control.2912+2913This used to be the default, but not since Git 2.0 (`simple` is the2914new default).29152916--29172918push.followTags::2919 If set to true enable `--follow-tags` option by default. You2920 may override this configuration at time of push by specifying2921 `--no-follow-tags`.29222923push.gpgSign::2924 May be set to a boolean value, or the string 'if-asked'. A true2925 value causes all pushes to be GPG signed, as if `--signed` is2926 passed to linkgit:git-push[1]. The string 'if-asked' causes2927 pushes to be signed if the server supports it, as if2928 `--signed=if-asked` is passed to 'git push'. A false value may2929 override a value from a lower-priority config file. An explicit2930 command-line flag always overrides this config option.29312932push.pushOption::2933 When no `--push-option=<option>` argument is given from the2934 command line, `git push` behaves as if each <value> of2935 this variable is given as `--push-option=<value>`.2936+2937This is a multi-valued variable, and an empty value can be used in a2938higher priority configuration file (e.g. `.git/config` in a2939repository) to clear the values inherited from a lower priority2940configuration files (e.g. `$HOME/.gitconfig`).2941+2942--29432944Example:29452946/etc/gitconfig2947 push.pushoption = a2948 push.pushoption = b29492950~/.gitconfig2951 push.pushoption = c29522953repo/.git/config2954 push.pushoption =2955 push.pushoption = b29562957This will result in only b (a and c are cleared).29582959--29602961push.recurseSubmodules::2962 Make sure all submodule commits used by the revisions to be pushed2963 are available on a remote-tracking branch. If the value is 'check'2964 then Git will verify that all submodule commits that changed in the2965 revisions to be pushed are available on at least one remote of the2966 submodule. If any commits are missing, the push will be aborted and2967 exit with non-zero status. If the value is 'on-demand' then all2968 submodules that changed in the revisions to be pushed will be2969 pushed. If on-demand was not able to push all necessary revisions2970 it will also be aborted and exit with non-zero status. If the value2971 is 'no' then default behavior of ignoring submodules when pushing2972 is retained. You may override this configuration at time of push by2973 specifying '--recurse-submodules=check|on-demand|no'.29742975include::rebase-config.txt[]29762977receive.advertiseAtomic::2978 By default, git-receive-pack will advertise the atomic push2979 capability to its clients. If you don't want to advertise this2980 capability, set this variable to false.29812982receive.advertisePushOptions::2983 When set to true, git-receive-pack will advertise the push options2984 capability to its clients. False by default.29852986receive.autogc::2987 By default, git-receive-pack will run "git-gc --auto" after2988 receiving data from git-push and updating refs. You can stop2989 it by setting this variable to false.29902991receive.certNonceSeed::2992 By setting this variable to a string, `git receive-pack`2993 will accept a `git push --signed` and verifies it by using2994 a "nonce" protected by HMAC using this string as a secret2995 key.29962997receive.certNonceSlop::2998 When a `git push --signed` sent a push certificate with a2999 "nonce" that was issued by a receive-pack serving the same3000 repository within this many seconds, export the "nonce"3001 found in the certificate to `GIT_PUSH_CERT_NONCE` to the3002 hooks (instead of what the receive-pack asked the sending3003 side to include). This may allow writing checks in3004 `pre-receive` and `post-receive` a bit easier. Instead of3005 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable3006 that records by how many seconds the nonce is stale to3007 decide if they want to accept the certificate, they only3008 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.30093010receive.fsckObjects::3011 If it is set to true, git-receive-pack will check all received3012 objects. See `transfer.fsckObjects` for what's checked.3013 Defaults to false. If not set, the value of3014 `transfer.fsckObjects` is used instead.30153016receive.fsck.<msg-id>::3017 Acts like `fsck.<msg-id>`, but is used by3018 linkgit:git-receive-pack[1] instead of3019 linkgit:git-fsck[1]. See the `fsck.<msg-id>` documentation for3020 details.30213022receive.fsck.skipList::3023 Acts like `fsck.skipList`, but is used by3024 linkgit:git-receive-pack[1] instead of3025 linkgit:git-fsck[1]. See the `fsck.skipList` documentation for3026 details.30273028receive.keepAlive::3029 After receiving the pack from the client, `receive-pack` may3030 produce no output (if `--quiet` was specified) while processing3031 the pack, causing some networks to drop the TCP connection.3032 With this option set, if `receive-pack` does not transmit3033 any data in this phase for `receive.keepAlive` seconds, it will3034 send a short keepalive packet. The default is 5 seconds; set3035 to 0 to disable keepalives entirely.30363037receive.unpackLimit::3038 If the number of objects received in a push is below this3039 limit then the objects will be unpacked into loose object3040 files. However if the number of received objects equals or3041 exceeds this limit then the received pack will be stored as3042 a pack, after adding any missing delta bases. Storing the3043 pack from a push can make the push operation complete faster,3044 especially on slow filesystems. If not set, the value of3045 `transfer.unpackLimit` is used instead.30463047receive.maxInputSize::3048 If the size of the incoming pack stream is larger than this3049 limit, then git-receive-pack will error out, instead of3050 accepting the pack file. If not set or set to 0, then the size3051 is unlimited.30523053receive.denyDeletes::3054 If set to true, git-receive-pack will deny a ref update that deletes3055 the ref. Use this to prevent such a ref deletion via a push.30563057receive.denyDeleteCurrent::3058 If set to true, git-receive-pack will deny a ref update that3059 deletes the currently checked out branch of a non-bare repository.30603061receive.denyCurrentBranch::3062 If set to true or "refuse", git-receive-pack will deny a ref update3063 to the currently checked out branch of a non-bare repository.3064 Such a push is potentially dangerous because it brings the HEAD3065 out of sync with the index and working tree. If set to "warn",3066 print a warning of such a push to stderr, but allow the push to3067 proceed. If set to false or "ignore", allow such pushes with no3068 message. Defaults to "refuse".3069+3070Another option is "updateInstead" which will update the working3071tree if pushing into the current branch. This option is3072intended for synchronizing working directories when one side is not easily3073accessible via interactive ssh (e.g. a live web site, hence the requirement3074that the working directory be clean). This mode also comes in handy when3075developing inside a VM to test and fix code on different Operating Systems.3076+3077By default, "updateInstead" will refuse the push if the working tree or3078the index have any difference from the HEAD, but the `push-to-checkout`3079hook can be used to customize this. See linkgit:githooks[5].30803081receive.denyNonFastForwards::3082 If set to true, git-receive-pack will deny a ref update which is3083 not a fast-forward. Use this to prevent such an update via a push,3084 even if that push is forced. This configuration variable is3085 set when initializing a shared repository.30863087receive.hideRefs::3088 This variable is the same as `transfer.hideRefs`, but applies3089 only to `receive-pack` (and so affects pushes, but not fetches).3090 An attempt to update or delete a hidden ref by `git push` is3091 rejected.30923093receive.updateServerInfo::3094 If set to true, git-receive-pack will run git-update-server-info3095 after receiving data from git-push and updating refs.30963097receive.shallowUpdate::3098 If set to true, .git/shallow can be updated when new refs3099 require new shallow roots. Otherwise those refs are rejected.31003101remote.pushDefault::3102 The remote to push to by default. Overrides3103 `branch.<name>.remote` for all branches, and is overridden by3104 `branch.<name>.pushRemote` for specific branches.31053106remote.<name>.url::3107 The URL of a remote repository. See linkgit:git-fetch[1] or3108 linkgit:git-push[1].31093110remote.<name>.pushurl::3111 The push URL of a remote repository. See linkgit:git-push[1].31123113remote.<name>.proxy::3114 For remotes that require curl (http, https and ftp), the URL to3115 the proxy to use for that remote. Set to the empty string to3116 disable proxying for that remote.31173118remote.<name>.proxyAuthMethod::3119 For remotes that require curl (http, https and ftp), the method to use for3120 authenticating against the proxy in use (probably set in3121 `remote.<name>.proxy`). See `http.proxyAuthMethod`.31223123remote.<name>.fetch::3124 The default set of "refspec" for linkgit:git-fetch[1]. See3125 linkgit:git-fetch[1].31263127remote.<name>.push::3128 The default set of "refspec" for linkgit:git-push[1]. See3129 linkgit:git-push[1].31303131remote.<name>.mirror::3132 If true, pushing to this remote will automatically behave3133 as if the `--mirror` option was given on the command line.31343135remote.<name>.skipDefaultUpdate::3136 If true, this remote will be skipped by default when updating3137 using linkgit:git-fetch[1] or the `update` subcommand of3138 linkgit:git-remote[1].31393140remote.<name>.skipFetchAll::3141 If true, this remote will be skipped by default when updating3142 using linkgit:git-fetch[1] or the `update` subcommand of3143 linkgit:git-remote[1].31443145remote.<name>.receivepack::3146 The default program to execute on the remote side when pushing. See3147 option --receive-pack of linkgit:git-push[1].31483149remote.<name>.uploadpack::3150 The default program to execute on the remote side when fetching. See3151 option --upload-pack of linkgit:git-fetch-pack[1].31523153remote.<name>.tagOpt::3154 Setting this value to --no-tags disables automatic tag following when3155 fetching from remote <name>. Setting it to --tags will fetch every3156 tag from remote <name>, even if they are not reachable from remote3157 branch heads. Passing these flags directly to linkgit:git-fetch[1] can3158 override this setting. See options --tags and --no-tags of3159 linkgit:git-fetch[1].31603161remote.<name>.vcs::3162 Setting this to a value <vcs> will cause Git to interact with3163 the remote with the git-remote-<vcs> helper.31643165remote.<name>.prune::3166 When set to true, fetching from this remote by default will also3167 remove any remote-tracking references that no longer exist on the3168 remote (as if the `--prune` option was given on the command line).3169 Overrides `fetch.prune` settings, if any.31703171remote.<name>.pruneTags::3172 When set to true, fetching from this remote by default will also3173 remove any local tags that no longer exist on the remote if pruning3174 is activated in general via `remote.<name>.prune`, `fetch.prune` or3175 `--prune`. Overrides `fetch.pruneTags` settings, if any.3176+3177See also `remote.<name>.prune` and the PRUNING section of3178linkgit:git-fetch[1].31793180remotes.<group>::3181 The list of remotes which are fetched by "git remote update3182 <group>". See linkgit:git-remote[1].31833184repack.useDeltaBaseOffset::3185 By default, linkgit:git-repack[1] creates packs that use3186 delta-base offset. If you need to share your repository with3187 Git older than version 1.4.4, either directly or via a dumb3188 protocol such as http, then you need to set this option to3189 "false" and repack. Access from old Git versions over the3190 native protocol are unaffected by this option.31913192repack.packKeptObjects::3193 If set to true, makes `git repack` act as if3194 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for3195 details. Defaults to `false` normally, but `true` if a bitmap3196 index is being written (either via `--write-bitmap-index` or3197 `repack.writeBitmaps`).31983199repack.writeBitmaps::3200 When true, git will write a bitmap index when packing all3201 objects to disk (e.g., when `git repack -a` is run). This3202 index can speed up the "counting objects" phase of subsequent3203 packs created for clones and fetches, at the cost of some disk3204 space and extra time spent on the initial repack. This has3205 no effect if multiple packfiles are created.3206 Defaults to false.32073208rerere.autoUpdate::3209 When set to true, `git-rerere` updates the index with the3210 resulting contents after it cleanly resolves conflicts using3211 previously recorded resolution. Defaults to false.32123213rerere.enabled::3214 Activate recording of resolved conflicts, so that identical3215 conflict hunks can be resolved automatically, should they be3216 encountered again. By default, linkgit:git-rerere[1] is3217 enabled if there is an `rr-cache` directory under the3218 `$GIT_DIR`, e.g. if "rerere" was previously used in the3219 repository.32203221sendemail.identity::3222 A configuration identity. When given, causes values in the3223 'sendemail.<identity>' subsection to take precedence over3224 values in the 'sendemail' section. The default identity is3225 the value of `sendemail.identity`.32263227sendemail.smtpEncryption::3228 See linkgit:git-send-email[1] for description. Note that this3229 setting is not subject to the 'identity' mechanism.32303231sendemail.smtpssl (deprecated)::3232 Deprecated alias for 'sendemail.smtpEncryption = ssl'.32333234sendemail.smtpsslcertpath::3235 Path to ca-certificates (either a directory or a single file).3236 Set it to an empty string to disable certificate verification.32373238sendemail.<identity>.*::3239 Identity-specific versions of the 'sendemail.*' parameters3240 found below, taking precedence over those when this3241 identity is selected, through either the command-line or3242 `sendemail.identity`.32433244sendemail.aliasesFile::3245sendemail.aliasFileType::3246sendemail.annotate::3247sendemail.bcc::3248sendemail.cc::3249sendemail.ccCmd::3250sendemail.chainReplyTo::3251sendemail.confirm::3252sendemail.envelopeSender::3253sendemail.from::3254sendemail.multiEdit::3255sendemail.signedoffbycc::3256sendemail.smtpPass::3257sendemail.suppresscc::3258sendemail.suppressFrom::3259sendemail.to::3260sendemail.tocmd::3261sendemail.smtpDomain::3262sendemail.smtpServer::3263sendemail.smtpServerPort::3264sendemail.smtpServerOption::3265sendemail.smtpUser::3266sendemail.thread::3267sendemail.transferEncoding::3268sendemail.validate::3269sendemail.xmailer::3270 See linkgit:git-send-email[1] for description.32713272sendemail.signedoffcc (deprecated)::3273 Deprecated alias for `sendemail.signedoffbycc`.32743275sendemail.smtpBatchSize::3276 Number of messages to be sent per connection, after that a relogin3277 will happen. If the value is 0 or undefined, send all messages in3278 one connection.3279 See also the `--batch-size` option of linkgit:git-send-email[1].32803281sendemail.smtpReloginDelay::3282 Seconds wait before reconnecting to smtp server.3283 See also the `--relogin-delay` option of linkgit:git-send-email[1].32843285showbranch.default::3286 The default set of branches for linkgit:git-show-branch[1].3287 See linkgit:git-show-branch[1].32883289splitIndex.maxPercentChange::3290 When the split index feature is used, this specifies the3291 percent of entries the split index can contain compared to the3292 total number of entries in both the split index and the shared3293 index before a new shared index is written.3294 The value should be between 0 and 100. If the value is 0 then3295 a new shared index is always written, if it is 100 a new3296 shared index is never written.3297 By default the value is 20, so a new shared index is written3298 if the number of entries in the split index would be greater3299 than 20 percent of the total number of entries.3300 See linkgit:git-update-index[1].33013302splitIndex.sharedIndexExpire::3303 When the split index feature is used, shared index files that3304 were not modified since the time this variable specifies will3305 be removed when a new shared index file is created. The value3306 "now" expires all entries immediately, and "never" suppresses3307 expiration altogether.3308 The default value is "2.weeks.ago".3309 Note that a shared index file is considered modified (for the3310 purpose of expiration) each time a new split-index file is3311 either created based on it or read from it.3312 See linkgit:git-update-index[1].33133314status.relativePaths::3315 By default, linkgit:git-status[1] shows paths relative to the3316 current directory. Setting this variable to `false` shows paths3317 relative to the repository root (this was the default for Git3318 prior to v1.5.4).33193320status.short::3321 Set to true to enable --short by default in linkgit:git-status[1].3322 The option --no-short takes precedence over this variable.33233324status.branch::3325 Set to true to enable --branch by default in linkgit:git-status[1].3326 The option --no-branch takes precedence over this variable.33273328status.displayCommentPrefix::3329 If set to true, linkgit:git-status[1] will insert a comment3330 prefix before each output line (starting with3331 `core.commentChar`, i.e. `#` by default). This was the3332 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.3333 Defaults to false.33343335status.renameLimit::3336 The number of files to consider when performing rename detection3337 in linkgit:git-status[1] and linkgit:git-commit[1]. Defaults to3338 the value of diff.renameLimit.33393340status.renames::3341 Whether and how Git detects renames in linkgit:git-status[1] and3342 linkgit:git-commit[1] . If set to "false", rename detection is3343 disabled. If set to "true", basic rename detection is enabled.3344 If set to "copies" or "copy", Git will detect copies, as well.3345 Defaults to the value of diff.renames.33463347status.showStash::3348 If set to true, linkgit:git-status[1] will display the number of3349 entries currently stashed away.3350 Defaults to false.33513352status.showUntrackedFiles::3353 By default, linkgit:git-status[1] and linkgit:git-commit[1] show3354 files which are not currently tracked by Git. Directories which3355 contain only untracked files, are shown with the directory name3356 only. Showing untracked files means that Git needs to lstat() all3357 the files in the whole repository, which might be slow on some3358 systems. So, this variable controls how the commands displays3359 the untracked files. Possible values are:3360+3361--3362* `no` - Show no untracked files.3363* `normal` - Show untracked files and directories.3364* `all` - Show also individual files in untracked directories.3365--3366+3367If this variable is not specified, it defaults to 'normal'.3368This variable can be overridden with the -u|--untracked-files option3369of linkgit:git-status[1] and linkgit:git-commit[1].33703371status.submoduleSummary::3372 Defaults to false.3373 If this is set to a non zero number or true (identical to -1 or an3374 unlimited number), the submodule summary will be enabled and a3375 summary of commits for modified submodules will be shown (see3376 --summary-limit option of linkgit:git-submodule[1]). Please note3377 that the summary output command will be suppressed for all3378 submodules when `diff.ignoreSubmodules` is set to 'all' or only3379 for those submodules where `submodule.<name>.ignore=all`. The only3380 exception to that rule is that status and commit will show staged3381 submodule changes. To3382 also view the summary for ignored submodules you can either use3383 the --ignore-submodules=dirty command-line option or the 'git3384 submodule summary' command, which shows a similar output but does3385 not honor these settings.33863387stash.showPatch::3388 If this is set to true, the `git stash show` command without an3389 option will show the stash entry in patch form. Defaults to false.3390 See description of 'show' command in linkgit:git-stash[1].33913392stash.showStat::3393 If this is set to true, the `git stash show` command without an3394 option will show diffstat of the stash entry. Defaults to true.3395 See description of 'show' command in linkgit:git-stash[1].33963397submodule.<name>.url::3398 The URL for a submodule. This variable is copied from the .gitmodules3399 file to the git config via 'git submodule init'. The user can change3400 the configured URL before obtaining the submodule via 'git submodule3401 update'. If neither submodule.<name>.active or submodule.active are3402 set, the presence of this variable is used as a fallback to indicate3403 whether the submodule is of interest to git commands.3404 See linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.34053406submodule.<name>.update::3407 The method by which a submodule is updated by 'git submodule update',3408 which is the only affected command, others such as3409 'git checkout --recurse-submodules' are unaffected. It exists for3410 historical reasons, when 'git submodule' was the only command to3411 interact with submodules; settings like `submodule.active`3412 and `pull.rebase` are more specific. It is populated by3413 `git submodule init` from the linkgit:gitmodules[5] file.3414 See description of 'update' command in linkgit:git-submodule[1].34153416submodule.<name>.branch::3417 The remote branch name for a submodule, used by `git submodule3418 update --remote`. Set this option to override the value found in3419 the `.gitmodules` file. See linkgit:git-submodule[1] and3420 linkgit:gitmodules[5] for details.34213422submodule.<name>.fetchRecurseSubmodules::3423 This option can be used to control recursive fetching of this3424 submodule. It can be overridden by using the --[no-]recurse-submodules3425 command-line option to "git fetch" and "git pull".3426 This setting will override that from in the linkgit:gitmodules[5]3427 file.34283429submodule.<name>.ignore::3430 Defines under what circumstances "git status" and the diff family show3431 a submodule as modified. When set to "all", it will never be considered3432 modified (but it will nonetheless show up in the output of status and3433 commit when it has been staged), "dirty" will ignore all changes3434 to the submodules work tree and3435 takes only differences between the HEAD of the submodule and the commit3436 recorded in the superproject into account. "untracked" will additionally3437 let submodules with modified tracked files in their work tree show up.3438 Using "none" (the default when this option is not set) also shows3439 submodules that have untracked files in their work tree as changed.3440 This setting overrides any setting made in .gitmodules for this submodule,3441 both settings can be overridden on the command line by using the3442 "--ignore-submodules" option. The 'git submodule' commands are not3443 affected by this setting.34443445submodule.<name>.active::3446 Boolean value indicating if the submodule is of interest to git3447 commands. This config option takes precedence over the3448 submodule.active config option. See linkgit:gitsubmodules[7] for3449 details.34503451submodule.active::3452 A repeated field which contains a pathspec used to match against a3453 submodule's path to determine if the submodule is of interest to git3454 commands. See linkgit:gitsubmodules[7] for details.34553456submodule.recurse::3457 Specifies if commands recurse into submodules by default. This3458 applies to all commands that have a `--recurse-submodules` option,3459 except `clone`.3460 Defaults to false.34613462submodule.fetchJobs::3463 Specifies how many submodules are fetched/cloned at the same time.3464 A positive integer allows up to that number of submodules fetched3465 in parallel. A value of 0 will give some reasonable default.3466 If unset, it defaults to 1.34673468submodule.alternateLocation::3469 Specifies how the submodules obtain alternates when submodules are3470 cloned. Possible values are `no`, `superproject`.3471 By default `no` is assumed, which doesn't add references. When the3472 value is set to `superproject` the submodule to be cloned computes3473 its alternates location relative to the superprojects alternate.34743475submodule.alternateErrorStrategy::3476 Specifies how to treat errors with the alternates for a submodule3477 as computed via `submodule.alternateLocation`. Possible values are3478 `ignore`, `info`, `die`. Default is `die`.34793480tag.forceSignAnnotated::3481 A boolean to specify whether annotated tags created should be GPG signed.3482 If `--annotate` is specified on the command line, it takes3483 precedence over this option.34843485tag.sort::3486 This variable controls the sort ordering of tags when displayed by3487 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the3488 value of this variable will be used as the default.34893490tar.umask::3491 This variable can be used to restrict the permission bits of3492 tar archive entries. The default is 0002, which turns off the3493 world write bit. The special value "user" indicates that the3494 archiving user's umask will be used instead. See umask(2) and3495 linkgit:git-archive[1].34963497transfer.fsckObjects::3498 When `fetch.fsckObjects` or `receive.fsckObjects` are3499 not set, the value of this variable is used instead.3500 Defaults to false.3501+3502When set, the fetch or receive will abort in the case of a malformed3503object or a link to a nonexistent object. In addition, various other3504issues are checked for, including legacy issues (see `fsck.<msg-id>`),3505and potential security issues like the existence of a `.GIT` directory3506or a malicious `.gitmodules` file (see the release notes for v2.2.13507and v2.17.1 for details). Other sanity and security checks may be3508added in future releases.3509+3510On the receiving side, failing fsckObjects will make those objects3511unreachable, see "QUARANTINE ENVIRONMENT" in3512linkgit:git-receive-pack[1]. On the fetch side, malformed objects will3513instead be left unreferenced in the repository.3514+3515Due to the non-quarantine nature of the `fetch.fsckObjects`3516implementation it can not be relied upon to leave the object store3517clean like `receive.fsckObjects` can.3518+3519As objects are unpacked they're written to the object store, so there3520can be cases where malicious objects get introduced even though the3521"fetch" failed, only to have a subsequent "fetch" succeed because only3522new incoming objects are checked, not those that have already been3523written to the object store. That difference in behavior should not be3524relied upon. In the future, such objects may be quarantined for3525"fetch" as well.3526+3527For now, the paranoid need to find some way to emulate the quarantine3528environment if they'd like the same protection as "push". E.g. in the3529case of an internal mirror do the mirroring in two steps, one to fetch3530the untrusted objects, and then do a second "push" (which will use the3531quarantine) to another internal repo, and have internal clients3532consume this pushed-to repository, or embargo internal fetches and3533only allow them once a full "fsck" has run (and no new fetches have3534happened in the meantime).35353536transfer.hideRefs::3537 String(s) `receive-pack` and `upload-pack` use to decide which3538 refs to omit from their initial advertisements. Use more than3539 one definition to specify multiple prefix strings. A ref that is3540 under the hierarchies listed in the value of this variable is3541 excluded, and is hidden when responding to `git push` or `git3542 fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for3543 program-specific versions of this config.3544+3545You may also include a `!` in front of the ref name to negate the entry,3546explicitly exposing it, even if an earlier entry marked it as hidden.3547If you have multiple hideRefs values, later entries override earlier ones3548(and entries in more-specific config files override less-specific ones).3549+3550If a namespace is in use, the namespace prefix is stripped from each3551reference before it is matched against `transfer.hiderefs` patterns.3552For example, if `refs/heads/master` is specified in `transfer.hideRefs` and3553the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`3554is omitted from the advertisements but `refs/heads/master` and3555`refs/namespaces/bar/refs/heads/master` are still advertised as so-called3556"have" lines. In order to match refs before stripping, add a `^` in front of3557the ref name. If you combine `!` and `^`, `!` must be specified first.3558+3559Even if you hide refs, a client may still be able to steal the target3560objects via the techniques described in the "SECURITY" section of the3561linkgit:gitnamespaces[7] man page; it's best to keep private data in a3562separate repository.35633564transfer.unpackLimit::3565 When `fetch.unpackLimit` or `receive.unpackLimit` are3566 not set, the value of this variable is used instead.3567 The default value is 100.35683569uploadarchive.allowUnreachable::3570 If true, allow clients to use `git archive --remote` to request3571 any tree, whether reachable from the ref tips or not. See the3572 discussion in the "SECURITY" section of3573 linkgit:git-upload-archive[1] for more details. Defaults to3574 `false`.35753576uploadpack.hideRefs::3577 This variable is the same as `transfer.hideRefs`, but applies3578 only to `upload-pack` (and so affects only fetches, not pushes).3579 An attempt to fetch a hidden ref by `git fetch` will fail. See3580 also `uploadpack.allowTipSHA1InWant`.35813582uploadpack.allowTipSHA1InWant::3583 When `uploadpack.hideRefs` is in effect, allow `upload-pack`3584 to accept a fetch request that asks for an object at the tip3585 of a hidden ref (by default, such a request is rejected).3586 See also `uploadpack.hideRefs`. Even if this is false, a client3587 may be able to steal objects via the techniques described in the3588 "SECURITY" section of the linkgit:gitnamespaces[7] man page; it's3589 best to keep private data in a separate repository.35903591uploadpack.allowReachableSHA1InWant::3592 Allow `upload-pack` to accept a fetch request that asks for an3593 object that is reachable from any ref tip. However, note that3594 calculating object reachability is computationally expensive.3595 Defaults to `false`. Even if this is false, a client may be able3596 to steal objects via the techniques described in the "SECURITY"3597 section of the linkgit:gitnamespaces[7] man page; it's best to3598 keep private data in a separate repository.35993600uploadpack.allowAnySHA1InWant::3601 Allow `upload-pack` to accept a fetch request that asks for any3602 object at all.3603 Defaults to `false`.36043605uploadpack.keepAlive::3606 When `upload-pack` has started `pack-objects`, there may be a3607 quiet period while `pack-objects` prepares the pack. Normally3608 it would output progress information, but if `--quiet` was used3609 for the fetch, `pack-objects` will output nothing at all until3610 the pack data begins. Some clients and networks may consider3611 the server to be hung and give up. Setting this option instructs3612 `upload-pack` to send an empty keepalive packet every3613 `uploadpack.keepAlive` seconds. Setting this option to 03614 disables keepalive packets entirely. The default is 5 seconds.36153616uploadpack.packObjectsHook::3617 If this option is set, when `upload-pack` would run3618 `git pack-objects` to create a packfile for a client, it will3619 run this shell command instead. The `pack-objects` command and3620 arguments it _would_ have run (including the `git pack-objects`3621 at the beginning) are appended to the shell command. The stdin3622 and stdout of the hook are treated as if `pack-objects` itself3623 was run. I.e., `upload-pack` will feed input intended for3624 `pack-objects` to the hook, and expects a completed packfile on3625 stdout.36263627uploadpack.allowFilter::3628 If this option is set, `upload-pack` will support partial3629 clone and partial fetch object filtering.3630+3631Note that this configuration variable is ignored if it is seen in the3632repository-level config (this is a safety measure against fetching from3633untrusted repositories).36343635uploadpack.allowRefInWant::3636 If this option is set, `upload-pack` will support the `ref-in-want`3637 feature of the protocol version 2 `fetch` command. This feature3638 is intended for the benefit of load-balanced servers which may3639 not have the same view of what OIDs their refs point to due to3640 replication delay.36413642url.<base>.insteadOf::3643 Any URL that starts with this value will be rewritten to3644 start, instead, with <base>. In cases where some site serves a3645 large number of repositories, and serves them with multiple3646 access methods, and some users need to use different access3647 methods, this feature allows people to specify any of the3648 equivalent URLs and have Git automatically rewrite the URL to3649 the best alternative for the particular user, even for a3650 never-before-seen repository on the site. When more than one3651 insteadOf strings match a given URL, the longest match is used.3652+3653Note that any protocol restrictions will be applied to the rewritten3654URL. If the rewrite changes the URL to use a custom protocol or remote3655helper, you may need to adjust the `protocol.*.allow` config to permit3656the request. In particular, protocols you expect to use for submodules3657must be set to `always` rather than the default of `user`. See the3658description of `protocol.allow` above.36593660url.<base>.pushInsteadOf::3661 Any URL that starts with this value will not be pushed to;3662 instead, it will be rewritten to start with <base>, and the3663 resulting URL will be pushed to. In cases where some site serves3664 a large number of repositories, and serves them with multiple3665 access methods, some of which do not allow push, this feature3666 allows people to specify a pull-only URL and have Git3667 automatically use an appropriate URL to push, even for a3668 never-before-seen repository on the site. When more than one3669 pushInsteadOf strings match a given URL, the longest match is3670 used. If a remote has an explicit pushurl, Git will ignore this3671 setting for that remote.36723673user.email::3674 Your email address to be recorded in any newly created commits.3675 Can be overridden by the `GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_EMAIL`, and3676 `EMAIL` environment variables. See linkgit:git-commit-tree[1].36773678user.name::3679 Your full name to be recorded in any newly created commits.3680 Can be overridden by the `GIT_AUTHOR_NAME` and `GIT_COMMITTER_NAME`3681 environment variables. See linkgit:git-commit-tree[1].36823683user.useConfigOnly::3684 Instruct Git to avoid trying to guess defaults for `user.email`3685 and `user.name`, and instead retrieve the values only from the3686 configuration. For example, if you have multiple email addresses3687 and would like to use a different one for each repository, then3688 with this configuration option set to `true` in the global config3689 along with a name, Git will prompt you to set up an email before3690 making new commits in a newly cloned repository.3691 Defaults to `false`.36923693user.signingKey::3694 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the3695 key you want it to automatically when creating a signed tag or3696 commit, you can override the default selection with this variable.3697 This option is passed unchanged to gpg's --local-user parameter,3698 so you may specify a key using any method that gpg supports.36993700versionsort.prereleaseSuffix (deprecated)::3701 Deprecated alias for `versionsort.suffix`. Ignored if3702 `versionsort.suffix` is set.37033704versionsort.suffix::3705 Even when version sort is used in linkgit:git-tag[1], tagnames3706 with the same base version but different suffixes are still sorted3707 lexicographically, resulting e.g. in prerelease tags appearing3708 after the main release (e.g. "1.0-rc1" after "1.0"). This3709 variable can be specified to determine the sorting order of tags3710 with different suffixes.3711+3712By specifying a single suffix in this variable, any tagname containing3713that suffix will appear before the corresponding main release. E.g. if3714the variable is set to "-rc", then all "1.0-rcX" tags will appear before3715"1.0". If specified multiple times, once per suffix, then the order of3716suffixes in the configuration will determine the sorting order of tagnames3717with those suffixes. E.g. if "-pre" appears before "-rc" in the3718configuration, then all "1.0-preX" tags will be listed before any3719"1.0-rcX" tags. The placement of the main release tag relative to tags3720with various suffixes can be determined by specifying the empty suffix3721among those other suffixes. E.g. if the suffixes "-rc", "", "-ck" and3722"-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags3723are listed first, followed by "v4.8", then "v4.8-ckX" and finally3724"v4.8-bfsX".3725+3726If more than one suffixes match the same tagname, then that tagname will3727be sorted according to the suffix which starts at the earliest position in3728the tagname. If more than one different matching suffixes start at3729that earliest position, then that tagname will be sorted according to the3730longest of those suffixes.3731The sorting order between different suffixes is undefined if they are3732in multiple config files.37333734web.browser::3735 Specify a web browser that may be used by some commands.3736 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]3737 may use it.37383739worktree.guessRemote::3740 With `add`, if no branch argument, and neither of `-b` nor3741 `-B` nor `--detach` are given, the command defaults to3742 creating a new branch from HEAD. If `worktree.guessRemote` is3743 set to true, `worktree add` tries to find a remote-tracking3744 branch whose name uniquely matches the new branch name. If3745 such a branch exists, it is checked out and set as "upstream"3746 for the new branch. If no such match can be found, it falls3747 back to creating a new branch from the current HEAD.