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. 18 19Syntax 20~~~~~~ 21 22The syntax is fairly flexible and permissive; whitespaces are mostly 23ignored. The '#' and ';' characters begin comments to the end of line, 24blank lines are ignored. 25 26The file consists of sections and variables. A section begins with 27the name of the section in square brackets and continues until the next 28section begins. Section names are not case sensitive. Only alphanumeric 29characters, `-` and `.` are allowed in section names. Each variable 30must belong to some section, which means that there must be a section 31header before the first setting of a variable. 32 33Sections can be further divided into subsections. To begin a subsection 34put its name in double quotes, separated by space from the section name, 35in the section header, like in the example below: 36 37-------- 38 [section "subsection"] 39 40-------- 41 42Subsection names are case sensitive and can contain any characters except 43newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`, 44respectively). Section headers cannot span multiple 45lines. Variables may belong directly to a section or to a given subsection. 46You can have `[section]` if you have `[section "subsection"]`, but you 47don't need to. 48 49There is also a deprecated `[section.subsection]` syntax. With this 50syntax, the subsection name is converted to lower-case and is also 51compared case sensitively. These subsection names follow the same 52restrictions as section names. 53 54All the other lines (and the remainder of the line after the section 55header) are recognized as setting variables, in the form 56'name = value'. If there is no equal sign on the line, the entire line 57is taken as 'name' and the variable is recognized as boolean "true". 58The variable names are case-insensitive, allow only alphanumeric characters 59and `-`, and must start with an alphabetic character. There can be more 60than one value for a given variable; we say then that the variable is 61multivalued. 62 63Leading and trailing whitespace in a variable value is discarded. 64Internal whitespace within a variable value is retained verbatim. 65 66The values following the equals sign in variable assign are all either 67a string, an integer, or a boolean. Boolean values may be given as yes/no, 681/0, true/false or on/off. Case is not significant in boolean values, when 69converting value to the canonical form using '--bool' type specifier; 70'git config' will ensure that the output is "true" or "false". 71 72String values may be entirely or partially enclosed in double quotes. 73You need to enclose variable values in double quotes if you want to 74preserve leading or trailing whitespace, or if the variable value contains 75comment characters (i.e. it contains '#' or ';'). 76Double quote `"` and backslash `\` characters in variable values must 77be escaped: use `\"` for `"` and `\\` for `\`. 78 79The following escape sequences (beside `\"` and `\\`) are recognized: 80`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 81and `\b` for backspace (BS). Other char escape sequences (including octal 82escape sequences) are invalid. 83 84Variable values ending in a `\` are continued on the next line in the 85customary UNIX fashion. 86 87Some variables may require a special value format. 88 89Includes 90~~~~~~~~ 91 92You can include one config file from another by setting the special 93`include.path` variable to the name of the file to be included. The 94included file is expanded immediately, as if its contents had been 95found at the location of the include directive. If the value of the 96`include.path` variable is a relative path, the path is considered to be 97relative to the configuration file in which the include directive was 98found. The value of `include.path` is subject to tilde expansion: `~/` 99is expanded to the value of `$HOME`, and `~user/` to the specified 100user's home directory. See below for examples. 101 102Example 103~~~~~~~ 104 105 # Core variables 106 [core] 107 ; Don't trust file modes 108 filemode = false 109 110 # Our diff algorithm 111 [diff] 112 external = /usr/local/bin/diff-wrapper 113 renames = true 114 115 [branch "devel"] 116 remote = origin 117 merge = refs/heads/devel 118 119 # Proxy settings 120 [core] 121 gitProxy="ssh" for "kernel.org" 122 gitProxy=default-proxy ; for the rest 123 124 [include] 125 path = /path/to/foo.inc ; include by absolute path 126 path = foo ; expand "foo" relative to the current file 127 path = ~/foo ; expand "foo" in your $HOME directory 128 129Variables 130~~~~~~~~~ 131 132Note that this list is non-comprehensive and not necessarily complete. 133For command-specific variables, you will find a more detailed description 134in the appropriate manual page. 135 136Other git-related tools may and do use their own variables. When 137inventing new variables for use in your own tool, make sure their 138names do not conflict with those that are used by Git itself and 139other popular tools, and describe them in your documentation. 140 141 142advice.*:: 143 These variables control various optional help messages designed to 144 aid new users. All 'advice.*' variables default to 'true', and you 145 can tell Git that you do not need help by setting these to 'false': 146+ 147-- 148 pushUpdateRejected:: 149 Set this variable to 'false' if you want to disable 150 'pushNonFFCurrent', 151 'pushNonFFMatching', 'pushAlreadyExists', 152 'pushFetchFirst', and 'pushNeedsForce' 153 simultaneously. 154 pushNonFFCurrent:: 155 Advice shown when linkgit:git-push[1] fails due to a 156 non-fast-forward update to the current branch. 157 pushNonFFMatching:: 158 Advice shown when you ran linkgit:git-push[1] and pushed 159 'matching refs' explicitly (i.e. you used ':', or 160 specified a refspec that isn't your current branch) and 161 it resulted in a non-fast-forward error. 162 pushAlreadyExists:: 163 Shown when linkgit:git-push[1] rejects an update that 164 does not qualify for fast-forwarding (e.g., a tag.) 165 pushFetchFirst:: 166 Shown when linkgit:git-push[1] rejects an update that 167 tries to overwrite a remote ref that points at an 168 object we do not have. 169 pushNeedsForce:: 170 Shown when linkgit:git-push[1] rejects an update that 171 tries to overwrite a remote ref that points at an 172 object that is not a commit-ish, or make the remote 173 ref point at an object that is not a commit-ish. 174 statusHints:: 175 Show directions on how to proceed from the current 176 state in the output of linkgit:git-status[1], in 177 the template shown when writing commit messages in 178 linkgit:git-commit[1], and in the help message shown 179 by linkgit:git-checkout[1] when switching branch. 180 statusUoption:: 181 Advise to consider using the `-u` option to linkgit:git-status[1] 182 when the command takes more than 2 seconds to enumerate untracked 183 files. 184 commitBeforeMerge:: 185 Advice shown when linkgit:git-merge[1] refuses to 186 merge to avoid overwriting local changes. 187 resolveConflict:: 188 Advice shown by various commands when conflicts 189 prevent the operation from being performed. 190 implicitIdentity:: 191 Advice on how to set your identity configuration when 192 your information is guessed from the system username and 193 domain name. 194 detachedHead:: 195 Advice shown when you used linkgit:git-checkout[1] to 196 move to the detach HEAD state, to instruct how to create 197 a local branch after the fact. 198 amWorkDir:: 199 Advice that shows the location of the patch file when 200 linkgit:git-am[1] fails to apply it. 201 rmHints:: 202 In case of failure in the output of linkgit:git-rm[1], 203 show directions on how to proceed from the current state. 204-- 205 206core.fileMode:: 207 Tells Git if the executable bit of files in the working tree 208 is to be honored. 209+ 210Some filesystems lose the executable bit when a file that is 211marked as executable is checked out, or checks out an 212non-executable file with executable bit on. 213linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 214to see if it handles the executable bit correctly 215and this variable is automatically set as necessary. 216+ 217A repository, however, may be on a filesystem that handles 218the filemode correctly, and this variable is set to 'true' 219when created, but later may be made accessible from another 220environment that loses the filemode (e.g. exporting ext4 via 221CIFS mount, visiting a Cygwin created repository with 222Git for Windows or Eclipse). 223In such a case it may be necessary to set this variable to 'false'. 224See linkgit:git-update-index[1]. 225+ 226The default is true (when core.filemode is not specified in the config file). 227 228core.ignorecase:: 229 If true, this option enables various workarounds to enable 230 Git to work better on filesystems that are not case sensitive, 231 like FAT. For example, if a directory listing finds 232 "makefile" when Git expects "Makefile", Git will assume 233 it is really the same file, and continue to remember it as 234 "Makefile". 235+ 236The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 237will probe and set core.ignorecase true if appropriate when the repository 238is created. 239 240core.precomposeunicode:: 241 This option is only used by Mac OS implementation of Git. 242 When core.precomposeunicode=true, Git reverts the unicode decomposition 243 of filenames done by Mac OS. This is useful when sharing a repository 244 between Mac OS and Linux or Windows. 245 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 246 When false, file names are handled fully transparent by Git, 247 which is backward compatible with older versions of Git. 248 249core.protectHFS:: 250 If set to true, do not allow checkout of paths that would 251 be considered equivalent to `.git` on an HFS+ filesystem. 252 Defaults to `true` on Mac OS, and `false` elsewhere. 253 254core.protectNTFS:: 255 If set to true, do not allow checkout of paths that would 256 cause problems with the NTFS filesystem, e.g. conflict with 257 8.3 "short" names. 258 Defaults to `true` on Windows, and `false` elsewhere. 259 260core.trustctime:: 261 If false, the ctime differences between the index and the 262 working tree are ignored; useful when the inode change time 263 is regularly modified by something outside Git (file system 264 crawlers and some backup systems). 265 See linkgit:git-update-index[1]. True by default. 266 267core.checkstat:: 268 Determines which stat fields to match between the index 269 and work tree. The user can set this to 'default' or 270 'minimal'. Default (or explicitly 'default'), is to check 271 all fields, including the sub-second part of mtime and ctime. 272 273core.quotepath:: 274 The commands that output paths (e.g. 'ls-files', 275 'diff'), when not given the `-z` option, will quote 276 "unusual" characters in the pathname by enclosing the 277 pathname in a double-quote pair and with backslashes the 278 same way strings in C source code are quoted. If this 279 variable is set to false, the bytes higher than 0x80 are 280 not quoted but output as verbatim. Note that double 281 quote, backslash and control characters are always 282 quoted without `-z` regardless of the setting of this 283 variable. 284 285core.eol:: 286 Sets the line ending type to use in the working directory for 287 files that have the `text` property set. Alternatives are 288 'lf', 'crlf' and 'native', which uses the platform's native 289 line ending. The default value is `native`. See 290 linkgit:gitattributes[5] for more information on end-of-line 291 conversion. 292 293core.safecrlf:: 294 If true, makes Git check if converting `CRLF` is reversible when 295 end-of-line conversion is active. Git will verify if a command 296 modifies a file in the work tree either directly or indirectly. 297 For example, committing a file followed by checking out the 298 same file should yield the original file in the work tree. If 299 this is not the case for the current setting of 300 `core.autocrlf`, Git will reject the file. The variable can 301 be set to "warn", in which case Git will only warn about an 302 irreversible conversion but continue the operation. 303+ 304CRLF conversion bears a slight chance of corrupting data. 305When it is enabled, Git will convert CRLF to LF during commit and LF to 306CRLF during checkout. A file that contains a mixture of LF and 307CRLF before the commit cannot be recreated by Git. For text 308files this is the right thing to do: it corrects line endings 309such that we have only LF line endings in the repository. 310But for binary files that are accidentally classified as text the 311conversion can corrupt data. 312+ 313If you recognize such corruption early you can easily fix it by 314setting the conversion type explicitly in .gitattributes. Right 315after committing you still have the original file in your work 316tree and this file is not yet corrupted. You can explicitly tell 317Git that this file is binary and Git will handle the file 318appropriately. 319+ 320Unfortunately, the desired effect of cleaning up text files with 321mixed line endings and the undesired effect of corrupting binary 322files cannot be distinguished. In both cases CRLFs are removed 323in an irreversible way. For text files this is the right thing 324to do because CRLFs are line endings, while for binary files 325converting CRLFs corrupts data. 326+ 327Note, this safety check does not mean that a checkout will generate a 328file identical to the original file for a different setting of 329`core.eol` and `core.autocrlf`, but only for the current one. For 330example, a text file with `LF` would be accepted with `core.eol=lf` 331and could later be checked out with `core.eol=crlf`, in which case the 332resulting file would contain `CRLF`, although the original file 333contained `LF`. However, in both work trees the line endings would be 334consistent, that is either all `LF` or all `CRLF`, but never mixed. A 335file with mixed line endings would be reported by the `core.safecrlf` 336mechanism. 337 338core.autocrlf:: 339 Setting this variable to "true" is almost the same as setting 340 the `text` attribute to "auto" on all files except that text 341 files are not guaranteed to be normalized: files that contain 342 `CRLF` in the repository will not be touched. Use this 343 setting if you want to have `CRLF` line endings in your 344 working directory even though the repository does not have 345 normalized line endings. This variable can be set to 'input', 346 in which case no output conversion is performed. 347 348core.symlinks:: 349 If false, symbolic links are checked out as small plain files that 350 contain the link text. linkgit:git-update-index[1] and 351 linkgit:git-add[1] will not change the recorded type to regular 352 file. Useful on filesystems like FAT that do not support 353 symbolic links. 354+ 355The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 356will probe and set core.symlinks false if appropriate when the repository 357is created. 358 359core.gitProxy:: 360 A "proxy command" to execute (as 'command host port') instead 361 of establishing direct connection to the remote server when 362 using the Git protocol for fetching. If the variable value is 363 in the "COMMAND for DOMAIN" format, the command is applied only 364 on hostnames ending with the specified domain string. This variable 365 may be set multiple times and is matched in the given order; 366 the first match wins. 367+ 368Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 369(which always applies universally, without the special "for" 370handling). 371+ 372The special string `none` can be used as the proxy command to 373specify that no proxy be used for a given domain pattern. 374This is useful for excluding servers inside a firewall from 375proxy use, while defaulting to a common proxy for external domains. 376 377core.ignoreStat:: 378 If true, commands which modify both the working tree and the index 379 will mark the updated paths with the "assume unchanged" bit in the 380 index. These marked files are then assumed to stay unchanged in the 381 working tree, until you mark them otherwise manually - Git will not 382 detect the file changes by lstat() calls. This is useful on systems 383 where those are very slow, such as Microsoft Windows. 384 See linkgit:git-update-index[1]. 385 False by default. 386 387core.preferSymlinkRefs:: 388 Instead of the default "symref" format for HEAD 389 and other symbolic reference files, use symbolic links. 390 This is sometimes needed to work with old scripts that 391 expect HEAD to be a symbolic link. 392 393core.bare:: 394 If true this repository is assumed to be 'bare' and has no 395 working directory associated with it. If this is the case a 396 number of commands that require a working directory will be 397 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 398+ 399This setting is automatically guessed by linkgit:git-clone[1] or 400linkgit:git-init[1] when the repository was created. By default a 401repository that ends in "/.git" is assumed to be not bare (bare = 402false), while all other repositories are assumed to be bare (bare 403= true). 404 405core.worktree:: 406 Set the path to the root of the working tree. 407 This can be overridden by the GIT_WORK_TREE environment 408 variable and the '--work-tree' command-line option. 409 The value can be an absolute path or relative to the path to 410 the .git directory, which is either specified by --git-dir 411 or GIT_DIR, or automatically discovered. 412 If --git-dir or GIT_DIR is specified but none of 413 --work-tree, GIT_WORK_TREE and core.worktree is specified, 414 the current working directory is regarded as the top level 415 of your working tree. 416+ 417Note that this variable is honored even when set in a configuration 418file in a ".git" subdirectory of a directory and its value differs 419from the latter directory (e.g. "/path/to/.git/config" has 420core.worktree set to "/different/path"), which is most likely a 421misconfiguration. Running Git commands in the "/path/to" directory will 422still use "/different/path" as the root of the work tree and can cause 423confusion unless you know what you are doing (e.g. you are creating a 424read-only snapshot of the same index to a location different from the 425repository's usual working tree). 426 427core.logAllRefUpdates:: 428 Enable the reflog. Updates to a ref <ref> is logged to the file 429 "$GIT_DIR/logs/<ref>", by appending the new and old 430 SHA-1, the date/time and the reason of the update, but 431 only when the file exists. If this configuration 432 variable is set to true, missing "$GIT_DIR/logs/<ref>" 433 file is automatically created for branch heads (i.e. under 434 refs/heads/), remote refs (i.e. under refs/remotes/), 435 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 436+ 437This information can be used to determine what commit 438was the tip of a branch "2 days ago". 439+ 440This value is true by default in a repository that has 441a working directory associated with it, and false by 442default in a bare repository. 443 444core.repositoryFormatVersion:: 445 Internal variable identifying the repository format and layout 446 version. 447 448core.sharedRepository:: 449 When 'group' (or 'true'), the repository is made shareable between 450 several users in a group (making sure all the files and objects are 451 group-writable). When 'all' (or 'world' or 'everybody'), the 452 repository will be readable by all users, additionally to being 453 group-shareable. When 'umask' (or 'false'), Git will use permissions 454 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 455 files in the repository will have this mode value. '0xxx' will override 456 user's umask value (whereas the other options will only override 457 requested parts of the user's umask value). Examples: '0660' will make 458 the repo read/write-able for the owner and group, but inaccessible to 459 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 460 repository that is group-readable but not group-writable. 461 See linkgit:git-init[1]. False by default. 462 463core.warnAmbiguousRefs:: 464 If true, Git will warn you if the ref name you passed it is ambiguous 465 and might match multiple refs in the repository. True by default. 466 467core.compression:: 468 An integer -1..9, indicating a default compression level. 469 -1 is the zlib default. 0 means no compression, 470 and 1..9 are various speed/size tradeoffs, 9 being slowest. 471 If set, this provides a default to other compression variables, 472 such as 'core.loosecompression' and 'pack.compression'. 473 474core.loosecompression:: 475 An integer -1..9, indicating the compression level for objects that 476 are not in a pack file. -1 is the zlib default. 0 means no 477 compression, and 1..9 are various speed/size tradeoffs, 9 being 478 slowest. If not set, defaults to core.compression. If that is 479 not set, defaults to 1 (best speed). 480 481core.packedGitWindowSize:: 482 Number of bytes of a pack file to map into memory in a 483 single mapping operation. Larger window sizes may allow 484 your system to process a smaller number of large pack files 485 more quickly. Smaller window sizes will negatively affect 486 performance due to increased calls to the operating system's 487 memory manager, but may improve performance when accessing 488 a large number of large pack files. 489+ 490Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 491MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 492be reasonable for all users/operating systems. You probably do 493not need to adjust this value. 494+ 495Common unit suffixes of 'k', 'm', or 'g' are supported. 496 497core.packedGitLimit:: 498 Maximum number of bytes to map simultaneously into memory 499 from pack files. If Git needs to access more than this many 500 bytes at once to complete an operation it will unmap existing 501 regions to reclaim virtual address space within the process. 502+ 503Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 504This should be reasonable for all users/operating systems, except on 505the largest projects. You probably do not need to adjust this value. 506+ 507Common unit suffixes of 'k', 'm', or 'g' are supported. 508 509core.deltaBaseCacheLimit:: 510 Maximum number of bytes to reserve for caching base objects 511 that may be referenced by multiple deltified objects. By storing the 512 entire decompressed base objects in a cache Git is able 513 to avoid unpacking and decompressing frequently used base 514 objects multiple times. 515+ 516Default is 96 MiB on all platforms. This should be reasonable 517for all users/operating systems, except on the largest projects. 518You probably do not need to adjust this value. 519+ 520Common unit suffixes of 'k', 'm', or 'g' are supported. 521 522core.bigFileThreshold:: 523 Files larger than this size are stored deflated, without 524 attempting delta compression. Storing large files without 525 delta compression avoids excessive memory usage, at the 526 slight expense of increased disk usage. Additionally files 527 larger than this size are always treated as binary. 528+ 529Default is 512 MiB on all platforms. This should be reasonable 530for most projects as source code and other text files can still 531be delta compressed, but larger binary media files won't be. 532+ 533Common unit suffixes of 'k', 'm', or 'g' are supported. 534 535core.excludesfile:: 536 In addition to '.gitignore' (per-directory) and 537 '.git/info/exclude', Git looks into this file for patterns 538 of files which are not meant to be tracked. "`~/`" is expanded 539 to the value of `$HOME` and "`~user/`" to the specified user's 540 home directory. Its default value is $XDG_CONFIG_HOME/git/ignore. 541 If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore 542 is used instead. See linkgit:gitignore[5]. 543 544core.askpass:: 545 Some commands (e.g. svn and http interfaces) that interactively 546 ask for a password can be told to use an external program given 547 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 548 environment variable. If not set, fall back to the value of the 549 'SSH_ASKPASS' environment variable or, failing that, a simple password 550 prompt. The external program shall be given a suitable prompt as 551 command-line argument and write the password on its STDOUT. 552 553core.attributesfile:: 554 In addition to '.gitattributes' (per-directory) and 555 '.git/info/attributes', Git looks into this file for attributes 556 (see linkgit:gitattributes[5]). Path expansions are made the same 557 way as for `core.excludesfile`. Its default value is 558 $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not 559 set or empty, $HOME/.config/git/attributes is used instead. 560 561core.editor:: 562 Commands such as `commit` and `tag` that lets you edit 563 messages by launching an editor uses the value of this 564 variable when it is set, and the environment variable 565 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 566 567core.commentchar:: 568 Commands such as `commit` and `tag` that lets you edit 569 messages consider a line that begins with this character 570 commented, and removes them after the editor returns 571 (default '#'). 572+ 573If set to "auto", `git-commit` would select a character that is not 574the beginning character of any line in existing commit messages. 575 576sequence.editor:: 577 Text editor used by `git rebase -i` for editing the rebase instruction file. 578 The value is meant to be interpreted by the shell when it is used. 579 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 580 When not configured the default commit message editor is used instead. 581 582core.pager:: 583 Text viewer for use by Git commands (e.g., 'less'). The value 584 is meant to be interpreted by the shell. The order of preference 585 is the `$GIT_PAGER` environment variable, then `core.pager` 586 configuration, then `$PAGER`, and then the default chosen at 587 compile time (usually 'less'). 588+ 589When the `LESS` environment variable is unset, Git sets it to `FRX` 590(if `LESS` environment variable is set, Git does not change it at 591all). If you want to selectively override Git's default setting 592for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 593be passed to the shell by Git, which will translate the final 594command to `LESS=FRX less -S`. The environment does not set the 595`S` option but the command line does, instructing less to truncate 596long lines. Similarly, setting `core.pager` to `less -+F` will 597deactivate the `F` option specified by the environment from the 598command-line, deactivating the "quit if one screen" behavior of 599`less`. One can specifically activate some flags for particular 600commands: for example, setting `pager.blame` to `less -S` enables 601line truncation only for `git blame`. 602+ 603Likewise, when the `LV` environment variable is unset, Git sets it 604to `-c`. You can override this setting by exporting `LV` with 605another value or setting `core.pager` to `lv +c`. 606 607core.whitespace:: 608 A comma separated list of common whitespace problems to 609 notice. 'git diff' will use `color.diff.whitespace` to 610 highlight them, and 'git apply --whitespace=error' will 611 consider them as errors. You can prefix `-` to disable 612 any of them (e.g. `-trailing-space`): 613+ 614* `blank-at-eol` treats trailing whitespaces at the end of the line 615 as an error (enabled by default). 616* `space-before-tab` treats a space character that appears immediately 617 before a tab character in the initial indent part of the line as an 618 error (enabled by default). 619* `indent-with-non-tab` treats a line that is indented with space 620 characters instead of the equivalent tabs as an error (not enabled by 621 default). 622* `tab-in-indent` treats a tab character in the initial indent part of 623 the line as an error (not enabled by default). 624* `blank-at-eof` treats blank lines added at the end of file as an error 625 (enabled by default). 626* `trailing-space` is a short-hand to cover both `blank-at-eol` and 627 `blank-at-eof`. 628* `cr-at-eol` treats a carriage-return at the end of line as 629 part of the line terminator, i.e. with it, `trailing-space` 630 does not trigger if the character before such a carriage-return 631 is not a whitespace (not enabled by default). 632* `tabwidth=<n>` tells how many character positions a tab occupies; this 633 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 634 errors. The default tab width is 8. Allowed values are 1 to 63. 635 636core.fsyncobjectfiles:: 637 This boolean will enable 'fsync()' when writing object files. 638+ 639This is a total waste of time and effort on a filesystem that orders 640data writes properly, but can be useful for filesystems that do not use 641journalling (traditional UNIX filesystems) or that only journal metadata 642and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 643 644core.preloadindex:: 645 Enable parallel index preload for operations like 'git diff' 646+ 647This can speed up operations like 'git diff' and 'git status' especially 648on filesystems like NFS that have weak caching semantics and thus 649relatively high IO latencies. When enabled, Git will do the 650index comparison to the filesystem data in parallel, allowing 651overlapping IO's. Defaults to true. 652 653core.createObject:: 654 You can set this to 'link', in which case a hardlink followed by 655 a delete of the source are used to make sure that object creation 656 will not overwrite existing objects. 657+ 658On some file system/operating system combinations, this is unreliable. 659Set this config setting to 'rename' there; However, This will remove the 660check that makes sure that existing object files will not get overwritten. 661 662core.notesRef:: 663 When showing commit messages, also show notes which are stored in 664 the given ref. The ref must be fully qualified. If the given 665 ref does not exist, it is not an error but means that no 666 notes should be printed. 667+ 668This setting defaults to "refs/notes/commits", and it can be overridden by 669the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 670 671core.sparseCheckout:: 672 Enable "sparse checkout" feature. See section "Sparse checkout" in 673 linkgit:git-read-tree[1] for more information. 674 675core.abbrev:: 676 Set the length object names are abbreviated to. If unspecified, 677 many commands abbreviate to 7 hexdigits, which may not be enough 678 for abbreviated object names to stay unique for sufficiently long 679 time. 680 681add.ignore-errors:: 682add.ignoreErrors:: 683 Tells 'git add' to continue adding files when some files cannot be 684 added due to indexing errors. Equivalent to the '--ignore-errors' 685 option of linkgit:git-add[1]. Older versions of Git accept only 686 `add.ignore-errors`, which does not follow the usual naming 687 convention for configuration variables. Newer versions of Git 688 honor `add.ignoreErrors` as well. 689 690alias.*:: 691 Command aliases for the linkgit:git[1] command wrapper - e.g. 692 after defining "alias.last = cat-file commit HEAD", the invocation 693 "git last" is equivalent to "git cat-file commit HEAD". To avoid 694 confusion and troubles with script usage, aliases that 695 hide existing Git commands are ignored. Arguments are split by 696 spaces, the usual shell quoting and escaping is supported. 697 A quote pair or a backslash can be used to quote them. 698+ 699If the alias expansion is prefixed with an exclamation point, 700it will be treated as a shell command. For example, defining 701"alias.new = !gitk --all --not ORIG_HEAD", the invocation 702"git new" is equivalent to running the shell command 703"gitk --all --not ORIG_HEAD". Note that shell commands will be 704executed from the top-level directory of a repository, which may 705not necessarily be the current directory. 706'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 707from the original current directory. See linkgit:git-rev-parse[1]. 708 709am.keepcr:: 710 If true, git-am will call git-mailsplit for patches in mbox format 711 with parameter '--keep-cr'. In this case git-mailsplit will 712 not remove `\r` from lines ending with `\r\n`. Can be overridden 713 by giving '--no-keep-cr' from the command line. 714 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 715 716apply.ignorewhitespace:: 717 When set to 'change', tells 'git apply' to ignore changes in 718 whitespace, in the same way as the '--ignore-space-change' 719 option. 720 When set to one of: no, none, never, false tells 'git apply' to 721 respect all whitespace differences. 722 See linkgit:git-apply[1]. 723 724apply.whitespace:: 725 Tells 'git apply' how to handle whitespaces, in the same way 726 as the '--whitespace' option. See linkgit:git-apply[1]. 727 728branch.autosetupmerge:: 729 Tells 'git branch' and 'git checkout' to set up new branches 730 so that linkgit:git-pull[1] will appropriately merge from the 731 starting point branch. Note that even if this option is not set, 732 this behavior can be chosen per-branch using the `--track` 733 and `--no-track` options. The valid settings are: `false` -- no 734 automatic setup is done; `true` -- automatic setup is done when the 735 starting point is a remote-tracking branch; `always` -- 736 automatic setup is done when the starting point is either a 737 local branch or remote-tracking 738 branch. This option defaults to true. 739 740branch.autosetuprebase:: 741 When a new branch is created with 'git branch' or 'git checkout' 742 that tracks another branch, this variable tells Git to set 743 up pull to rebase instead of merge (see "branch.<name>.rebase"). 744 When `never`, rebase is never automatically set to true. 745 When `local`, rebase is set to true for tracked branches of 746 other local branches. 747 When `remote`, rebase is set to true for tracked branches of 748 remote-tracking branches. 749 When `always`, rebase will be set to true for all tracking 750 branches. 751 See "branch.autosetupmerge" for details on how to set up a 752 branch to track another branch. 753 This option defaults to never. 754 755branch.<name>.remote:: 756 When on branch <name>, it tells 'git fetch' and 'git push' 757 which remote to fetch from/push to. The remote to push to 758 may be overridden with `remote.pushdefault` (for all branches). 759 The remote to push to, for the current branch, may be further 760 overridden by `branch.<name>.pushremote`. If no remote is 761 configured, or if you are not on any branch, it defaults to 762 `origin` for fetching and `remote.pushdefault` for pushing. 763 Additionally, `.` (a period) is the current local repository 764 (a dot-repository), see `branch.<name>.merge`'s final note below. 765 766branch.<name>.pushremote:: 767 When on branch <name>, it overrides `branch.<name>.remote` for 768 pushing. It also overrides `remote.pushdefault` for pushing 769 from branch <name>. When you pull from one place (e.g. your 770 upstream) and push to another place (e.g. your own publishing 771 repository), you would want to set `remote.pushdefault` to 772 specify the remote to push to for all branches, and use this 773 option to override it for a specific branch. 774 775branch.<name>.merge:: 776 Defines, together with branch.<name>.remote, the upstream branch 777 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 778 branch to merge and can also affect 'git push' (see push.default). 779 When in branch <name>, it tells 'git fetch' the default 780 refspec to be marked for merging in FETCH_HEAD. The value is 781 handled like the remote part of a refspec, and must match a 782 ref which is fetched from the remote given by 783 "branch.<name>.remote". 784 The merge information is used by 'git pull' (which at first calls 785 'git fetch') to lookup the default branch for merging. Without 786 this option, 'git pull' defaults to merge the first refspec fetched. 787 Specify multiple values to get an octopus merge. 788 If you wish to setup 'git pull' so that it merges into <name> from 789 another branch in the local repository, you can point 790 branch.<name>.merge to the desired branch, and use the relative path 791 setting `.` (a period) for branch.<name>.remote. 792 793branch.<name>.mergeoptions:: 794 Sets default options for merging into branch <name>. The syntax and 795 supported options are the same as those of linkgit:git-merge[1], but 796 option values containing whitespace characters are currently not 797 supported. 798 799branch.<name>.rebase:: 800 When true, rebase the branch <name> on top of the fetched branch, 801 instead of merging the default branch from the default remote when 802 "git pull" is run. See "pull.rebase" for doing this in a non 803 branch-specific manner. 804+ 805 When preserve, also pass `--preserve-merges` along to 'git rebase' 806 so that locally committed merge commits will not be flattened 807 by running 'git pull'. 808+ 809*NOTE*: this is a possibly dangerous operation; do *not* use 810it unless you understand the implications (see linkgit:git-rebase[1] 811for details). 812 813branch.<name>.description:: 814 Branch description, can be edited with 815 `git branch --edit-description`. Branch description is 816 automatically added in the format-patch cover letter or 817 request-pull summary. 818 819browser.<tool>.cmd:: 820 Specify the command to invoke the specified browser. The 821 specified command is evaluated in shell with the URLs passed 822 as arguments. (See linkgit:git-web{litdd}browse[1].) 823 824browser.<tool>.path:: 825 Override the path for the given tool that may be used to 826 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 827 working repository in gitweb (see linkgit:git-instaweb[1]). 828 829clean.requireForce:: 830 A boolean to make git-clean do nothing unless given -f, 831 -i or -n. Defaults to true. 832 833color.branch:: 834 A boolean to enable/disable color in the output of 835 linkgit:git-branch[1]. May be set to `always`, 836 `false` (or `never`) or `auto` (or `true`), in which case colors are used 837 only when the output is to a terminal. Defaults to false. 838 839color.branch.<slot>:: 840 Use customized color for branch coloration. `<slot>` is one of 841 `current` (the current branch), `local` (a local branch), 842 `remote` (a remote-tracking branch in refs/remotes/), 843 `upstream` (upstream tracking branch), `plain` (other 844 refs). 845+ 846The value for these configuration variables is a list of colors (at most 847two) and attributes (at most one), separated by spaces. The colors 848accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 849`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 850`blink` and `reverse`. The first color given is the foreground; the 851second is the background. The position of the attribute, if any, 852doesn't matter. 853 854color.diff:: 855 Whether to use ANSI escape sequences to add color to patches. 856 If this is set to `always`, linkgit:git-diff[1], 857 linkgit:git-log[1], and linkgit:git-show[1] will use color 858 for all patches. If it is set to `true` or `auto`, those 859 commands will only use color when output is to the terminal. 860 Defaults to false. 861+ 862This does not affect linkgit:git-format-patch[1] or the 863'git-diff-{asterisk}' plumbing commands. Can be overridden on the 864command line with the `--color[=<when>]` option. 865 866color.diff.<slot>:: 867 Use customized color for diff colorization. `<slot>` specifies 868 which part of the patch to use the specified color, and is one 869 of `plain` (context text), `meta` (metainformation), `frag` 870 (hunk header), 'func' (function in hunk header), `old` (removed lines), 871 `new` (added lines), `commit` (commit headers), or `whitespace` 872 (highlighting whitespace errors). The values of these variables may be 873 specified as in color.branch.<slot>. 874 875color.decorate.<slot>:: 876 Use customized color for 'git log --decorate' output. `<slot>` is one 877 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 878 branches, remote-tracking branches, tags, stash and HEAD, respectively. 879 880color.grep:: 881 When set to `always`, always highlight matches. When `false` (or 882 `never`), never. When set to `true` or `auto`, use color only 883 when the output is written to the terminal. Defaults to `false`. 884 885color.grep.<slot>:: 886 Use customized color for grep colorization. `<slot>` specifies which 887 part of the line to use the specified color, and is one of 888+ 889-- 890`context`;; 891 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 892`filename`;; 893 filename prefix (when not using `-h`) 894`function`;; 895 function name lines (when using `-p`) 896`linenumber`;; 897 line number prefix (when using `-n`) 898`match`;; 899 matching text (same as setting `matchContext` and `matchSelected`) 900`matchContext`;; 901 matching text in context lines 902`matchSelected`;; 903 matching text in selected lines 904`selected`;; 905 non-matching text in selected lines 906`separator`;; 907 separators between fields on a line (`:`, `-`, and `=`) 908 and between hunks (`--`) 909-- 910+ 911The values of these variables may be specified as in color.branch.<slot>. 912 913color.interactive:: 914 When set to `always`, always use colors for interactive prompts 915 and displays (such as those used by "git-add --interactive" and 916 "git-clean --interactive"). When false (or `never`), never. 917 When set to `true` or `auto`, use colors only when the output is 918 to the terminal. Defaults to false. 919 920color.interactive.<slot>:: 921 Use customized color for 'git add --interactive' and 'git clean 922 --interactive' output. `<slot>` may be `prompt`, `header`, `help` 923 or `error`, for four distinct types of normal output from 924 interactive commands. The values of these variables may be 925 specified as in color.branch.<slot>. 926 927color.pager:: 928 A boolean to enable/disable colored output when the pager is in 929 use (default is true). 930 931color.showbranch:: 932 A boolean to enable/disable color in the output of 933 linkgit:git-show-branch[1]. May be set to `always`, 934 `false` (or `never`) or `auto` (or `true`), in which case colors are used 935 only when the output is to a terminal. Defaults to false. 936 937color.status:: 938 A boolean to enable/disable color in the output of 939 linkgit:git-status[1]. May be set to `always`, 940 `false` (or `never`) or `auto` (or `true`), in which case colors are used 941 only when the output is to a terminal. Defaults to false. 942 943color.status.<slot>:: 944 Use customized color for status colorization. `<slot>` is 945 one of `header` (the header text of the status message), 946 `added` or `updated` (files which are added but not committed), 947 `changed` (files which are changed but not added in the index), 948 `untracked` (files which are not tracked by Git), 949 `branch` (the current branch), or 950 `nobranch` (the color the 'no branch' warning is shown in, defaulting 951 to red). The values of these variables may be specified as in 952 color.branch.<slot>. 953 954color.ui:: 955 This variable determines the default value for variables such 956 as `color.diff` and `color.grep` that control the use of color 957 per command family. Its scope will expand as more commands learn 958 configuration to set a default for the `--color` option. Set it 959 to `false` or `never` if you prefer Git commands not to use 960 color unless enabled explicitly with some other configuration 961 or the `--color` option. Set it to `always` if you want all 962 output not intended for machine consumption to use color, to 963 `true` or `auto` (this is the default since Git 1.8.4) if you 964 want such output to use color when written to the terminal. 965 966column.ui:: 967 Specify whether supported commands should output in columns. 968 This variable consists of a list of tokens separated by spaces 969 or commas: 970+ 971These options control when the feature should be enabled 972(defaults to 'never'): 973+ 974-- 975`always`;; 976 always show in columns 977`never`;; 978 never show in columns 979`auto`;; 980 show in columns if the output is to the terminal 981-- 982+ 983These options control layout (defaults to 'column'). Setting any 984of these implies 'always' if none of 'always', 'never', or 'auto' are 985specified. 986+ 987-- 988`column`;; 989 fill columns before rows 990`row`;; 991 fill rows before columns 992`plain`;; 993 show in one column 994-- 995+ 996Finally, these options can be combined with a layout option (defaults 997to 'nodense'): 998+ 999--1000`dense`;;1001 make unequal size columns to utilize more space1002`nodense`;;1003 make equal size columns1004--10051006column.branch::1007 Specify whether to output branch listing in `git branch` in columns.1008 See `column.ui` for details.10091010column.clean::1011 Specify the layout when list items in `git clean -i`, which always1012 shows files and directories in columns. See `column.ui` for details.10131014column.status::1015 Specify whether to output untracked files in `git status` in columns.1016 See `column.ui` for details.10171018column.tag::1019 Specify whether to output tag listing in `git tag` in columns.1020 See `column.ui` for details.10211022commit.cleanup::1023 This setting overrides the default of the `--cleanup` option in1024 `git commit`. See linkgit:git-commit[1] for details. Changing the1025 default can be useful when you always want to keep lines that begin1026 with comment character `#` in your log message, in which case you1027 would do `git config commit.cleanup whitespace` (note that you will1028 have to remove the help lines that begin with `#` in the commit log1029 template yourself, if you do this).10301031commit.gpgsign::10321033 A boolean to specify whether all commits should be GPG signed.1034 Use of this option when doing operations such as rebase can1035 result in a large number of commits being signed. It may be1036 convenient to use an agent to avoid typing your GPG passphrase1037 several times.10381039commit.status::1040 A boolean to enable/disable inclusion of status information in the1041 commit message template when using an editor to prepare the commit1042 message. Defaults to true.10431044commit.template::1045 Specify a file to use as the template for new commit messages.1046 "`~/`" is expanded to the value of `$HOME` and "`~user/`" to the1047 specified user's home directory.10481049credential.helper::1050 Specify an external helper to be called when a username or1051 password credential is needed; the helper may consult external1052 storage to avoid prompting the user for the credentials. See1053 linkgit:gitcredentials[7] for details.10541055credential.useHttpPath::1056 When acquiring credentials, consider the "path" component of an http1057 or https URL to be important. Defaults to false. See1058 linkgit:gitcredentials[7] for more information.10591060credential.username::1061 If no username is set for a network authentication, use this username1062 by default. See credential.<context>.* below, and1063 linkgit:gitcredentials[7].10641065credential.<url>.*::1066 Any of the credential.* options above can be applied selectively to1067 some credentials. For example "credential.https://example.com.username"1068 would set the default username only for https connections to1069 example.com. See linkgit:gitcredentials[7] for details on how URLs are1070 matched.10711072include::diff-config.txt[]10731074difftool.<tool>.path::1075 Override the path for the given tool. This is useful in case1076 your tool is not in the PATH.10771078difftool.<tool>.cmd::1079 Specify the command to invoke the specified diff tool.1080 The specified command is evaluated in shell with the following1081 variables available: 'LOCAL' is set to the name of the temporary1082 file containing the contents of the diff pre-image and 'REMOTE'1083 is set to the name of the temporary file containing the contents1084 of the diff post-image.10851086difftool.prompt::1087 Prompt before each invocation of the diff tool.10881089fetch.recurseSubmodules::1090 This option can be either set to a boolean value or to 'on-demand'.1091 Setting it to a boolean changes the behavior of fetch and pull to1092 unconditionally recurse into submodules when set to true or to not1093 recurse at all when set to false. When set to 'on-demand' (the default1094 value), fetch and pull will only recurse into a populated submodule1095 when its superproject retrieves a commit that updates the submodule's1096 reference.10971098fetch.fsckObjects::1099 If it is set to true, git-fetch-pack will check all fetched1100 objects. It will abort in the case of a malformed object or a1101 broken link. The result of an abort are only dangling objects.1102 Defaults to false. If not set, the value of `transfer.fsckObjects`1103 is used instead.11041105fetch.unpackLimit::1106 If the number of objects fetched over the Git native1107 transfer is below this1108 limit, then the objects will be unpacked into loose object1109 files. However if the number of received objects equals or1110 exceeds this limit then the received pack will be stored as1111 a pack, after adding any missing delta bases. Storing the1112 pack from a push can make the push operation complete faster,1113 especially on slow filesystems. If not set, the value of1114 `transfer.unpackLimit` is used instead.11151116fetch.prune::1117 If true, fetch will automatically behave as if the `--prune`1118 option was given on the command line. See also `remote.<name>.prune`.11191120format.attach::1121 Enable multipart/mixed attachments as the default for1122 'format-patch'. The value can also be a double quoted string1123 which will enable attachments as the default and set the1124 value as the boundary. See the --attach option in1125 linkgit:git-format-patch[1].11261127format.numbered::1128 A boolean which can enable or disable sequence numbers in patch1129 subjects. It defaults to "auto" which enables it only if there1130 is more than one patch. It can be enabled or disabled for all1131 messages by setting it to "true" or "false". See --numbered1132 option in linkgit:git-format-patch[1].11331134format.headers::1135 Additional email headers to include in a patch to be submitted1136 by mail. See linkgit:git-format-patch[1].11371138format.to::1139format.cc::1140 Additional recipients to include in a patch to be submitted1141 by mail. See the --to and --cc options in1142 linkgit:git-format-patch[1].11431144format.subjectprefix::1145 The default for format-patch is to output files with the '[PATCH]'1146 subject prefix. Use this variable to change that prefix.11471148format.signature::1149 The default for format-patch is to output a signature containing1150 the Git version number. Use this variable to change that default.1151 Set this variable to the empty string ("") to suppress1152 signature generation.11531154format.signaturefile::1155 Works just like format.signature except the contents of the1156 file specified by this variable will be used as the signature.11571158format.suffix::1159 The default for format-patch is to output files with the suffix1160 `.patch`. Use this variable to change that suffix (make sure to1161 include the dot if you want it).11621163format.pretty::1164 The default pretty format for log/show/whatchanged command,1165 See linkgit:git-log[1], linkgit:git-show[1],1166 linkgit:git-whatchanged[1].11671168format.thread::1169 The default threading style for 'git format-patch'. Can be1170 a boolean value, or `shallow` or `deep`. `shallow` threading1171 makes every mail a reply to the head of the series,1172 where the head is chosen from the cover letter, the1173 `--in-reply-to`, and the first patch mail, in this order.1174 `deep` threading makes every mail a reply to the previous one.1175 A true boolean value is the same as `shallow`, and a false1176 value disables threading.11771178format.signoff::1179 A boolean value which lets you enable the `-s/--signoff` option of1180 format-patch by default. *Note:* Adding the Signed-off-by: line to a1181 patch should be a conscious act and means that you certify you have1182 the rights to submit this work under the same open source license.1183 Please see the 'SubmittingPatches' document for further discussion.11841185format.coverLetter::1186 A boolean that controls whether to generate a cover-letter when1187 format-patch is invoked, but in addition can be set to "auto", to1188 generate a cover-letter only when there's more than one patch.11891190filter.<driver>.clean::1191 The command which is used to convert the content of a worktree1192 file to a blob upon checkin. See linkgit:gitattributes[5] for1193 details.11941195filter.<driver>.smudge::1196 The command which is used to convert the content of a blob1197 object to a worktree file upon checkout. See1198 linkgit:gitattributes[5] for details.11991200gc.aggressiveDepth::1201 The depth parameter used in the delta compression1202 algorithm used by 'git gc --aggressive'. This defaults1203 to 250.12041205gc.aggressiveWindow::1206 The window size parameter used in the delta compression1207 algorithm used by 'git gc --aggressive'. This defaults1208 to 250.12091210gc.auto::1211 When there are approximately more than this many loose1212 objects in the repository, `git gc --auto` will pack them.1213 Some Porcelain commands use this command to perform a1214 light-weight garbage collection from time to time. The1215 default value is 6700. Setting this to 0 disables it.12161217gc.autopacklimit::1218 When there are more than this many packs that are not1219 marked with `*.keep` file in the repository, `git gc1220 --auto` consolidates them into one larger pack. The1221 default value is 50. Setting this to 0 disables it.12221223gc.autodetach::1224 Make `git gc --auto` return immediately and run in background1225 if the system supports it. Default is true.12261227gc.packrefs::1228 Running `git pack-refs` in a repository renders it1229 unclonable by Git versions prior to 1.5.1.2 over dumb1230 transports such as HTTP. This variable determines whether1231 'git gc' runs `git pack-refs`. This can be set to `notbare`1232 to enable it within all non-bare repos or it can be set to a1233 boolean value. The default is `true`.12341235gc.pruneexpire::1236 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1237 Override the grace period with this config variable. The value1238 "now" may be used to disable this grace period and always prune1239 unreachable objects immediately.12401241gc.reflogexpire::1242gc.<pattern>.reflogexpire::1243 'git reflog expire' removes reflog entries older than1244 this time; defaults to 90 days. With "<pattern>" (e.g.1245 "refs/stash") in the middle the setting applies only to1246 the refs that match the <pattern>.12471248gc.reflogexpireunreachable::1249gc.<ref>.reflogexpireunreachable::1250 'git reflog expire' removes reflog entries older than1251 this time and are not reachable from the current tip;1252 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")1253 in the middle, the setting applies only to the refs that1254 match the <pattern>.12551256gc.rerereresolved::1257 Records of conflicted merge you resolved earlier are1258 kept for this many days when 'git rerere gc' is run.1259 The default is 60 days. See linkgit:git-rerere[1].12601261gc.rerereunresolved::1262 Records of conflicted merge you have not resolved are1263 kept for this many days when 'git rerere gc' is run.1264 The default is 15 days. See linkgit:git-rerere[1].12651266gitcvs.commitmsgannotation::1267 Append this string to each commit message. Set to empty string1268 to disable this feature. Defaults to "via git-CVS emulator".12691270gitcvs.enabled::1271 Whether the CVS server interface is enabled for this repository.1272 See linkgit:git-cvsserver[1].12731274gitcvs.logfile::1275 Path to a log file where the CVS server interface well... logs1276 various stuff. See linkgit:git-cvsserver[1].12771278gitcvs.usecrlfattr::1279 If true, the server will look up the end-of-line conversion1280 attributes for files to determine the '-k' modes to use. If1281 the attributes force Git to treat a file as text,1282 the '-k' mode will be left blank so CVS clients will1283 treat it as text. If they suppress text conversion, the file1284 will be set with '-kb' mode, which suppresses any newline munging1285 the client might otherwise do. If the attributes do not allow1286 the file type to be determined, then 'gitcvs.allbinary' is1287 used. See linkgit:gitattributes[5].12881289gitcvs.allbinary::1290 This is used if 'gitcvs.usecrlfattr' does not resolve1291 the correct '-kb' mode to use. If true, all1292 unresolved files are sent to the client in1293 mode '-kb'. This causes the client to treat them1294 as binary files, which suppresses any newline munging it1295 otherwise might do. Alternatively, if it is set to "guess",1296 then the contents of the file are examined to decide if1297 it is binary, similar to 'core.autocrlf'.12981299gitcvs.dbname::1300 Database used by git-cvsserver to cache revision information1301 derived from the Git repository. The exact meaning depends on the1302 used database driver, for SQLite (which is the default driver) this1303 is a filename. Supports variable substitution (see1304 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1305 Default: '%Ggitcvs.%m.sqlite'13061307gitcvs.dbdriver::1308 Used Perl DBI driver. You can specify any available driver1309 for this here, but it might not work. git-cvsserver is tested1310 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1311 reported *not* to work with 'DBD::mysql'. Experimental feature.1312 May not contain double colons (`:`). Default: 'SQLite'.1313 See linkgit:git-cvsserver[1].13141315gitcvs.dbuser, gitcvs.dbpass::1316 Database user and password. Only useful if setting 'gitcvs.dbdriver',1317 since SQLite has no concept of database users and/or passwords.1318 'gitcvs.dbuser' supports variable substitution (see1319 linkgit:git-cvsserver[1] for details).13201321gitcvs.dbTableNamePrefix::1322 Database table name prefix. Prepended to the names of any1323 database tables used, allowing a single database to be used1324 for several repositories. Supports variable substitution (see1325 linkgit:git-cvsserver[1] for details). Any non-alphabetic1326 characters will be replaced with underscores.13271328All gitcvs variables except for 'gitcvs.usecrlfattr' and1329'gitcvs.allbinary' can also be specified as1330'gitcvs.<access_method>.<varname>' (where 'access_method'1331is one of "ext" and "pserver") to make them apply only for the given1332access method.13331334gitweb.category::1335gitweb.description::1336gitweb.owner::1337gitweb.url::1338 See linkgit:gitweb[1] for description.13391340gitweb.avatar::1341gitweb.blame::1342gitweb.grep::1343gitweb.highlight::1344gitweb.patches::1345gitweb.pickaxe::1346gitweb.remote_heads::1347gitweb.showsizes::1348gitweb.snapshot::1349 See linkgit:gitweb.conf[5] for description.13501351grep.lineNumber::1352 If set to true, enable '-n' option by default.13531354grep.patternType::1355 Set the default matching behavior. Using a value of 'basic', 'extended',1356 'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',1357 '--fixed-strings', or '--perl-regexp' option accordingly, while the1358 value 'default' will return to the default matching behavior.13591360grep.extendedRegexp::1361 If set to true, enable '--extended-regexp' option by default. This1362 option is ignored when the 'grep.patternType' option is set to a value1363 other than 'default'.13641365gpg.program::1366 Use this custom program instead of "gpg" found on $PATH when1367 making or verifying a PGP signature. The program must support the1368 same command-line interface as GPG, namely, to verify a detached1369 signature, "gpg --verify $file - <$signature" is run, and the1370 program is expected to signal a good signature by exiting with1371 code 0, and to generate an ASCII-armored detached signature, the1372 standard input of "gpg -bsau $key" is fed with the contents to be1373 signed, and the program is expected to send the result to its1374 standard output.13751376gui.commitmsgwidth::1377 Defines how wide the commit message window is in the1378 linkgit:git-gui[1]. "75" is the default.13791380gui.diffcontext::1381 Specifies how many context lines should be used in calls to diff1382 made by the linkgit:git-gui[1]. The default is "5".13831384gui.displayuntracked::1385 Determines if linkgit::git-gui[1] shows untracked files1386 in the file list. The default is "true".13871388gui.encoding::1389 Specifies the default encoding to use for displaying of1390 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1391 It can be overridden by setting the 'encoding' attribute1392 for relevant files (see linkgit:gitattributes[5]).1393 If this option is not set, the tools default to the1394 locale encoding.13951396gui.matchtrackingbranch::1397 Determines if new branches created with linkgit:git-gui[1] should1398 default to tracking remote branches with matching names or1399 not. Default: "false".14001401gui.newbranchtemplate::1402 Is used as suggested name when creating new branches using the1403 linkgit:git-gui[1].14041405gui.pruneduringfetch::1406 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1407 performing a fetch. The default value is "false".14081409gui.trustmtime::1410 Determines if linkgit:git-gui[1] should trust the file modification1411 timestamp or not. By default the timestamps are not trusted.14121413gui.spellingdictionary::1414 Specifies the dictionary used for spell checking commit messages in1415 the linkgit:git-gui[1]. When set to "none" spell checking is turned1416 off.14171418gui.fastcopyblame::1419 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1420 location detection. It makes blame significantly faster on huge1421 repositories at the expense of less thorough copy detection.14221423gui.copyblamethreshold::1424 Specifies the threshold to use in 'git gui blame' original location1425 detection, measured in alphanumeric characters. See the1426 linkgit:git-blame[1] manual for more information on copy detection.14271428gui.blamehistoryctx::1429 Specifies the radius of history context in days to show in1430 linkgit:gitk[1] for the selected commit, when the `Show History1431 Context` menu item is invoked from 'git gui blame'. If this1432 variable is set to zero, the whole history is shown.14331434guitool.<name>.cmd::1435 Specifies the shell command line to execute when the corresponding item1436 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1437 mandatory for every tool. The command is executed from the root of1438 the working directory, and in the environment it receives the name of1439 the tool as 'GIT_GUITOOL', the name of the currently selected file as1440 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1441 the head is detached, 'CUR_BRANCH' is empty).14421443guitool.<name>.needsfile::1444 Run the tool only if a diff is selected in the GUI. It guarantees1445 that 'FILENAME' is not empty.14461447guitool.<name>.noconsole::1448 Run the command silently, without creating a window to display its1449 output.14501451guitool.<name>.norescan::1452 Don't rescan the working directory for changes after the tool1453 finishes execution.14541455guitool.<name>.confirm::1456 Show a confirmation dialog before actually running the tool.14571458guitool.<name>.argprompt::1459 Request a string argument from the user, and pass it to the tool1460 through the 'ARGS' environment variable. Since requesting an1461 argument implies confirmation, the 'confirm' option has no effect1462 if this is enabled. If the option is set to 'true', 'yes', or '1',1463 the dialog uses a built-in generic prompt; otherwise the exact1464 value of the variable is used.14651466guitool.<name>.revprompt::1467 Request a single valid revision from the user, and set the1468 'REVISION' environment variable. In other aspects this option1469 is similar to 'argprompt', and can be used together with it.14701471guitool.<name>.revunmerged::1472 Show only unmerged branches in the 'revprompt' subdialog.1473 This is useful for tools similar to merge or rebase, but not1474 for things like checkout or reset.14751476guitool.<name>.title::1477 Specifies the title to use for the prompt dialog. The default1478 is the tool name.14791480guitool.<name>.prompt::1481 Specifies the general prompt string to display at the top of1482 the dialog, before subsections for 'argprompt' and 'revprompt'.1483 The default value includes the actual command.14841485help.browser::1486 Specify the browser that will be used to display help in the1487 'web' format. See linkgit:git-help[1].14881489help.format::1490 Override the default help format used by linkgit:git-help[1].1491 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1492 the default. 'web' and 'html' are the same.14931494help.autocorrect::1495 Automatically correct and execute mistyped commands after1496 waiting for the given number of deciseconds (0.1 sec). If more1497 than one command can be deduced from the entered text, nothing1498 will be executed. If the value of this option is negative,1499 the corrected command will be executed immediately. If the1500 value is 0 - the command will be just shown but not executed.1501 This is the default.15021503help.htmlpath::1504 Specify the path where the HTML documentation resides. File system paths1505 and URLs are supported. HTML pages will be prefixed with this path when1506 help is displayed in the 'web' format. This defaults to the documentation1507 path of your Git installation.15081509http.proxy::1510 Override the HTTP proxy, normally configured using the 'http_proxy',1511 'https_proxy', and 'all_proxy' environment variables (see1512 `curl(1)`). This can be overridden on a per-remote basis; see1513 remote.<name>.proxy15141515http.cookiefile::1516 File containing previously stored cookie lines which should be used1517 in the Git http session, if they match the server. The file format1518 of the file to read cookies from should be plain HTTP headers or1519 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1520 NOTE that the file specified with http.cookiefile is only used as1521 input unless http.saveCookies is set.15221523http.savecookies::1524 If set, store cookies received during requests to the file specified by1525 http.cookiefile. Has no effect if http.cookiefile is unset.15261527http.sslVerify::1528 Whether to verify the SSL certificate when fetching or pushing1529 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1530 variable.15311532http.sslCert::1533 File containing the SSL certificate when fetching or pushing1534 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1535 variable.15361537http.sslKey::1538 File containing the SSL private key when fetching or pushing1539 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1540 variable.15411542http.sslCertPasswordProtected::1543 Enable Git's password prompt for the SSL certificate. Otherwise1544 OpenSSL will prompt the user, possibly many times, if the1545 certificate or private key is encrypted. Can be overridden by the1546 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.15471548http.sslCAInfo::1549 File containing the certificates to verify the peer with when1550 fetching or pushing over HTTPS. Can be overridden by the1551 'GIT_SSL_CAINFO' environment variable.15521553http.sslCAPath::1554 Path containing files with the CA certificates to verify the peer1555 with when fetching or pushing over HTTPS. Can be overridden1556 by the 'GIT_SSL_CAPATH' environment variable.15571558http.sslTry::1559 Attempt to use AUTH SSL/TLS and encrypted data transfers1560 when connecting via regular FTP protocol. This might be needed1561 if the FTP server requires it for security reasons or you wish1562 to connect securely whenever remote FTP server supports it.1563 Default is false since it might trigger certificate verification1564 errors on misconfigured servers.15651566http.maxRequests::1567 How many HTTP requests to launch in parallel. Can be overridden1568 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.15691570http.minSessions::1571 The number of curl sessions (counted across slots) to be kept across1572 requests. They will not be ended with curl_easy_cleanup() until1573 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1574 value will be capped at 1. Defaults to 1.15751576http.postBuffer::1577 Maximum size in bytes of the buffer used by smart HTTP1578 transports when POSTing data to the remote system.1579 For requests larger than this buffer size, HTTP/1.1 and1580 Transfer-Encoding: chunked is used to avoid creating a1581 massive pack file locally. Default is 1 MiB, which is1582 sufficient for most requests.15831584http.lowSpeedLimit, http.lowSpeedTime::1585 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1586 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1587 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1588 'GIT_HTTP_LOW_SPEED_TIME' environment variables.15891590http.noEPSV::1591 A boolean which disables using of EPSV ftp command by curl.1592 This can helpful with some "poor" ftp servers which don't1593 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1594 environment variable. Default is false (curl will use EPSV).15951596http.useragent::1597 The HTTP USER_AGENT string presented to an HTTP server. The default1598 value represents the version of the client Git such as git/1.7.1.1599 This option allows you to override this value to a more common value1600 such as Mozilla/4.0. This may be necessary, for instance, if1601 connecting through a firewall that restricts HTTP connections to a set1602 of common USER_AGENT strings (but not including those like git/1.7.1).1603 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.16041605http.<url>.*::1606 Any of the http.* options above can be applied selectively to some URLs.1607 For a config key to match a URL, each element of the config key is1608 compared to that of the URL, in the following order:1609+1610--1611. Scheme (e.g., `https` in `https://example.com/`). This field1612 must match exactly between the config key and the URL.16131614. Host/domain name (e.g., `example.com` in `https://example.com/`).1615 This field must match exactly between the config key and the URL.16161617. Port number (e.g., `8080` in `http://example.com:8080/`).1618 This field must match exactly between the config key and the URL.1619 Omitted port numbers are automatically converted to the correct1620 default for the scheme before matching.16211622. Path (e.g., `repo.git` in `https://example.com/repo.git`). The1623 path field of the config key must match the path field of the URL1624 either exactly or as a prefix of slash-delimited path elements. This means1625 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only1626 match on a slash (`/`) boundary. Longer matches take precedence (so a config1627 key with path `foo/bar` is a better match to URL path `foo/bar` than a config1628 key with just path `foo/`).16291630. User name (e.g., `user` in `https://user@example.com/repo.git`). If1631 the config key has a user name it must match the user name in the1632 URL exactly. If the config key does not have a user name, that1633 config key will match a URL with any user name (including none),1634 but at a lower precedence than a config key with a user name.1635--1636+1637The list above is ordered by decreasing precedence; a URL that matches1638a config key's path is preferred to one that matches its user name. For example,1639if the URL is `https://user@example.com/foo/bar` a config key match of1640`https://example.com/foo` will be preferred over a config key match of1641`https://user@example.com`.1642+1643All URLs are normalized before attempting any matching (the password part,1644if embedded in the URL, is always ignored for matching purposes) so that1645equivalent URLs that are simply spelled differently will match properly.1646Environment variable settings always override any matches. The URLs that are1647matched against are those given directly to Git commands. This means any URLs1648visited as a result of a redirection do not participate in matching.16491650i18n.commitEncoding::1651 Character encoding the commit messages are stored in; Git itself1652 does not care per se, but this information is necessary e.g. when1653 importing commits from emails or in the gitk graphical history1654 browser (and possibly at other places in the future or in other1655 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.16561657i18n.logOutputEncoding::1658 Character encoding the commit messages are converted to when1659 running 'git log' and friends.16601661imap::1662 The configuration variables in the 'imap' section are described1663 in linkgit:git-imap-send[1].16641665index.version::1666 Specify the version with which new index files should be1667 initialized. This does not affect existing repositories.16681669init.templatedir::1670 Specify the directory from which templates will be copied.1671 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)16721673instaweb.browser::1674 Specify the program that will be used to browse your working1675 repository in gitweb. See linkgit:git-instaweb[1].16761677instaweb.httpd::1678 The HTTP daemon command-line to start gitweb on your working1679 repository. See linkgit:git-instaweb[1].16801681instaweb.local::1682 If true the web server started by linkgit:git-instaweb[1] will1683 be bound to the local IP (127.0.0.1).16841685instaweb.modulepath::1686 The default module path for linkgit:git-instaweb[1] to use1687 instead of /usr/lib/apache2/modules. Only used if httpd1688 is Apache.16891690instaweb.port::1691 The port number to bind the gitweb httpd to. See1692 linkgit:git-instaweb[1].16931694interactive.singlekey::1695 In interactive commands, allow the user to provide one-letter1696 input with a single key (i.e., without hitting enter).1697 Currently this is used by the `--patch` mode of1698 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1699 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1700 setting is silently ignored if portable keystroke input1701 is not available; requires the Perl module Term::ReadKey.17021703log.abbrevCommit::1704 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1705 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may1706 override this option with `--no-abbrev-commit`.17071708log.date::1709 Set the default date-time mode for the 'log' command.1710 Setting a value for log.date is similar to using 'git log''s1711 `--date` option. Possible values are `relative`, `local`,1712 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]1713 for details.17141715log.decorate::1716 Print out the ref names of any commits that are shown by the log1717 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1718 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1719 specified, the full ref name (including prefix) will be printed.1720 This is the same as the log commands '--decorate' option.17211722log.showroot::1723 If true, the initial commit will be shown as a big creation event.1724 This is equivalent to a diff against an empty tree.1725 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1726 normally hide the root commit will now show it. True by default.17271728log.mailmap::1729 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1730 linkgit:git-whatchanged[1] assume `--use-mailmap`.17311732mailmap.file::1733 The location of an augmenting mailmap file. The default1734 mailmap, located in the root of the repository, is loaded1735 first, then the mailmap file pointed to by this variable.1736 The location of the mailmap file may be in a repository1737 subdirectory, or somewhere outside of the repository itself.1738 See linkgit:git-shortlog[1] and linkgit:git-blame[1].17391740mailmap.blob::1741 Like `mailmap.file`, but consider the value as a reference to a1742 blob in the repository. If both `mailmap.file` and1743 `mailmap.blob` are given, both are parsed, with entries from1744 `mailmap.file` taking precedence. In a bare repository, this1745 defaults to `HEAD:.mailmap`. In a non-bare repository, it1746 defaults to empty.17471748man.viewer::1749 Specify the programs that may be used to display help in the1750 'man' format. See linkgit:git-help[1].17511752man.<tool>.cmd::1753 Specify the command to invoke the specified man viewer. The1754 specified command is evaluated in shell with the man page1755 passed as argument. (See linkgit:git-help[1].)17561757man.<tool>.path::1758 Override the path for the given tool that may be used to1759 display help in the 'man' format. See linkgit:git-help[1].17601761include::merge-config.txt[]17621763mergetool.<tool>.path::1764 Override the path for the given tool. This is useful in case1765 your tool is not in the PATH.17661767mergetool.<tool>.cmd::1768 Specify the command to invoke the specified merge tool. The1769 specified command is evaluated in shell with the following1770 variables available: 'BASE' is the name of a temporary file1771 containing the common base of the files to be merged, if available;1772 'LOCAL' is the name of a temporary file containing the contents of1773 the file on the current branch; 'REMOTE' is the name of a temporary1774 file containing the contents of the file from the branch being1775 merged; 'MERGED' contains the name of the file to which the merge1776 tool should write the results of a successful merge.17771778mergetool.<tool>.trustExitCode::1779 For a custom merge command, specify whether the exit code of1780 the merge command can be used to determine whether the merge was1781 successful. If this is not set to true then the merge target file1782 timestamp is checked and the merge assumed to have been successful1783 if the file has been updated, otherwise the user is prompted to1784 indicate the success of the merge.17851786mergetool.meld.hasOutput::1787 Older versions of `meld` do not support the `--output` option.1788 Git will attempt to detect whether `meld` supports `--output`1789 by inspecting the output of `meld --help`. Configuring1790 `mergetool.meld.hasOutput` will make Git skip these checks and1791 use the configured value instead. Setting `mergetool.meld.hasOutput`1792 to `true` tells Git to unconditionally use the `--output` option,1793 and `false` avoids using `--output`.17941795mergetool.keepBackup::1796 After performing a merge, the original file with conflict markers1797 can be saved as a file with a `.orig` extension. If this variable1798 is set to `false` then this file is not preserved. Defaults to1799 `true` (i.e. keep the backup files).18001801mergetool.keepTemporaries::1802 When invoking a custom merge tool, Git uses a set of temporary1803 files to pass to the tool. If the tool returns an error and this1804 variable is set to `true`, then these temporary files will be1805 preserved, otherwise they will be removed after the tool has1806 exited. Defaults to `false`.18071808mergetool.writeToTemp::1809 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of1810 conflicting files in the worktree by default. Git will attempt1811 to use a temporary directory for these files when set `true`.1812 Defaults to `false`.18131814mergetool.prompt::1815 Prompt before each invocation of the merge resolution program.18161817notes.displayRef::1818 The (fully qualified) refname from which to show notes when1819 showing commit messages. The value of this variable can be set1820 to a glob, in which case notes from all matching refs will be1821 shown. You may also specify this configuration variable1822 several times. A warning will be issued for refs that do not1823 exist, but a glob that does not match any refs is silently1824 ignored.1825+1826This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1827environment variable, which must be a colon separated list of refs or1828globs.1829+1830The effective value of "core.notesRef" (possibly overridden by1831GIT_NOTES_REF) is also implicitly added to the list of refs to be1832displayed.18331834notes.rewrite.<command>::1835 When rewriting commits with <command> (currently `amend` or1836 `rebase`) and this variable is set to `true`, Git1837 automatically copies your notes from the original to the1838 rewritten commit. Defaults to `true`, but see1839 "notes.rewriteRef" below.18401841notes.rewriteMode::1842 When copying notes during a rewrite (see the1843 "notes.rewrite.<command>" option), determines what to do if1844 the target commit already has a note. Must be one of1845 `overwrite`, `concatenate`, or `ignore`. Defaults to1846 `concatenate`.1847+1848This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1849environment variable.18501851notes.rewriteRef::1852 When copying notes during a rewrite, specifies the (fully1853 qualified) ref whose notes should be copied. The ref may be a1854 glob, in which case notes in all matching refs will be copied.1855 You may also specify this configuration several times.1856+1857Does not have a default value; you must configure this variable to1858enable note rewriting. Set it to `refs/notes/commits` to enable1859rewriting for the default commit notes.1860+1861This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1862environment variable, which must be a colon separated list of refs or1863globs.18641865pack.window::1866 The size of the window used by linkgit:git-pack-objects[1] when no1867 window size is given on the command line. Defaults to 10.18681869pack.depth::1870 The maximum delta depth used by linkgit:git-pack-objects[1] when no1871 maximum depth is given on the command line. Defaults to 50.18721873pack.windowMemory::1874 The maximum size of memory that is consumed by each thread1875 in linkgit:git-pack-objects[1] for pack window memory when1876 no limit is given on the command line. The value can be1877 suffixed with "k", "m", or "g". When left unconfigured (or1878 set explicitly to 0), there will be no limit.18791880pack.compression::1881 An integer -1..9, indicating the compression level for objects1882 in a pack file. -1 is the zlib default. 0 means no1883 compression, and 1..9 are various speed/size tradeoffs, 9 being1884 slowest. If not set, defaults to core.compression. If that is1885 not set, defaults to -1, the zlib default, which is "a default1886 compromise between speed and compression (currently equivalent1887 to level 6)."1888+1889Note that changing the compression level will not automatically recompress1890all existing objects. You can force recompression by passing the -F option1891to linkgit:git-repack[1].18921893pack.deltaCacheSize::1894 The maximum memory in bytes used for caching deltas in1895 linkgit:git-pack-objects[1] before writing them out to a pack.1896 This cache is used to speed up the writing object phase by not1897 having to recompute the final delta result once the best match1898 for all objects is found. Repacking large repositories on machines1899 which are tight with memory might be badly impacted by this though,1900 especially if this cache pushes the system into swapping.1901 A value of 0 means no limit. The smallest size of 1 byte may be1902 used to virtually disable this cache. Defaults to 256 MiB.19031904pack.deltaCacheLimit::1905 The maximum size of a delta, that is cached in1906 linkgit:git-pack-objects[1]. This cache is used to speed up the1907 writing object phase by not having to recompute the final delta1908 result once the best match for all objects is found. Defaults to 1000.19091910pack.threads::1911 Specifies the number of threads to spawn when searching for best1912 delta matches. This requires that linkgit:git-pack-objects[1]1913 be compiled with pthreads otherwise this option is ignored with a1914 warning. This is meant to reduce packing time on multiprocessor1915 machines. The required amount of memory for the delta search window1916 is however multiplied by the number of threads.1917 Specifying 0 will cause Git to auto-detect the number of CPU's1918 and set the number of threads accordingly.19191920pack.indexVersion::1921 Specify the default pack index version. Valid values are 1 for1922 legacy pack index used by Git versions prior to 1.5.2, and 2 for1923 the new pack index with capabilities for packs larger than 4 GB1924 as well as proper protection against the repacking of corrupted1925 packs. Version 2 is the default. Note that version 2 is enforced1926 and this config option ignored whenever the corresponding pack is1927 larger than 2 GB.1928+1929If you have an old Git that does not understand the version 2 `*.idx` file,1930cloning or fetching over a non native protocol (e.g. "http" and "rsync")1931that will copy both `*.pack` file and corresponding `*.idx` file from the1932other side may give you a repository that cannot be accessed with your1933older version of Git. If the `*.pack` file is smaller than 2 GB, however,1934you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1935the `*.idx` file.19361937pack.packSizeLimit::1938 The maximum size of a pack. This setting only affects1939 packing to a file when repacking, i.e. the git:// protocol1940 is unaffected. It can be overridden by the `--max-pack-size`1941 option of linkgit:git-repack[1]. The minimum size allowed is1942 limited to 1 MiB. The default is unlimited.1943 Common unit suffixes of 'k', 'm', or 'g' are1944 supported.19451946pack.useBitmaps::1947 When true, git will use pack bitmaps (if available) when packing1948 to stdout (e.g., during the server side of a fetch). Defaults to1949 true. You should not generally need to turn this off unless1950 you are debugging pack bitmaps.19511952pack.writebitmaps::1953 This is a deprecated synonym for `repack.writeBitmaps`.19541955pack.writeBitmapHashCache::1956 When true, git will include a "hash cache" section in the bitmap1957 index (if one is written). This cache can be used to feed git's1958 delta heuristics, potentially leading to better deltas between1959 bitmapped and non-bitmapped objects (e.g., when serving a fetch1960 between an older, bitmapped pack and objects that have been1961 pushed since the last gc). The downside is that it consumes 41962 bytes per object of disk space, and that JGit's bitmap1963 implementation does not understand it, causing it to complain if1964 Git and JGit are used on the same repository. Defaults to false.19651966pager.<cmd>::1967 If the value is boolean, turns on or off pagination of the1968 output of a particular Git subcommand when writing to a tty.1969 Otherwise, turns on pagination for the subcommand using the1970 pager specified by the value of `pager.<cmd>`. If `--paginate`1971 or `--no-pager` is specified on the command line, it takes1972 precedence over this option. To disable pagination for all1973 commands, set `core.pager` or `GIT_PAGER` to `cat`.19741975pretty.<name>::1976 Alias for a --pretty= format string, as specified in1977 linkgit:git-log[1]. Any aliases defined here can be used just1978 as the built-in pretty formats could. For example,1979 running `git config pretty.changelog "format:* %H %s"`1980 would cause the invocation `git log --pretty=changelog`1981 to be equivalent to running `git log "--pretty=format:* %H %s"`.1982 Note that an alias with the same name as a built-in format1983 will be silently ignored.19841985pull.ff::1986 By default, Git does not create an extra merge commit when merging1987 a commit that is a descendant of the current commit. Instead, the1988 tip of the current branch is fast-forwarded. When set to `false`,1989 this variable tells Git to create an extra merge commit in such1990 a case (equivalent to giving the `--no-ff` option from the command1991 line). When set to `only`, only such fast-forward merges are1992 allowed (equivalent to giving the `--ff-only` option from the1993 command line).19941995pull.rebase::1996 When true, rebase branches on top of the fetched branch, instead1997 of merging the default branch from the default remote when "git1998 pull" is run. See "branch.<name>.rebase" for setting this on a1999 per-branch basis.2000+2001 When preserve, also pass `--preserve-merges` along to 'git rebase'2002 so that locally committed merge commits will not be flattened2003 by running 'git pull'.2004+2005*NOTE*: this is a possibly dangerous operation; do *not* use2006it unless you understand the implications (see linkgit:git-rebase[1]2007for details).20082009pull.octopus::2010 The default merge strategy to use when pulling multiple branches2011 at once.20122013pull.twohead::2014 The default merge strategy to use when pulling a single branch.20152016push.default::2017 Defines the action `git push` should take if no refspec is2018 explicitly given. Different values are well-suited for2019 specific workflows; for instance, in a purely central workflow2020 (i.e. the fetch source is equal to the push destination),2021 `upstream` is probably what you want. Possible values are:2022+2023--20242025* `nothing` - do not push anything (error out) unless a refspec is2026 explicitly given. This is primarily meant for people who want to2027 avoid mistakes by always being explicit.20282029* `current` - push the current branch to update a branch with the same2030 name on the receiving end. Works in both central and non-central2031 workflows.20322033* `upstream` - push the current branch back to the branch whose2034 changes are usually integrated into the current branch (which is2035 called `@{upstream}`). This mode only makes sense if you are2036 pushing to the same repository you would normally pull from2037 (i.e. central workflow).20382039* `simple` - in centralized workflow, work like `upstream` with an2040 added safety to refuse to push if the upstream branch's name is2041 different from the local one.2042+2043When pushing to a remote that is different from the remote you normally2044pull from, work as `current`. This is the safest option and is suited2045for beginners.2046+2047This mode has become the default in Git 2.0.20482049* `matching` - push all branches having the same name on both ends.2050 This makes the repository you are pushing to remember the set of2051 branches that will be pushed out (e.g. if you always push 'maint'2052 and 'master' there and no other branches, the repository you push2053 to will have these two branches, and your local 'maint' and2054 'master' will be pushed there).2055+2056To use this mode effectively, you have to make sure _all_ the2057branches you would push out are ready to be pushed out before2058running 'git push', as the whole point of this mode is to allow you2059to push all of the branches in one go. If you usually finish work2060on only one branch and push out the result, while other branches are2061unfinished, this mode is not for you. Also this mode is not2062suitable for pushing into a shared central repository, as other2063people may add new branches there, or update the tip of existing2064branches outside your control.2065+2066This used to be the default, but not since Git 2.0 (`simple` is the2067new default).20682069--20702071rebase.stat::2072 Whether to show a diffstat of what changed upstream since the last2073 rebase. False by default.20742075rebase.autosquash::2076 If set to true enable '--autosquash' option by default.20772078rebase.autostash::2079 When set to true, automatically create a temporary stash2080 before the operation begins, and apply it after the operation2081 ends. This means that you can run rebase on a dirty worktree.2082 However, use with care: the final stash application after a2083 successful rebase might result in non-trivial conflicts.2084 Defaults to false.20852086receive.autogc::2087 By default, git-receive-pack will run "git-gc --auto" after2088 receiving data from git-push and updating refs. You can stop2089 it by setting this variable to false.20902091receive.certnonceseed::2092 By setting this variable to a string, `git receive-pack`2093 will accept a `git push --signed` and verifies it by using2094 a "nonce" protected by HMAC using this string as a secret2095 key.20962097receive.certnonceslop::2098 When a `git push --signed` sent a push certificate with a2099 "nonce" that was issued by a receive-pack serving the same2100 repository within this many seconds, export the "nonce"2101 found in the certificate to `GIT_PUSH_CERT_NONCE` to the2102 hooks (instead of what the receive-pack asked the sending2103 side to include). This may allow writing checks in2104 `pre-receive` and `post-receive` a bit easier. Instead of2105 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable2106 that records by how many seconds the nonce is stale to2107 decide if they want to accept the certificate, they only2108 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.21092110receive.fsckObjects::2111 If it is set to true, git-receive-pack will check all received2112 objects. It will abort in the case of a malformed object or a2113 broken link. The result of an abort are only dangling objects.2114 Defaults to false. If not set, the value of `transfer.fsckObjects`2115 is used instead.21162117receive.unpackLimit::2118 If the number of objects received in a push is below this2119 limit then the objects will be unpacked into loose object2120 files. However if the number of received objects equals or2121 exceeds this limit then the received pack will be stored as2122 a pack, after adding any missing delta bases. Storing the2123 pack from a push can make the push operation complete faster,2124 especially on slow filesystems. If not set, the value of2125 `transfer.unpackLimit` is used instead.21262127receive.denyDeletes::2128 If set to true, git-receive-pack will deny a ref update that deletes2129 the ref. Use this to prevent such a ref deletion via a push.21302131receive.denyDeleteCurrent::2132 If set to true, git-receive-pack will deny a ref update that2133 deletes the currently checked out branch of a non-bare repository.21342135receive.denyCurrentBranch::2136 If set to true or "refuse", git-receive-pack will deny a ref update2137 to the currently checked out branch of a non-bare repository.2138 Such a push is potentially dangerous because it brings the HEAD2139 out of sync with the index and working tree. If set to "warn",2140 print a warning of such a push to stderr, but allow the push to2141 proceed. If set to false or "ignore", allow such pushes with no2142 message. Defaults to "refuse".21432144receive.denyNonFastForwards::2145 If set to true, git-receive-pack will deny a ref update which is2146 not a fast-forward. Use this to prevent such an update via a push,2147 even if that push is forced. This configuration variable is2148 set when initializing a shared repository.21492150receive.hiderefs::2151 String(s) `receive-pack` uses to decide which refs to omit2152 from its initial advertisement. Use more than one2153 definitions to specify multiple prefix strings. A ref that2154 are under the hierarchies listed on the value of this2155 variable is excluded, and is hidden when responding to `git2156 push`, and an attempt to update or delete a hidden ref by2157 `git push` is rejected.21582159receive.updateserverinfo::2160 If set to true, git-receive-pack will run git-update-server-info2161 after receiving data from git-push and updating refs.21622163receive.shallowupdate::2164 If set to true, .git/shallow can be updated when new refs2165 require new shallow roots. Otherwise those refs are rejected.21662167remote.pushdefault::2168 The remote to push to by default. Overrides2169 `branch.<name>.remote` for all branches, and is overridden by2170 `branch.<name>.pushremote` for specific branches.21712172remote.<name>.url::2173 The URL of a remote repository. See linkgit:git-fetch[1] or2174 linkgit:git-push[1].21752176remote.<name>.pushurl::2177 The push URL of a remote repository. See linkgit:git-push[1].21782179remote.<name>.proxy::2180 For remotes that require curl (http, https and ftp), the URL to2181 the proxy to use for that remote. Set to the empty string to2182 disable proxying for that remote.21832184remote.<name>.fetch::2185 The default set of "refspec" for linkgit:git-fetch[1]. See2186 linkgit:git-fetch[1].21872188remote.<name>.push::2189 The default set of "refspec" for linkgit:git-push[1]. See2190 linkgit:git-push[1].21912192remote.<name>.mirror::2193 If true, pushing to this remote will automatically behave2194 as if the `--mirror` option was given on the command line.21952196remote.<name>.skipDefaultUpdate::2197 If true, this remote will be skipped by default when updating2198 using linkgit:git-fetch[1] or the `update` subcommand of2199 linkgit:git-remote[1].22002201remote.<name>.skipFetchAll::2202 If true, this remote will be skipped by default when updating2203 using linkgit:git-fetch[1] or the `update` subcommand of2204 linkgit:git-remote[1].22052206remote.<name>.receivepack::2207 The default program to execute on the remote side when pushing. See2208 option \--receive-pack of linkgit:git-push[1].22092210remote.<name>.uploadpack::2211 The default program to execute on the remote side when fetching. See2212 option \--upload-pack of linkgit:git-fetch-pack[1].22132214remote.<name>.tagopt::2215 Setting this value to \--no-tags disables automatic tag following when2216 fetching from remote <name>. Setting it to \--tags will fetch every2217 tag from remote <name>, even if they are not reachable from remote2218 branch heads. Passing these flags directly to linkgit:git-fetch[1] can2219 override this setting. See options \--tags and \--no-tags of2220 linkgit:git-fetch[1].22212222remote.<name>.vcs::2223 Setting this to a value <vcs> will cause Git to interact with2224 the remote with the git-remote-<vcs> helper.22252226remote.<name>.prune::2227 When set to true, fetching from this remote by default will also2228 remove any remote-tracking references that no longer exist on the2229 remote (as if the `--prune` option was given on the command line).2230 Overrides `fetch.prune` settings, if any.22312232remotes.<group>::2233 The list of remotes which are fetched by "git remote update2234 <group>". See linkgit:git-remote[1].22352236repack.usedeltabaseoffset::2237 By default, linkgit:git-repack[1] creates packs that use2238 delta-base offset. If you need to share your repository with2239 Git older than version 1.4.4, either directly or via a dumb2240 protocol such as http, then you need to set this option to2241 "false" and repack. Access from old Git versions over the2242 native protocol are unaffected by this option.22432244repack.packKeptObjects::2245 If set to true, makes `git repack` act as if2246 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for2247 details. Defaults to `false` normally, but `true` if a bitmap2248 index is being written (either via `--write-bitmap-index` or2249 `repack.writeBitmaps`).22502251repack.writeBitmaps::2252 When true, git will write a bitmap index when packing all2253 objects to disk (e.g., when `git repack -a` is run). This2254 index can speed up the "counting objects" phase of subsequent2255 packs created for clones and fetches, at the cost of some disk2256 space and extra time spent on the initial repack. Defaults to2257 false.22582259rerere.autoupdate::2260 When set to true, `git-rerere` updates the index with the2261 resulting contents after it cleanly resolves conflicts using2262 previously recorded resolution. Defaults to false.22632264rerere.enabled::2265 Activate recording of resolved conflicts, so that identical2266 conflict hunks can be resolved automatically, should they be2267 encountered again. By default, linkgit:git-rerere[1] is2268 enabled if there is an `rr-cache` directory under the2269 `$GIT_DIR`, e.g. if "rerere" was previously used in the2270 repository.22712272sendemail.identity::2273 A configuration identity. When given, causes values in the2274 'sendemail.<identity>' subsection to take precedence over2275 values in the 'sendemail' section. The default identity is2276 the value of 'sendemail.identity'.22772278sendemail.smtpencryption::2279 See linkgit:git-send-email[1] for description. Note that this2280 setting is not subject to the 'identity' mechanism.22812282sendemail.smtpssl::2283 Deprecated alias for 'sendemail.smtpencryption = ssl'.22842285sendemail.smtpsslcertpath::2286 Path to ca-certificates (either a directory or a single file).2287 Set it to an empty string to disable certificate verification.22882289sendemail.<identity>.*::2290 Identity-specific versions of the 'sendemail.*' parameters2291 found below, taking precedence over those when the this2292 identity is selected, through command-line or2293 'sendemail.identity'.22942295sendemail.aliasesfile::2296sendemail.aliasfiletype::2297sendemail.annotate::2298sendemail.bcc::2299sendemail.cc::2300sendemail.cccmd::2301sendemail.chainreplyto::2302sendemail.confirm::2303sendemail.envelopesender::2304sendemail.from::2305sendemail.multiedit::2306sendemail.signedoffbycc::2307sendemail.smtppass::2308sendemail.suppresscc::2309sendemail.suppressfrom::2310sendemail.to::2311sendemail.smtpdomain::2312sendemail.smtpserver::2313sendemail.smtpserverport::2314sendemail.smtpserveroption::2315sendemail.smtpuser::2316sendemail.thread::2317sendemail.validate::2318 See linkgit:git-send-email[1] for description.23192320sendemail.signedoffcc::2321 Deprecated alias for 'sendemail.signedoffbycc'.23222323showbranch.default::2324 The default set of branches for linkgit:git-show-branch[1].2325 See linkgit:git-show-branch[1].23262327status.relativePaths::2328 By default, linkgit:git-status[1] shows paths relative to the2329 current directory. Setting this variable to `false` shows paths2330 relative to the repository root (this was the default for Git2331 prior to v1.5.4).23322333status.short::2334 Set to true to enable --short by default in linkgit:git-status[1].2335 The option --no-short takes precedence over this variable.23362337status.branch::2338 Set to true to enable --branch by default in linkgit:git-status[1].2339 The option --no-branch takes precedence over this variable.23402341status.displayCommentPrefix::2342 If set to true, linkgit:git-status[1] will insert a comment2343 prefix before each output line (starting with2344 `core.commentChar`, i.e. `#` by default). This was the2345 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.2346 Defaults to false.23472348status.showUntrackedFiles::2349 By default, linkgit:git-status[1] and linkgit:git-commit[1] show2350 files which are not currently tracked by Git. Directories which2351 contain only untracked files, are shown with the directory name2352 only. Showing untracked files means that Git needs to lstat() all2353 the files in the whole repository, which might be slow on some2354 systems. So, this variable controls how the commands displays2355 the untracked files. Possible values are:2356+2357--2358* `no` - Show no untracked files.2359* `normal` - Show untracked files and directories.2360* `all` - Show also individual files in untracked directories.2361--2362+2363If this variable is not specified, it defaults to 'normal'.2364This variable can be overridden with the -u|--untracked-files option2365of linkgit:git-status[1] and linkgit:git-commit[1].23662367status.submodulesummary::2368 Defaults to false.2369 If this is set to a non zero number or true (identical to -1 or an2370 unlimited number), the submodule summary will be enabled and a2371 summary of commits for modified submodules will be shown (see2372 --summary-limit option of linkgit:git-submodule[1]). Please note2373 that the summary output command will be suppressed for all2374 submodules when `diff.ignoreSubmodules` is set to 'all' or only2375 for those submodules where `submodule.<name>.ignore=all`. The only2376 exception to that rule is that status and commit will show staged2377 submodule changes. To2378 also view the summary for ignored submodules you can either use2379 the --ignore-submodules=dirty command-line option or the 'git2380 submodule summary' command, which shows a similar output but does2381 not honor these settings.23822383submodule.<name>.path::2384submodule.<name>.url::2385submodule.<name>.update::2386 The path within this project, URL, and the updating strategy2387 for a submodule. These variables are initially populated2388 by 'git submodule init'; edit them to override the2389 URL and other values found in the `.gitmodules` file. See2390 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.23912392submodule.<name>.branch::2393 The remote branch name for a submodule, used by `git submodule2394 update --remote`. Set this option to override the value found in2395 the `.gitmodules` file. See linkgit:git-submodule[1] and2396 linkgit:gitmodules[5] for details.23972398submodule.<name>.fetchRecurseSubmodules::2399 This option can be used to control recursive fetching of this2400 submodule. It can be overridden by using the --[no-]recurse-submodules2401 command-line option to "git fetch" and "git pull".2402 This setting will override that from in the linkgit:gitmodules[5]2403 file.24042405submodule.<name>.ignore::2406 Defines under what circumstances "git status" and the diff family show2407 a submodule as modified. When set to "all", it will never be considered2408 modified (but it will nonetheless show up in the output of status and2409 commit when it has been staged), "dirty" will ignore all changes2410 to the submodules work tree and2411 takes only differences between the HEAD of the submodule and the commit2412 recorded in the superproject into account. "untracked" will additionally2413 let submodules with modified tracked files in their work tree show up.2414 Using "none" (the default when this option is not set) also shows2415 submodules that have untracked files in their work tree as changed.2416 This setting overrides any setting made in .gitmodules for this submodule,2417 both settings can be overridden on the command line by using the2418 "--ignore-submodules" option. The 'git submodule' commands are not2419 affected by this setting.24202421tag.sort::2422 This variable controls the sort ordering of tags when displayed by2423 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the2424 value of this variable will be used as the default.24252426tar.umask::2427 This variable can be used to restrict the permission bits of2428 tar archive entries. The default is 0002, which turns off the2429 world write bit. The special value "user" indicates that the2430 archiving user's umask will be used instead. See umask(2) and2431 linkgit:git-archive[1].24322433transfer.fsckObjects::2434 When `fetch.fsckObjects` or `receive.fsckObjects` are2435 not set, the value of this variable is used instead.2436 Defaults to false.24372438transfer.hiderefs::2439 This variable can be used to set both `receive.hiderefs`2440 and `uploadpack.hiderefs` at the same time to the same2441 values. See entries for these other variables.24422443transfer.unpackLimit::2444 When `fetch.unpackLimit` or `receive.unpackLimit` are2445 not set, the value of this variable is used instead.2446 The default value is 100.24472448uploadarchive.allowUnreachable::2449 If true, allow clients to use `git archive --remote` to request2450 any tree, whether reachable from the ref tips or not. See the2451 discussion in the `SECURITY` section of2452 linkgit:git-upload-archive[1] for more details. Defaults to2453 `false`.24542455uploadpack.hiderefs::2456 String(s) `upload-pack` uses to decide which refs to omit2457 from its initial advertisement. Use more than one2458 definitions to specify multiple prefix strings. A ref that2459 are under the hierarchies listed on the value of this2460 variable is excluded, and is hidden from `git ls-remote`,2461 `git fetch`, etc. An attempt to fetch a hidden ref by `git2462 fetch` will fail. See also `uploadpack.allowtipsha1inwant`.24632464uploadpack.allowtipsha1inwant::2465 When `uploadpack.hiderefs` is in effect, allow `upload-pack`2466 to accept a fetch request that asks for an object at the tip2467 of a hidden ref (by default, such a request is rejected).2468 see also `uploadpack.hiderefs`.24692470uploadpack.keepalive::2471 When `upload-pack` has started `pack-objects`, there may be a2472 quiet period while `pack-objects` prepares the pack. Normally2473 it would output progress information, but if `--quiet` was used2474 for the fetch, `pack-objects` will output nothing at all until2475 the pack data begins. Some clients and networks may consider2476 the server to be hung and give up. Setting this option instructs2477 `upload-pack` to send an empty keepalive packet every2478 `uploadpack.keepalive` seconds. Setting this option to 02479 disables keepalive packets entirely. The default is 5 seconds.24802481url.<base>.insteadOf::2482 Any URL that starts with this value will be rewritten to2483 start, instead, with <base>. In cases where some site serves a2484 large number of repositories, and serves them with multiple2485 access methods, and some users need to use different access2486 methods, this feature allows people to specify any of the2487 equivalent URLs and have Git automatically rewrite the URL to2488 the best alternative for the particular user, even for a2489 never-before-seen repository on the site. When more than one2490 insteadOf strings match a given URL, the longest match is used.24912492url.<base>.pushInsteadOf::2493 Any URL that starts with this value will not be pushed to;2494 instead, it will be rewritten to start with <base>, and the2495 resulting URL will be pushed to. In cases where some site serves2496 a large number of repositories, and serves them with multiple2497 access methods, some of which do not allow push, this feature2498 allows people to specify a pull-only URL and have Git2499 automatically use an appropriate URL to push, even for a2500 never-before-seen repository on the site. When more than one2501 pushInsteadOf strings match a given URL, the longest match is2502 used. If a remote has an explicit pushurl, Git will ignore this2503 setting for that remote.25042505user.email::2506 Your email address to be recorded in any newly created commits.2507 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and2508 'EMAIL' environment variables. See linkgit:git-commit-tree[1].25092510user.name::2511 Your full name to be recorded in any newly created commits.2512 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'2513 environment variables. See linkgit:git-commit-tree[1].25142515user.signingkey::2516 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the2517 key you want it to automatically when creating a signed tag or2518 commit, you can override the default selection with this variable.2519 This option is passed unchanged to gpg's --local-user parameter,2520 so you may specify a key using any method that gpg supports.25212522web.browser::2523 Specify a web browser that may be used by some commands.2524 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]2525 may use it.