1CONFIGURATION FILE 2------------------ 3 4The Git configuration file contains a number of variables that affect 5the Git commands' behavior. The `.git/config` file in each repository 6is used to store the configuration for that repository, and 7`$HOME/.gitconfig` is used to store a per-user configuration as 8fallback values for the `.git/config` file. The file `/etc/gitconfig` 9can be used to store a system-wide default configuration. 10 11The configuration variables are used by both the Git plumbing 12and the porcelains. The variables are divided into sections, wherein 13the fully qualified variable name of the variable itself is the last 14dot-separated segment and the section name is everything before the last 15dot. The variable names are case-insensitive, allow only alphanumeric 16characters and `-`, and must start with an alphabetic character. Some 17variables may appear multiple times; we say then that the variable is 18multivalued. 19 20Syntax 21~~~~~~ 22 23The syntax is fairly flexible and permissive; whitespaces are mostly 24ignored. The '#' and ';' characters begin comments to the end of line, 25blank lines are ignored. 26 27The file consists of sections and variables. A section begins with 28the name of the section in square brackets and continues until the next 29section begins. Section names are case-insensitive. Only alphanumeric 30characters, `-` and `.` are allowed in section names. Each variable 31must belong to some section, which means that there must be a section 32header before the first setting of a variable. 33 34Sections can be further divided into subsections. To begin a subsection 35put its name in double quotes, separated by space from the section name, 36in the section header, like in the example below: 37 38-------- 39 [section "subsection"] 40 41-------- 42 43Subsection names are case sensitive and can contain any characters except 44newline (doublequote `"` and backslash can be included by escaping them 45as `\"` and `\\`, respectively). Section headers cannot span multiple 46lines. Variables may belong directly to a section or to a given subsection. 47You can have `[section]` if you have `[section "subsection"]`, but you 48don't need to. 49 50There is also a deprecated `[section.subsection]` syntax. With this 51syntax, the subsection name is converted to lower-case and is also 52compared case sensitively. These subsection names follow the same 53restrictions as section names. 54 55All the other lines (and the remainder of the line after the section 56header) are recognized as setting variables, in the form 57'name = value' (or just 'name', which is a short-hand to say that 58the variable is the boolean "true"). 59The variable names are case-insensitive, allow only alphanumeric characters 60and `-`, and must start with an alphabetic character. 61 62A line that defines a value can be continued to the next line by 63ending it with a `\`; the backquote and the end-of-line are 64stripped. Leading whitespaces after 'name =', the remainder of the 65line after the first comment character '#' or ';', and trailing 66whitespaces of the line are discarded unless they are enclosed in 67double quotes. Internal whitespaces within the value are retained 68verbatim. 69 70Inside double quotes, double quote `"` and backslash `\` characters 71must be escaped: use `\"` for `"` and `\\` for `\`. 72 73The following escape sequences (beside `\"` and `\\`) are recognized: 74`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 75and `\b` for backspace (BS). Other char escape sequences (including octal 76escape sequences) are invalid. 77 78 79Includes 80~~~~~~~~ 81 82You can include one config file from another by setting the special 83`include.path` variable to the name of the file to be included. The 84included file is expanded immediately, as if its contents had been 85found at the location of the include directive. If the value of the 86`include.path` variable is a relative path, the path is considered to be 87relative to the configuration file in which the include directive was 88found. The value of `include.path` is subject to tilde expansion: `~/` 89is expanded to the value of `$HOME`, and `~user/` to the specified 90user's home directory. See below for examples. 91 92Example 93~~~~~~~ 94 95 # Core variables 96 [core] 97 ; Don't trust file modes 98 filemode = false 99 100 # Our diff algorithm 101 [diff] 102 external = /usr/local/bin/diff-wrapper 103 renames = true 104 105 [branch "devel"] 106 remote = origin 107 merge = refs/heads/devel 108 109 # Proxy settings 110 [core] 111 gitProxy="ssh" for "kernel.org" 112 gitProxy=default-proxy ; for the rest 113 114 [include] 115 path = /path/to/foo.inc ; include by absolute path 116 path = foo ; expand "foo" relative to the current file 117 path = ~/foo ; expand "foo" in your $HOME directory 118 119 120Values 121~~~~~~ 122 123Values of many variables are treated as a simple string, but there 124are variables that take values of specific types and there are rules 125as to how to spell them. 126 127boolean:: 128 129 When a variable is said to take a boolean value, many 130 synonyms are accepted for 'true' and 'false'; these are all 131 case-insensitive. 132 133 true;; Boolean true can be spelled as `yes`, `on`, `true`, 134 or `1`. Also, a variable defined without `= <value>` 135 is taken as true. 136 137 false;; Boolean false can be spelled as `no`, `off`, 138 `false`, or `0`. 139+ 140When converting value to the canonical form using '--bool' type 141specifier; 'git config' will ensure that the output is "true" or 142"false" (spelled in lowercase). 143 144integer:: 145 The value for many variables that specify various sizes can 146 be suffixed with `k`, `M`,... to mean "scale the number by 147 1024", "by 1024x1024", etc. 148 149color:: 150 The value for a variables that takes a color is a list of 151 colors (at most two) and attributes (at most one), separated 152 by spaces. The colors accepted are `normal`, `black`, 153 `red`, `green`, `yellow`, `blue`, `magenta`, `cyan` and 154 `white`; the attributes are `bold`, `dim`, `ul`, `blink` and 155 `reverse`. The first color given is the foreground; the 156 second is the background. The position of the attribute, if 157 any, doesn't matter. Attributes may be turned off 158 specifically by prefixing them with `no` (e.g., `noreverse`, 159 `noul`, etc). 160+ 161Colors (foreground and background) may also be given as numbers between 1620 and 255; these use ANSI 256-color mode (but note that not all 163terminals may support this). If your terminal supports it, you may also 164specify 24-bit RGB values as hex, like `#ff0ab3`. 165+ 166The attributes are meant to be reset at the beginning of each item 167in the colored output, so setting color.decorate.branch to `black` 168will paint that branch name in a plain `black`, even if the previous 169thing on the same output line (e.g. opening parenthesis before the 170list of branch names in `log --decorate` output) is set to be 171painted with `bold` or some other attribute. 172 173 174Variables 175~~~~~~~~~ 176 177Note that this list is non-comprehensive and not necessarily complete. 178For command-specific variables, you will find a more detailed description 179in the appropriate manual page. 180 181Other git-related tools may and do use their own variables. When 182inventing new variables for use in your own tool, make sure their 183names do not conflict with those that are used by Git itself and 184other popular tools, and describe them in your documentation. 185 186 187advice.*:: 188 These variables control various optional help messages designed to 189 aid new users. All 'advice.*' variables default to 'true', and you 190 can tell Git that you do not need help by setting these to 'false': 191+ 192-- 193 pushUpdateRejected:: 194 Set this variable to 'false' if you want to disable 195 'pushNonFFCurrent', 196 'pushNonFFMatching', 'pushAlreadyExists', 197 'pushFetchFirst', and 'pushNeedsForce' 198 simultaneously. 199 pushNonFFCurrent:: 200 Advice shown when linkgit:git-push[1] fails due to a 201 non-fast-forward update to the current branch. 202 pushNonFFMatching:: 203 Advice shown when you ran linkgit:git-push[1] and pushed 204 'matching refs' explicitly (i.e. you used ':', or 205 specified a refspec that isn't your current branch) and 206 it resulted in a non-fast-forward error. 207 pushAlreadyExists:: 208 Shown when linkgit:git-push[1] rejects an update that 209 does not qualify for fast-forwarding (e.g., a tag.) 210 pushFetchFirst:: 211 Shown when linkgit:git-push[1] rejects an update that 212 tries to overwrite a remote ref that points at an 213 object we do not have. 214 pushNeedsForce:: 215 Shown when linkgit:git-push[1] rejects an update that 216 tries to overwrite a remote ref that points at an 217 object that is not a commit-ish, or make the remote 218 ref point at an object that is not a commit-ish. 219 statusHints:: 220 Show directions on how to proceed from the current 221 state in the output of linkgit:git-status[1], in 222 the template shown when writing commit messages in 223 linkgit:git-commit[1], and in the help message shown 224 by linkgit:git-checkout[1] when switching branch. 225 statusUoption:: 226 Advise to consider using the `-u` option to linkgit:git-status[1] 227 when the command takes more than 2 seconds to enumerate untracked 228 files. 229 commitBeforeMerge:: 230 Advice shown when linkgit:git-merge[1] refuses to 231 merge to avoid overwriting local changes. 232 resolveConflict:: 233 Advice shown by various commands when conflicts 234 prevent the operation from being performed. 235 implicitIdentity:: 236 Advice on how to set your identity configuration when 237 your information is guessed from the system username and 238 domain name. 239 detachedHead:: 240 Advice shown when you used linkgit:git-checkout[1] to 241 move to the detach HEAD state, to instruct how to create 242 a local branch after the fact. 243 amWorkDir:: 244 Advice that shows the location of the patch file when 245 linkgit:git-am[1] fails to apply it. 246 rmHints:: 247 In case of failure in the output of linkgit:git-rm[1], 248 show directions on how to proceed from the current state. 249-- 250 251core.fileMode:: 252 Tells Git if the executable bit of files in the working tree 253 is to be honored. 254+ 255Some filesystems lose the executable bit when a file that is 256marked as executable is checked out, or checks out an 257non-executable file with executable bit on. 258linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 259to see if it handles the executable bit correctly 260and this variable is automatically set as necessary. 261+ 262A repository, however, may be on a filesystem that handles 263the filemode correctly, and this variable is set to 'true' 264when created, but later may be made accessible from another 265environment that loses the filemode (e.g. exporting ext4 via 266CIFS mount, visiting a Cygwin created repository with 267Git for Windows or Eclipse). 268In such a case it may be necessary to set this variable to 'false'. 269See linkgit:git-update-index[1]. 270+ 271The default is true (when core.filemode is not specified in the config file). 272 273core.ignorecase:: 274 If true, this option enables various workarounds to enable 275 Git to work better on filesystems that are not case sensitive, 276 like FAT. For example, if a directory listing finds 277 "makefile" when Git expects "Makefile", Git will assume 278 it is really the same file, and continue to remember it as 279 "Makefile". 280+ 281The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 282will probe and set core.ignorecase true if appropriate when the repository 283is created. 284 285core.precomposeunicode:: 286 This option is only used by Mac OS implementation of Git. 287 When core.precomposeunicode=true, Git reverts the unicode decomposition 288 of filenames done by Mac OS. This is useful when sharing a repository 289 between Mac OS and Linux or Windows. 290 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 291 When false, file names are handled fully transparent by Git, 292 which is backward compatible with older versions of Git. 293 294core.protectHFS:: 295 If set to true, do not allow checkout of paths that would 296 be considered equivalent to `.git` on an HFS+ filesystem. 297 Defaults to `true` on Mac OS, and `false` elsewhere. 298 299core.protectNTFS:: 300 If set to true, do not allow checkout of paths that would 301 cause problems with the NTFS filesystem, e.g. conflict with 302 8.3 "short" names. 303 Defaults to `true` on Windows, and `false` elsewhere. 304 305core.trustctime:: 306 If false, the ctime differences between the index and the 307 working tree are ignored; useful when the inode change time 308 is regularly modified by something outside Git (file system 309 crawlers and some backup systems). 310 See linkgit:git-update-index[1]. True by default. 311 312core.checkstat:: 313 Determines which stat fields to match between the index 314 and work tree. The user can set this to 'default' or 315 'minimal'. Default (or explicitly 'default'), is to check 316 all fields, including the sub-second part of mtime and ctime. 317 318core.quotepath:: 319 The commands that output paths (e.g. 'ls-files', 320 'diff'), when not given the `-z` option, will quote 321 "unusual" characters in the pathname by enclosing the 322 pathname in a double-quote pair and with backslashes the 323 same way strings in C source code are quoted. If this 324 variable is set to false, the bytes higher than 0x80 are 325 not quoted but output as verbatim. Note that double 326 quote, backslash and control characters are always 327 quoted without `-z` regardless of the setting of this 328 variable. 329 330core.eol:: 331 Sets the line ending type to use in the working directory for 332 files that have the `text` property set. Alternatives are 333 'lf', 'crlf' and 'native', which uses the platform's native 334 line ending. The default value is `native`. See 335 linkgit:gitattributes[5] for more information on end-of-line 336 conversion. 337 338core.safecrlf:: 339 If true, makes Git check if converting `CRLF` is reversible when 340 end-of-line conversion is active. Git will verify if a command 341 modifies a file in the work tree either directly or indirectly. 342 For example, committing a file followed by checking out the 343 same file should yield the original file in the work tree. If 344 this is not the case for the current setting of 345 `core.autocrlf`, Git will reject the file. The variable can 346 be set to "warn", in which case Git will only warn about an 347 irreversible conversion but continue the operation. 348+ 349CRLF conversion bears a slight chance of corrupting data. 350When it is enabled, Git will convert CRLF to LF during commit and LF to 351CRLF during checkout. A file that contains a mixture of LF and 352CRLF before the commit cannot be recreated by Git. For text 353files this is the right thing to do: it corrects line endings 354such that we have only LF line endings in the repository. 355But for binary files that are accidentally classified as text the 356conversion can corrupt data. 357+ 358If you recognize such corruption early you can easily fix it by 359setting the conversion type explicitly in .gitattributes. Right 360after committing you still have the original file in your work 361tree and this file is not yet corrupted. You can explicitly tell 362Git that this file is binary and Git will handle the file 363appropriately. 364+ 365Unfortunately, the desired effect of cleaning up text files with 366mixed line endings and the undesired effect of corrupting binary 367files cannot be distinguished. In both cases CRLFs are removed 368in an irreversible way. For text files this is the right thing 369to do because CRLFs are line endings, while for binary files 370converting CRLFs corrupts data. 371+ 372Note, this safety check does not mean that a checkout will generate a 373file identical to the original file for a different setting of 374`core.eol` and `core.autocrlf`, but only for the current one. For 375example, a text file with `LF` would be accepted with `core.eol=lf` 376and could later be checked out with `core.eol=crlf`, in which case the 377resulting file would contain `CRLF`, although the original file 378contained `LF`. However, in both work trees the line endings would be 379consistent, that is either all `LF` or all `CRLF`, but never mixed. A 380file with mixed line endings would be reported by the `core.safecrlf` 381mechanism. 382 383core.autocrlf:: 384 Setting this variable to "true" is almost the same as setting 385 the `text` attribute to "auto" on all files except that text 386 files are not guaranteed to be normalized: files that contain 387 `CRLF` in the repository will not be touched. Use this 388 setting if you want to have `CRLF` line endings in your 389 working directory even though the repository does not have 390 normalized line endings. This variable can be set to 'input', 391 in which case no output conversion is performed. 392 393core.symlinks:: 394 If false, symbolic links are checked out as small plain files that 395 contain the link text. linkgit:git-update-index[1] and 396 linkgit:git-add[1] will not change the recorded type to regular 397 file. Useful on filesystems like FAT that do not support 398 symbolic links. 399+ 400The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 401will probe and set core.symlinks false if appropriate when the repository 402is created. 403 404core.gitProxy:: 405 A "proxy command" to execute (as 'command host port') instead 406 of establishing direct connection to the remote server when 407 using the Git protocol for fetching. If the variable value is 408 in the "COMMAND for DOMAIN" format, the command is applied only 409 on hostnames ending with the specified domain string. This variable 410 may be set multiple times and is matched in the given order; 411 the first match wins. 412+ 413Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 414(which always applies universally, without the special "for" 415handling). 416+ 417The special string `none` can be used as the proxy command to 418specify that no proxy be used for a given domain pattern. 419This is useful for excluding servers inside a firewall from 420proxy use, while defaulting to a common proxy for external domains. 421 422core.ignoreStat:: 423 If true, Git will avoid using lstat() calls to detect if files have 424 changed by setting the "assume-unchanged" bit for those tracked files 425 which it has updated identically in both the index and working tree. 426+ 427When files are modified outside of Git, the user will need to stage 428the modified files explicitly (e.g. see 'Examples' section in 429linkgit:git-update-index[1]). 430Git will not normally detect changes to those files. 431+ 432This is useful on systems where lstat() calls are very slow, such as 433CIFS/Microsoft Windows. 434+ 435False by default. 436 437core.preferSymlinkRefs:: 438 Instead of the default "symref" format for HEAD 439 and other symbolic reference files, use symbolic links. 440 This is sometimes needed to work with old scripts that 441 expect HEAD to be a symbolic link. 442 443core.bare:: 444 If true this repository is assumed to be 'bare' and has no 445 working directory associated with it. If this is the case a 446 number of commands that require a working directory will be 447 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 448+ 449This setting is automatically guessed by linkgit:git-clone[1] or 450linkgit:git-init[1] when the repository was created. By default a 451repository that ends in "/.git" is assumed to be not bare (bare = 452false), while all other repositories are assumed to be bare (bare 453= true). 454 455core.worktree:: 456 Set the path to the root of the working tree. 457 This can be overridden by the GIT_WORK_TREE environment 458 variable and the '--work-tree' command-line option. 459 The value can be an absolute path or relative to the path to 460 the .git directory, which is either specified by --git-dir 461 or GIT_DIR, or automatically discovered. 462 If --git-dir or GIT_DIR is specified but none of 463 --work-tree, GIT_WORK_TREE and core.worktree is specified, 464 the current working directory is regarded as the top level 465 of your working tree. 466+ 467Note that this variable is honored even when set in a configuration 468file in a ".git" subdirectory of a directory and its value differs 469from the latter directory (e.g. "/path/to/.git/config" has 470core.worktree set to "/different/path"), which is most likely a 471misconfiguration. Running Git commands in the "/path/to" directory will 472still use "/different/path" as the root of the work tree and can cause 473confusion unless you know what you are doing (e.g. you are creating a 474read-only snapshot of the same index to a location different from the 475repository's usual working tree). 476 477core.logAllRefUpdates:: 478 Enable the reflog. Updates to a ref <ref> is logged to the file 479 "$GIT_DIR/logs/<ref>", by appending the new and old 480 SHA-1, the date/time and the reason of the update, but 481 only when the file exists. If this configuration 482 variable is set to true, missing "$GIT_DIR/logs/<ref>" 483 file is automatically created for branch heads (i.e. under 484 refs/heads/), remote refs (i.e. under refs/remotes/), 485 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 486+ 487This information can be used to determine what commit 488was the tip of a branch "2 days ago". 489+ 490This value is true by default in a repository that has 491a working directory associated with it, and false by 492default in a bare repository. 493 494core.repositoryFormatVersion:: 495 Internal variable identifying the repository format and layout 496 version. 497 498core.sharedRepository:: 499 When 'group' (or 'true'), the repository is made shareable between 500 several users in a group (making sure all the files and objects are 501 group-writable). When 'all' (or 'world' or 'everybody'), the 502 repository will be readable by all users, additionally to being 503 group-shareable. When 'umask' (or 'false'), Git will use permissions 504 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 505 files in the repository will have this mode value. '0xxx' will override 506 user's umask value (whereas the other options will only override 507 requested parts of the user's umask value). Examples: '0660' will make 508 the repo read/write-able for the owner and group, but inaccessible to 509 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 510 repository that is group-readable but not group-writable. 511 See linkgit:git-init[1]. False by default. 512 513core.warnAmbiguousRefs:: 514 If true, Git will warn you if the ref name you passed it is ambiguous 515 and might match multiple refs in the repository. True by default. 516 517core.compression:: 518 An integer -1..9, indicating a default compression level. 519 -1 is the zlib default. 0 means no compression, 520 and 1..9 are various speed/size tradeoffs, 9 being slowest. 521 If set, this provides a default to other compression variables, 522 such as 'core.loosecompression' and 'pack.compression'. 523 524core.loosecompression:: 525 An integer -1..9, indicating the compression level for objects that 526 are not in a pack file. -1 is the zlib default. 0 means no 527 compression, and 1..9 are various speed/size tradeoffs, 9 being 528 slowest. If not set, defaults to core.compression. If that is 529 not set, defaults to 1 (best speed). 530 531core.packedGitWindowSize:: 532 Number of bytes of a pack file to map into memory in a 533 single mapping operation. Larger window sizes may allow 534 your system to process a smaller number of large pack files 535 more quickly. Smaller window sizes will negatively affect 536 performance due to increased calls to the operating system's 537 memory manager, but may improve performance when accessing 538 a large number of large pack files. 539+ 540Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 541MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 542be reasonable for all users/operating systems. You probably do 543not need to adjust this value. 544+ 545Common unit suffixes of 'k', 'm', or 'g' are supported. 546 547core.packedGitLimit:: 548 Maximum number of bytes to map simultaneously into memory 549 from pack files. If Git needs to access more than this many 550 bytes at once to complete an operation it will unmap existing 551 regions to reclaim virtual address space within the process. 552+ 553Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 554This should be reasonable for all users/operating systems, except on 555the largest projects. You probably do not need to adjust this value. 556+ 557Common unit suffixes of 'k', 'm', or 'g' are supported. 558 559core.deltaBaseCacheLimit:: 560 Maximum number of bytes to reserve for caching base objects 561 that may be referenced by multiple deltified objects. By storing the 562 entire decompressed base objects in a cache Git is able 563 to avoid unpacking and decompressing frequently used base 564 objects multiple times. 565+ 566Default is 96 MiB on all platforms. This should be reasonable 567for all users/operating systems, except on the largest projects. 568You probably do not need to adjust this value. 569+ 570Common unit suffixes of 'k', 'm', or 'g' are supported. 571 572core.bigFileThreshold:: 573 Files larger than this size are stored deflated, without 574 attempting delta compression. Storing large files without 575 delta compression avoids excessive memory usage, at the 576 slight expense of increased disk usage. Additionally files 577 larger than this size are always treated as binary. 578+ 579Default is 512 MiB on all platforms. This should be reasonable 580for most projects as source code and other text files can still 581be delta compressed, but larger binary media files won't be. 582+ 583Common unit suffixes of 'k', 'm', or 'g' are supported. 584 585core.excludesfile:: 586 In addition to '.gitignore' (per-directory) and 587 '.git/info/exclude', Git looks into this file for patterns 588 of files which are not meant to be tracked. "`~/`" is expanded 589 to the value of `$HOME` and "`~user/`" to the specified user's 590 home directory. Its default value is $XDG_CONFIG_HOME/git/ignore. 591 If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore 592 is used instead. See linkgit:gitignore[5]. 593 594core.askpass:: 595 Some commands (e.g. svn and http interfaces) that interactively 596 ask for a password can be told to use an external program given 597 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 598 environment variable. If not set, fall back to the value of the 599 'SSH_ASKPASS' environment variable or, failing that, a simple password 600 prompt. The external program shall be given a suitable prompt as 601 command-line argument and write the password on its STDOUT. 602 603core.attributesfile:: 604 In addition to '.gitattributes' (per-directory) and 605 '.git/info/attributes', Git looks into this file for attributes 606 (see linkgit:gitattributes[5]). Path expansions are made the same 607 way as for `core.excludesfile`. Its default value is 608 $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not 609 set or empty, $HOME/.config/git/attributes is used instead. 610 611core.editor:: 612 Commands such as `commit` and `tag` that lets you edit 613 messages by launching an editor uses the value of this 614 variable when it is set, and the environment variable 615 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 616 617core.commentchar:: 618 Commands such as `commit` and `tag` that lets you edit 619 messages consider a line that begins with this character 620 commented, and removes them after the editor returns 621 (default '#'). 622+ 623If set to "auto", `git-commit` would select a character that is not 624the beginning character of any line in existing commit messages. 625 626sequence.editor:: 627 Text editor used by `git rebase -i` for editing the rebase instruction file. 628 The value is meant to be interpreted by the shell when it is used. 629 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 630 When not configured the default commit message editor is used instead. 631 632core.pager:: 633 Text viewer for use by Git commands (e.g., 'less'). The value 634 is meant to be interpreted by the shell. The order of preference 635 is the `$GIT_PAGER` environment variable, then `core.pager` 636 configuration, then `$PAGER`, and then the default chosen at 637 compile time (usually 'less'). 638+ 639When the `LESS` environment variable is unset, Git sets it to `FRX` 640(if `LESS` environment variable is set, Git does not change it at 641all). If you want to selectively override Git's default setting 642for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 643be passed to the shell by Git, which will translate the final 644command to `LESS=FRX less -S`. The environment does not set the 645`S` option but the command line does, instructing less to truncate 646long lines. Similarly, setting `core.pager` to `less -+F` will 647deactivate the `F` option specified by the environment from the 648command-line, deactivating the "quit if one screen" behavior of 649`less`. One can specifically activate some flags for particular 650commands: for example, setting `pager.blame` to `less -S` enables 651line truncation only for `git blame`. 652+ 653Likewise, when the `LV` environment variable is unset, Git sets it 654to `-c`. You can override this setting by exporting `LV` with 655another value or setting `core.pager` to `lv +c`. 656 657core.whitespace:: 658 A comma separated list of common whitespace problems to 659 notice. 'git diff' will use `color.diff.whitespace` to 660 highlight them, and 'git apply --whitespace=error' will 661 consider them as errors. You can prefix `-` to disable 662 any of them (e.g. `-trailing-space`): 663+ 664* `blank-at-eol` treats trailing whitespaces at the end of the line 665 as an error (enabled by default). 666* `space-before-tab` treats a space character that appears immediately 667 before a tab character in the initial indent part of the line as an 668 error (enabled by default). 669* `indent-with-non-tab` treats a line that is indented with space 670 characters instead of the equivalent tabs as an error (not enabled by 671 default). 672* `tab-in-indent` treats a tab character in the initial indent part of 673 the line as an error (not enabled by default). 674* `blank-at-eof` treats blank lines added at the end of file as an error 675 (enabled by default). 676* `trailing-space` is a short-hand to cover both `blank-at-eol` and 677 `blank-at-eof`. 678* `cr-at-eol` treats a carriage-return at the end of line as 679 part of the line terminator, i.e. with it, `trailing-space` 680 does not trigger if the character before such a carriage-return 681 is not a whitespace (not enabled by default). 682* `tabwidth=<n>` tells how many character positions a tab occupies; this 683 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 684 errors. The default tab width is 8. Allowed values are 1 to 63. 685 686core.fsyncobjectfiles:: 687 This boolean will enable 'fsync()' when writing object files. 688+ 689This is a total waste of time and effort on a filesystem that orders 690data writes properly, but can be useful for filesystems that do not use 691journalling (traditional UNIX filesystems) or that only journal metadata 692and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 693 694core.preloadindex:: 695 Enable parallel index preload for operations like 'git diff' 696+ 697This can speed up operations like 'git diff' and 'git status' especially 698on filesystems like NFS that have weak caching semantics and thus 699relatively high IO latencies. When enabled, Git will do the 700index comparison to the filesystem data in parallel, allowing 701overlapping IO's. Defaults to true. 702 703core.createObject:: 704 You can set this to 'link', in which case a hardlink followed by 705 a delete of the source are used to make sure that object creation 706 will not overwrite existing objects. 707+ 708On some file system/operating system combinations, this is unreliable. 709Set this config setting to 'rename' there; However, This will remove the 710check that makes sure that existing object files will not get overwritten. 711 712core.notesRef:: 713 When showing commit messages, also show notes which are stored in 714 the given ref. The ref must be fully qualified. If the given 715 ref does not exist, it is not an error but means that no 716 notes should be printed. 717+ 718This setting defaults to "refs/notes/commits", and it can be overridden by 719the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 720 721core.sparseCheckout:: 722 Enable "sparse checkout" feature. See section "Sparse checkout" in 723 linkgit:git-read-tree[1] for more information. 724 725core.abbrev:: 726 Set the length object names are abbreviated to. If unspecified, 727 many commands abbreviate to 7 hexdigits, which may not be enough 728 for abbreviated object names to stay unique for sufficiently long 729 time. 730 731add.ignoreErrors:: 732add.ignore-errors (deprecated):: 733 Tells 'git add' to continue adding files when some files cannot be 734 added due to indexing errors. Equivalent to the '--ignore-errors' 735 option of linkgit:git-add[1]. `add.ignore-errors` is deprecated, 736 as it does not follow the usual naming convention for configuration 737 variables. 738 739alias.*:: 740 Command aliases for the linkgit:git[1] command wrapper - e.g. 741 after defining "alias.last = cat-file commit HEAD", the invocation 742 "git last" is equivalent to "git cat-file commit HEAD". To avoid 743 confusion and troubles with script usage, aliases that 744 hide existing Git commands are ignored. Arguments are split by 745 spaces, the usual shell quoting and escaping is supported. 746 A quote pair or a backslash can be used to quote them. 747+ 748If the alias expansion is prefixed with an exclamation point, 749it will be treated as a shell command. For example, defining 750"alias.new = !gitk --all --not ORIG_HEAD", the invocation 751"git new" is equivalent to running the shell command 752"gitk --all --not ORIG_HEAD". Note that shell commands will be 753executed from the top-level directory of a repository, which may 754not necessarily be the current directory. 755'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 756from the original current directory. See linkgit:git-rev-parse[1]. 757 758am.keepcr:: 759 If true, git-am will call git-mailsplit for patches in mbox format 760 with parameter '--keep-cr'. In this case git-mailsplit will 761 not remove `\r` from lines ending with `\r\n`. Can be overridden 762 by giving '--no-keep-cr' from the command line. 763 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 764 765apply.ignorewhitespace:: 766 When set to 'change', tells 'git apply' to ignore changes in 767 whitespace, in the same way as the '--ignore-space-change' 768 option. 769 When set to one of: no, none, never, false tells 'git apply' to 770 respect all whitespace differences. 771 See linkgit:git-apply[1]. 772 773apply.whitespace:: 774 Tells 'git apply' how to handle whitespaces, in the same way 775 as the '--whitespace' option. See linkgit:git-apply[1]. 776 777branch.autosetupmerge:: 778 Tells 'git branch' and 'git checkout' to set up new branches 779 so that linkgit:git-pull[1] will appropriately merge from the 780 starting point branch. Note that even if this option is not set, 781 this behavior can be chosen per-branch using the `--track` 782 and `--no-track` options. The valid settings are: `false` -- no 783 automatic setup is done; `true` -- automatic setup is done when the 784 starting point is a remote-tracking branch; `always` -- 785 automatic setup is done when the starting point is either a 786 local branch or remote-tracking 787 branch. This option defaults to true. 788 789branch.autosetuprebase:: 790 When a new branch is created with 'git branch' or 'git checkout' 791 that tracks another branch, this variable tells Git to set 792 up pull to rebase instead of merge (see "branch.<name>.rebase"). 793 When `never`, rebase is never automatically set to true. 794 When `local`, rebase is set to true for tracked branches of 795 other local branches. 796 When `remote`, rebase is set to true for tracked branches of 797 remote-tracking branches. 798 When `always`, rebase will be set to true for all tracking 799 branches. 800 See "branch.autosetupmerge" for details on how to set up a 801 branch to track another branch. 802 This option defaults to never. 803 804branch.<name>.remote:: 805 When on branch <name>, it tells 'git fetch' and 'git push' 806 which remote to fetch from/push to. The remote to push to 807 may be overridden with `remote.pushdefault` (for all branches). 808 The remote to push to, for the current branch, may be further 809 overridden by `branch.<name>.pushremote`. If no remote is 810 configured, or if you are not on any branch, it defaults to 811 `origin` for fetching and `remote.pushdefault` for pushing. 812 Additionally, `.` (a period) is the current local repository 813 (a dot-repository), see `branch.<name>.merge`'s final note below. 814 815branch.<name>.pushremote:: 816 When on branch <name>, it overrides `branch.<name>.remote` for 817 pushing. It also overrides `remote.pushdefault` for pushing 818 from branch <name>. When you pull from one place (e.g. your 819 upstream) and push to another place (e.g. your own publishing 820 repository), you would want to set `remote.pushdefault` to 821 specify the remote to push to for all branches, and use this 822 option to override it for a specific branch. 823 824branch.<name>.merge:: 825 Defines, together with branch.<name>.remote, the upstream branch 826 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 827 branch to merge and can also affect 'git push' (see push.default). 828 When in branch <name>, it tells 'git fetch' the default 829 refspec to be marked for merging in FETCH_HEAD. The value is 830 handled like the remote part of a refspec, and must match a 831 ref which is fetched from the remote given by 832 "branch.<name>.remote". 833 The merge information is used by 'git pull' (which at first calls 834 'git fetch') to lookup the default branch for merging. Without 835 this option, 'git pull' defaults to merge the first refspec fetched. 836 Specify multiple values to get an octopus merge. 837 If you wish to setup 'git pull' so that it merges into <name> from 838 another branch in the local repository, you can point 839 branch.<name>.merge to the desired branch, and use the relative path 840 setting `.` (a period) for branch.<name>.remote. 841 842branch.<name>.mergeoptions:: 843 Sets default options for merging into branch <name>. The syntax and 844 supported options are the same as those of linkgit:git-merge[1], but 845 option values containing whitespace characters are currently not 846 supported. 847 848branch.<name>.rebase:: 849 When true, rebase the branch <name> on top of the fetched branch, 850 instead of merging the default branch from the default remote when 851 "git pull" is run. See "pull.rebase" for doing this in a non 852 branch-specific manner. 853+ 854 When preserve, also pass `--preserve-merges` along to 'git rebase' 855 so that locally committed merge commits will not be flattened 856 by running 'git pull'. 857+ 858*NOTE*: this is a possibly dangerous operation; do *not* use 859it unless you understand the implications (see linkgit:git-rebase[1] 860for details). 861 862branch.<name>.description:: 863 Branch description, can be edited with 864 `git branch --edit-description`. Branch description is 865 automatically added in the format-patch cover letter or 866 request-pull summary. 867 868browser.<tool>.cmd:: 869 Specify the command to invoke the specified browser. The 870 specified command is evaluated in shell with the URLs passed 871 as arguments. (See linkgit:git-web{litdd}browse[1].) 872 873browser.<tool>.path:: 874 Override the path for the given tool that may be used to 875 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 876 working repository in gitweb (see linkgit:git-instaweb[1]). 877 878clean.requireForce:: 879 A boolean to make git-clean do nothing unless given -f, 880 -i or -n. Defaults to true. 881 882color.branch:: 883 A boolean to enable/disable color in the output of 884 linkgit:git-branch[1]. May be set to `always`, 885 `false` (or `never`) or `auto` (or `true`), in which case colors are used 886 only when the output is to a terminal. Defaults to false. 887 888color.branch.<slot>:: 889 Use customized color for branch coloration. `<slot>` is one of 890 `current` (the current branch), `local` (a local branch), 891 `remote` (a remote-tracking branch in refs/remotes/), 892 `upstream` (upstream tracking branch), `plain` (other 893 refs). 894 895color.diff:: 896 Whether to use ANSI escape sequences to add color to patches. 897 If this is set to `always`, linkgit:git-diff[1], 898 linkgit:git-log[1], and linkgit:git-show[1] will use color 899 for all patches. If it is set to `true` or `auto`, those 900 commands will only use color when output is to the terminal. 901 Defaults to false. 902+ 903This does not affect linkgit:git-format-patch[1] or the 904'git-diff-{asterisk}' plumbing commands. Can be overridden on the 905command line with the `--color[=<when>]` option. 906 907color.diff.<slot>:: 908 Use customized color for diff colorization. `<slot>` specifies 909 which part of the patch to use the specified color, and is one 910 of `plain` (context text), `meta` (metainformation), `frag` 911 (hunk header), 'func' (function in hunk header), `old` (removed lines), 912 `new` (added lines), `commit` (commit headers), or `whitespace` 913 (highlighting whitespace errors). 914 915color.decorate.<slot>:: 916 Use customized color for 'git log --decorate' output. `<slot>` is one 917 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 918 branches, remote-tracking branches, tags, stash and HEAD, respectively. 919 920color.grep:: 921 When set to `always`, always highlight matches. When `false` (or 922 `never`), never. When set to `true` or `auto`, use color only 923 when the output is written to the terminal. Defaults to `false`. 924 925color.grep.<slot>:: 926 Use customized color for grep colorization. `<slot>` specifies which 927 part of the line to use the specified color, and is one of 928+ 929-- 930`context`;; 931 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 932`filename`;; 933 filename prefix (when not using `-h`) 934`function`;; 935 function name lines (when using `-p`) 936`linenumber`;; 937 line number prefix (when using `-n`) 938`match`;; 939 matching text (same as setting `matchContext` and `matchSelected`) 940`matchContext`;; 941 matching text in context lines 942`matchSelected`;; 943 matching text in selected lines 944`selected`;; 945 non-matching text in selected lines 946`separator`;; 947 separators between fields on a line (`:`, `-`, and `=`) 948 and between hunks (`--`) 949-- 950 951color.interactive:: 952 When set to `always`, always use colors for interactive prompts 953 and displays (such as those used by "git-add --interactive" and 954 "git-clean --interactive"). When false (or `never`), never. 955 When set to `true` or `auto`, use colors only when the output is 956 to the terminal. Defaults to false. 957 958color.interactive.<slot>:: 959 Use customized color for 'git add --interactive' and 'git clean 960 --interactive' output. `<slot>` may be `prompt`, `header`, `help` 961 or `error`, for four distinct types of normal output from 962 interactive commands. 963 964color.pager:: 965 A boolean to enable/disable colored output when the pager is in 966 use (default is true). 967 968color.showbranch:: 969 A boolean to enable/disable color in the output of 970 linkgit:git-show-branch[1]. May be set to `always`, 971 `false` (or `never`) or `auto` (or `true`), in which case colors are used 972 only when the output is to a terminal. Defaults to false. 973 974color.status:: 975 A boolean to enable/disable color in the output of 976 linkgit:git-status[1]. May be set to `always`, 977 `false` (or `never`) or `auto` (or `true`), in which case colors are used 978 only when the output is to a terminal. Defaults to false. 979 980color.status.<slot>:: 981 Use customized color for status colorization. `<slot>` is 982 one of `header` (the header text of the status message), 983 `added` or `updated` (files which are added but not committed), 984 `changed` (files which are changed but not added in the index), 985 `untracked` (files which are not tracked by Git), 986 `branch` (the current branch), 987 `nobranch` (the color the 'no branch' warning is shown in, defaulting 988 to red), or 989 `unmerged` (files which have unmerged changes). 990 991color.ui:: 992 This variable determines the default value for variables such 993 as `color.diff` and `color.grep` that control the use of color 994 per command family. Its scope will expand as more commands learn 995 configuration to set a default for the `--color` option. Set it 996 to `false` or `never` if you prefer Git commands not to use 997 color unless enabled explicitly with some other configuration 998 or the `--color` option. Set it to `always` if you want all 999 output not intended for machine consumption to use color, to1000 `true` or `auto` (this is the default since Git 1.8.4) if you1001 want such output to use color when written to the terminal.10021003column.ui::1004 Specify whether supported commands should output in columns.1005 This variable consists of a list of tokens separated by spaces1006 or commas:1007+1008These options control when the feature should be enabled1009(defaults to 'never'):1010+1011--1012`always`;;1013 always show in columns1014`never`;;1015 never show in columns1016`auto`;;1017 show in columns if the output is to the terminal1018--1019+1020These options control layout (defaults to 'column'). Setting any1021of these implies 'always' if none of 'always', 'never', or 'auto' are1022specified.1023+1024--1025`column`;;1026 fill columns before rows1027`row`;;1028 fill rows before columns1029`plain`;;1030 show in one column1031--1032+1033Finally, these options can be combined with a layout option (defaults1034to 'nodense'):1035+1036--1037`dense`;;1038 make unequal size columns to utilize more space1039`nodense`;;1040 make equal size columns1041--10421043column.branch::1044 Specify whether to output branch listing in `git branch` in columns.1045 See `column.ui` for details.10461047column.clean::1048 Specify the layout when list items in `git clean -i`, which always1049 shows files and directories in columns. See `column.ui` for details.10501051column.status::1052 Specify whether to output untracked files in `git status` in columns.1053 See `column.ui` for details.10541055column.tag::1056 Specify whether to output tag listing in `git tag` in columns.1057 See `column.ui` for details.10581059commit.cleanup::1060 This setting overrides the default of the `--cleanup` option in1061 `git commit`. See linkgit:git-commit[1] for details. Changing the1062 default can be useful when you always want to keep lines that begin1063 with comment character `#` in your log message, in which case you1064 would do `git config commit.cleanup whitespace` (note that you will1065 have to remove the help lines that begin with `#` in the commit log1066 template yourself, if you do this).10671068commit.gpgsign::10691070 A boolean to specify whether all commits should be GPG signed.1071 Use of this option when doing operations such as rebase can1072 result in a large number of commits being signed. It may be1073 convenient to use an agent to avoid typing your GPG passphrase1074 several times.10751076commit.status::1077 A boolean to enable/disable inclusion of status information in the1078 commit message template when using an editor to prepare the commit1079 message. Defaults to true.10801081commit.template::1082 Specify a file to use as the template for new commit messages.1083 "`~/`" is expanded to the value of `$HOME` and "`~user/`" to the1084 specified user's home directory.10851086credential.helper::1087 Specify an external helper to be called when a username or1088 password credential is needed; the helper may consult external1089 storage to avoid prompting the user for the credentials. See1090 linkgit:gitcredentials[7] for details.10911092credential.useHttpPath::1093 When acquiring credentials, consider the "path" component of an http1094 or https URL to be important. Defaults to false. See1095 linkgit:gitcredentials[7] for more information.10961097credential.username::1098 If no username is set for a network authentication, use this username1099 by default. See credential.<context>.* below, and1100 linkgit:gitcredentials[7].11011102credential.<url>.*::1103 Any of the credential.* options above can be applied selectively to1104 some credentials. For example "credential.https://example.com.username"1105 would set the default username only for https connections to1106 example.com. See linkgit:gitcredentials[7] for details on how URLs are1107 matched.11081109include::diff-config.txt[]11101111difftool.<tool>.path::1112 Override the path for the given tool. This is useful in case1113 your tool is not in the PATH.11141115difftool.<tool>.cmd::1116 Specify the command to invoke the specified diff tool.1117 The specified command is evaluated in shell with the following1118 variables available: 'LOCAL' is set to the name of the temporary1119 file containing the contents of the diff pre-image and 'REMOTE'1120 is set to the name of the temporary file containing the contents1121 of the diff post-image.11221123difftool.prompt::1124 Prompt before each invocation of the diff tool.11251126fetch.recurseSubmodules::1127 This option can be either set to a boolean value or to 'on-demand'.1128 Setting it to a boolean changes the behavior of fetch and pull to1129 unconditionally recurse into submodules when set to true or to not1130 recurse at all when set to false. When set to 'on-demand' (the default1131 value), fetch and pull will only recurse into a populated submodule1132 when its superproject retrieves a commit that updates the submodule's1133 reference.11341135fetch.fsckObjects::1136 If it is set to true, git-fetch-pack will check all fetched1137 objects. It will abort in the case of a malformed object or a1138 broken link. The result of an abort are only dangling objects.1139 Defaults to false. If not set, the value of `transfer.fsckObjects`1140 is used instead.11411142fetch.unpackLimit::1143 If the number of objects fetched over the Git native1144 transfer is below this1145 limit, then the objects will be unpacked into loose object1146 files. However if the number of received objects equals or1147 exceeds this limit then the received pack will be stored as1148 a pack, after adding any missing delta bases. Storing the1149 pack from a push can make the push operation complete faster,1150 especially on slow filesystems. If not set, the value of1151 `transfer.unpackLimit` is used instead.11521153fetch.prune::1154 If true, fetch will automatically behave as if the `--prune`1155 option was given on the command line. See also `remote.<name>.prune`.11561157format.attach::1158 Enable multipart/mixed attachments as the default for1159 'format-patch'. The value can also be a double quoted string1160 which will enable attachments as the default and set the1161 value as the boundary. See the --attach option in1162 linkgit:git-format-patch[1].11631164format.numbered::1165 A boolean which can enable or disable sequence numbers in patch1166 subjects. It defaults to "auto" which enables it only if there1167 is more than one patch. It can be enabled or disabled for all1168 messages by setting it to "true" or "false". See --numbered1169 option in linkgit:git-format-patch[1].11701171format.headers::1172 Additional email headers to include in a patch to be submitted1173 by mail. See linkgit:git-format-patch[1].11741175format.to::1176format.cc::1177 Additional recipients to include in a patch to be submitted1178 by mail. See the --to and --cc options in1179 linkgit:git-format-patch[1].11801181format.subjectprefix::1182 The default for format-patch is to output files with the '[PATCH]'1183 subject prefix. Use this variable to change that prefix.11841185format.signature::1186 The default for format-patch is to output a signature containing1187 the Git version number. Use this variable to change that default.1188 Set this variable to the empty string ("") to suppress1189 signature generation.11901191format.signaturefile::1192 Works just like format.signature except the contents of the1193 file specified by this variable will be used as the signature.11941195format.suffix::1196 The default for format-patch is to output files with the suffix1197 `.patch`. Use this variable to change that suffix (make sure to1198 include the dot if you want it).11991200format.pretty::1201 The default pretty format for log/show/whatchanged command,1202 See linkgit:git-log[1], linkgit:git-show[1],1203 linkgit:git-whatchanged[1].12041205format.thread::1206 The default threading style for 'git format-patch'. Can be1207 a boolean value, or `shallow` or `deep`. `shallow` threading1208 makes every mail a reply to the head of the series,1209 where the head is chosen from the cover letter, the1210 `--in-reply-to`, and the first patch mail, in this order.1211 `deep` threading makes every mail a reply to the previous one.1212 A true boolean value is the same as `shallow`, and a false1213 value disables threading.12141215format.signoff::1216 A boolean value which lets you enable the `-s/--signoff` option of1217 format-patch by default. *Note:* Adding the Signed-off-by: line to a1218 patch should be a conscious act and means that you certify you have1219 the rights to submit this work under the same open source license.1220 Please see the 'SubmittingPatches' document for further discussion.12211222format.coverLetter::1223 A boolean that controls whether to generate a cover-letter when1224 format-patch is invoked, but in addition can be set to "auto", to1225 generate a cover-letter only when there's more than one patch.12261227filter.<driver>.clean::1228 The command which is used to convert the content of a worktree1229 file to a blob upon checkin. See linkgit:gitattributes[5] for1230 details.12311232filter.<driver>.smudge::1233 The command which is used to convert the content of a blob1234 object to a worktree file upon checkout. See1235 linkgit:gitattributes[5] for details.12361237gc.aggressiveDepth::1238 The depth parameter used in the delta compression1239 algorithm used by 'git gc --aggressive'. This defaults1240 to 250.12411242gc.aggressiveWindow::1243 The window size parameter used in the delta compression1244 algorithm used by 'git gc --aggressive'. This defaults1245 to 250.12461247gc.auto::1248 When there are approximately more than this many loose1249 objects in the repository, `git gc --auto` will pack them.1250 Some Porcelain commands use this command to perform a1251 light-weight garbage collection from time to time. The1252 default value is 6700. Setting this to 0 disables it.12531254gc.autopacklimit::1255 When there are more than this many packs that are not1256 marked with `*.keep` file in the repository, `git gc1257 --auto` consolidates them into one larger pack. The1258 default value is 50. Setting this to 0 disables it.12591260gc.autodetach::1261 Make `git gc --auto` return immediately and run in background1262 if the system supports it. Default is true.12631264gc.packrefs::1265 Running `git pack-refs` in a repository renders it1266 unclonable by Git versions prior to 1.5.1.2 over dumb1267 transports such as HTTP. This variable determines whether1268 'git gc' runs `git pack-refs`. This can be set to `notbare`1269 to enable it within all non-bare repos or it can be set to a1270 boolean value. The default is `true`.12711272gc.pruneexpire::1273 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1274 Override the grace period with this config variable. The value1275 "now" may be used to disable this grace period and always prune1276 unreachable objects immediately.12771278gc.reflogexpire::1279gc.<pattern>.reflogexpire::1280 'git reflog expire' removes reflog entries older than1281 this time; defaults to 90 days. With "<pattern>" (e.g.1282 "refs/stash") in the middle the setting applies only to1283 the refs that match the <pattern>.12841285gc.reflogexpireunreachable::1286gc.<ref>.reflogexpireunreachable::1287 'git reflog expire' removes reflog entries older than1288 this time and are not reachable from the current tip;1289 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")1290 in the middle, the setting applies only to the refs that1291 match the <pattern>.12921293gc.rerereresolved::1294 Records of conflicted merge you resolved earlier are1295 kept for this many days when 'git rerere gc' is run.1296 The default is 60 days. See linkgit:git-rerere[1].12971298gc.rerereunresolved::1299 Records of conflicted merge you have not resolved are1300 kept for this many days when 'git rerere gc' is run.1301 The default is 15 days. See linkgit:git-rerere[1].13021303gitcvs.commitmsgannotation::1304 Append this string to each commit message. Set to empty string1305 to disable this feature. Defaults to "via git-CVS emulator".13061307gitcvs.enabled::1308 Whether the CVS server interface is enabled for this repository.1309 See linkgit:git-cvsserver[1].13101311gitcvs.logfile::1312 Path to a log file where the CVS server interface well... logs1313 various stuff. See linkgit:git-cvsserver[1].13141315gitcvs.usecrlfattr::1316 If true, the server will look up the end-of-line conversion1317 attributes for files to determine the '-k' modes to use. If1318 the attributes force Git to treat a file as text,1319 the '-k' mode will be left blank so CVS clients will1320 treat it as text. If they suppress text conversion, the file1321 will be set with '-kb' mode, which suppresses any newline munging1322 the client might otherwise do. If the attributes do not allow1323 the file type to be determined, then 'gitcvs.allbinary' is1324 used. See linkgit:gitattributes[5].13251326gitcvs.allbinary::1327 This is used if 'gitcvs.usecrlfattr' does not resolve1328 the correct '-kb' mode to use. If true, all1329 unresolved files are sent to the client in1330 mode '-kb'. This causes the client to treat them1331 as binary files, which suppresses any newline munging it1332 otherwise might do. Alternatively, if it is set to "guess",1333 then the contents of the file are examined to decide if1334 it is binary, similar to 'core.autocrlf'.13351336gitcvs.dbname::1337 Database used by git-cvsserver to cache revision information1338 derived from the Git repository. The exact meaning depends on the1339 used database driver, for SQLite (which is the default driver) this1340 is a filename. Supports variable substitution (see1341 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1342 Default: '%Ggitcvs.%m.sqlite'13431344gitcvs.dbdriver::1345 Used Perl DBI driver. You can specify any available driver1346 for this here, but it might not work. git-cvsserver is tested1347 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1348 reported *not* to work with 'DBD::mysql'. Experimental feature.1349 May not contain double colons (`:`). Default: 'SQLite'.1350 See linkgit:git-cvsserver[1].13511352gitcvs.dbuser, gitcvs.dbpass::1353 Database user and password. Only useful if setting 'gitcvs.dbdriver',1354 since SQLite has no concept of database users and/or passwords.1355 'gitcvs.dbuser' supports variable substitution (see1356 linkgit:git-cvsserver[1] for details).13571358gitcvs.dbTableNamePrefix::1359 Database table name prefix. Prepended to the names of any1360 database tables used, allowing a single database to be used1361 for several repositories. Supports variable substitution (see1362 linkgit:git-cvsserver[1] for details). Any non-alphabetic1363 characters will be replaced with underscores.13641365All gitcvs variables except for 'gitcvs.usecrlfattr' and1366'gitcvs.allbinary' can also be specified as1367'gitcvs.<access_method>.<varname>' (where 'access_method'1368is one of "ext" and "pserver") to make them apply only for the given1369access method.13701371gitweb.category::1372gitweb.description::1373gitweb.owner::1374gitweb.url::1375 See linkgit:gitweb[1] for description.13761377gitweb.avatar::1378gitweb.blame::1379gitweb.grep::1380gitweb.highlight::1381gitweb.patches::1382gitweb.pickaxe::1383gitweb.remote_heads::1384gitweb.showsizes::1385gitweb.snapshot::1386 See linkgit:gitweb.conf[5] for description.13871388grep.lineNumber::1389 If set to true, enable '-n' option by default.13901391grep.patternType::1392 Set the default matching behavior. Using a value of 'basic', 'extended',1393 'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',1394 '--fixed-strings', or '--perl-regexp' option accordingly, while the1395 value 'default' will return to the default matching behavior.13961397grep.extendedRegexp::1398 If set to true, enable '--extended-regexp' option by default. This1399 option is ignored when the 'grep.patternType' option is set to a value1400 other than 'default'.14011402gpg.program::1403 Use this custom program instead of "gpg" found on $PATH when1404 making or verifying a PGP signature. The program must support the1405 same command-line interface as GPG, namely, to verify a detached1406 signature, "gpg --verify $file - <$signature" is run, and the1407 program is expected to signal a good signature by exiting with1408 code 0, and to generate an ASCII-armored detached signature, the1409 standard input of "gpg -bsau $key" is fed with the contents to be1410 signed, and the program is expected to send the result to its1411 standard output.14121413gui.commitmsgwidth::1414 Defines how wide the commit message window is in the1415 linkgit:git-gui[1]. "75" is the default.14161417gui.diffcontext::1418 Specifies how many context lines should be used in calls to diff1419 made by the linkgit:git-gui[1]. The default is "5".14201421gui.displayuntracked::1422 Determines if linkgit::git-gui[1] shows untracked files1423 in the file list. The default is "true".14241425gui.encoding::1426 Specifies the default encoding to use for displaying of1427 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1428 It can be overridden by setting the 'encoding' attribute1429 for relevant files (see linkgit:gitattributes[5]).1430 If this option is not set, the tools default to the1431 locale encoding.14321433gui.matchtrackingbranch::1434 Determines if new branches created with linkgit:git-gui[1] should1435 default to tracking remote branches with matching names or1436 not. Default: "false".14371438gui.newbranchtemplate::1439 Is used as suggested name when creating new branches using the1440 linkgit:git-gui[1].14411442gui.pruneduringfetch::1443 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1444 performing a fetch. The default value is "false".14451446gui.trustmtime::1447 Determines if linkgit:git-gui[1] should trust the file modification1448 timestamp or not. By default the timestamps are not trusted.14491450gui.spellingdictionary::1451 Specifies the dictionary used for spell checking commit messages in1452 the linkgit:git-gui[1]. When set to "none" spell checking is turned1453 off.14541455gui.fastcopyblame::1456 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1457 location detection. It makes blame significantly faster on huge1458 repositories at the expense of less thorough copy detection.14591460gui.copyblamethreshold::1461 Specifies the threshold to use in 'git gui blame' original location1462 detection, measured in alphanumeric characters. See the1463 linkgit:git-blame[1] manual for more information on copy detection.14641465gui.blamehistoryctx::1466 Specifies the radius of history context in days to show in1467 linkgit:gitk[1] for the selected commit, when the `Show History1468 Context` menu item is invoked from 'git gui blame'. If this1469 variable is set to zero, the whole history is shown.14701471guitool.<name>.cmd::1472 Specifies the shell command line to execute when the corresponding item1473 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1474 mandatory for every tool. The command is executed from the root of1475 the working directory, and in the environment it receives the name of1476 the tool as 'GIT_GUITOOL', the name of the currently selected file as1477 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1478 the head is detached, 'CUR_BRANCH' is empty).14791480guitool.<name>.needsfile::1481 Run the tool only if a diff is selected in the GUI. It guarantees1482 that 'FILENAME' is not empty.14831484guitool.<name>.noconsole::1485 Run the command silently, without creating a window to display its1486 output.14871488guitool.<name>.norescan::1489 Don't rescan the working directory for changes after the tool1490 finishes execution.14911492guitool.<name>.confirm::1493 Show a confirmation dialog before actually running the tool.14941495guitool.<name>.argprompt::1496 Request a string argument from the user, and pass it to the tool1497 through the 'ARGS' environment variable. Since requesting an1498 argument implies confirmation, the 'confirm' option has no effect1499 if this is enabled. If the option is set to 'true', 'yes', or '1',1500 the dialog uses a built-in generic prompt; otherwise the exact1501 value of the variable is used.15021503guitool.<name>.revprompt::1504 Request a single valid revision from the user, and set the1505 'REVISION' environment variable. In other aspects this option1506 is similar to 'argprompt', and can be used together with it.15071508guitool.<name>.revunmerged::1509 Show only unmerged branches in the 'revprompt' subdialog.1510 This is useful for tools similar to merge or rebase, but not1511 for things like checkout or reset.15121513guitool.<name>.title::1514 Specifies the title to use for the prompt dialog. The default1515 is the tool name.15161517guitool.<name>.prompt::1518 Specifies the general prompt string to display at the top of1519 the dialog, before subsections for 'argprompt' and 'revprompt'.1520 The default value includes the actual command.15211522help.browser::1523 Specify the browser that will be used to display help in the1524 'web' format. See linkgit:git-help[1].15251526help.format::1527 Override the default help format used by linkgit:git-help[1].1528 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1529 the default. 'web' and 'html' are the same.15301531help.autocorrect::1532 Automatically correct and execute mistyped commands after1533 waiting for the given number of deciseconds (0.1 sec). If more1534 than one command can be deduced from the entered text, nothing1535 will be executed. If the value of this option is negative,1536 the corrected command will be executed immediately. If the1537 value is 0 - the command will be just shown but not executed.1538 This is the default.15391540help.htmlpath::1541 Specify the path where the HTML documentation resides. File system paths1542 and URLs are supported. HTML pages will be prefixed with this path when1543 help is displayed in the 'web' format. This defaults to the documentation1544 path of your Git installation.15451546http.proxy::1547 Override the HTTP proxy, normally configured using the 'http_proxy',1548 'https_proxy', and 'all_proxy' environment variables (see1549 `curl(1)`). This can be overridden on a per-remote basis; see1550 remote.<name>.proxy15511552http.cookiefile::1553 File containing previously stored cookie lines which should be used1554 in the Git http session, if they match the server. The file format1555 of the file to read cookies from should be plain HTTP headers or1556 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1557 NOTE that the file specified with http.cookiefile is only used as1558 input unless http.saveCookies is set.15591560http.savecookies::1561 If set, store cookies received during requests to the file specified by1562 http.cookiefile. Has no effect if http.cookiefile is unset.15631564http.sslCipherList::1565 A list of SSL ciphers to use when negotiating an SSL connection.1566 The available ciphers depend on whether libcurl was built against1567 NSS or OpenSSL and the particular configuration of the crypto1568 library in use. Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'1569 option; see the libcurl documentation for more details on the format1570 of this list.1571+1572Can be overridden by the 'GIT_SSL_CIPHER_LIST' environment variable.1573To force git to use libcurl's default cipher list and ignore any1574explicit http.sslCipherList option, set 'GIT_SSL_CIPHER_LIST' to the1575empty string.15761577http.sslVerify::1578 Whether to verify the SSL certificate when fetching or pushing1579 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1580 variable.15811582http.sslCert::1583 File containing the SSL certificate when fetching or pushing1584 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1585 variable.15861587http.sslKey::1588 File containing the SSL private key when fetching or pushing1589 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1590 variable.15911592http.sslCertPasswordProtected::1593 Enable Git's password prompt for the SSL certificate. Otherwise1594 OpenSSL will prompt the user, possibly many times, if the1595 certificate or private key is encrypted. Can be overridden by the1596 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.15971598http.sslCAInfo::1599 File containing the certificates to verify the peer with when1600 fetching or pushing over HTTPS. Can be overridden by the1601 'GIT_SSL_CAINFO' environment variable.16021603http.sslCAPath::1604 Path containing files with the CA certificates to verify the peer1605 with when fetching or pushing over HTTPS. Can be overridden1606 by the 'GIT_SSL_CAPATH' environment variable.16071608http.sslTry::1609 Attempt to use AUTH SSL/TLS and encrypted data transfers1610 when connecting via regular FTP protocol. This might be needed1611 if the FTP server requires it for security reasons or you wish1612 to connect securely whenever remote FTP server supports it.1613 Default is false since it might trigger certificate verification1614 errors on misconfigured servers.16151616http.maxRequests::1617 How many HTTP requests to launch in parallel. Can be overridden1618 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.16191620http.minSessions::1621 The number of curl sessions (counted across slots) to be kept across1622 requests. They will not be ended with curl_easy_cleanup() until1623 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1624 value will be capped at 1. Defaults to 1.16251626http.postBuffer::1627 Maximum size in bytes of the buffer used by smart HTTP1628 transports when POSTing data to the remote system.1629 For requests larger than this buffer size, HTTP/1.1 and1630 Transfer-Encoding: chunked is used to avoid creating a1631 massive pack file locally. Default is 1 MiB, which is1632 sufficient for most requests.16331634http.lowSpeedLimit, http.lowSpeedTime::1635 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1636 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1637 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1638 'GIT_HTTP_LOW_SPEED_TIME' environment variables.16391640http.noEPSV::1641 A boolean which disables using of EPSV ftp command by curl.1642 This can helpful with some "poor" ftp servers which don't1643 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1644 environment variable. Default is false (curl will use EPSV).16451646http.useragent::1647 The HTTP USER_AGENT string presented to an HTTP server. The default1648 value represents the version of the client Git such as git/1.7.1.1649 This option allows you to override this value to a more common value1650 such as Mozilla/4.0. This may be necessary, for instance, if1651 connecting through a firewall that restricts HTTP connections to a set1652 of common USER_AGENT strings (but not including those like git/1.7.1).1653 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.16541655http.<url>.*::1656 Any of the http.* options above can be applied selectively to some URLs.1657 For a config key to match a URL, each element of the config key is1658 compared to that of the URL, in the following order:1659+1660--1661. Scheme (e.g., `https` in `https://example.com/`). This field1662 must match exactly between the config key and the URL.16631664. Host/domain name (e.g., `example.com` in `https://example.com/`).1665 This field must match exactly between the config key and the URL.16661667. Port number (e.g., `8080` in `http://example.com:8080/`).1668 This field must match exactly between the config key and the URL.1669 Omitted port numbers are automatically converted to the correct1670 default for the scheme before matching.16711672. Path (e.g., `repo.git` in `https://example.com/repo.git`). The1673 path field of the config key must match the path field of the URL1674 either exactly or as a prefix of slash-delimited path elements. This means1675 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only1676 match on a slash (`/`) boundary. Longer matches take precedence (so a config1677 key with path `foo/bar` is a better match to URL path `foo/bar` than a config1678 key with just path `foo/`).16791680. User name (e.g., `user` in `https://user@example.com/repo.git`). If1681 the config key has a user name it must match the user name in the1682 URL exactly. If the config key does not have a user name, that1683 config key will match a URL with any user name (including none),1684 but at a lower precedence than a config key with a user name.1685--1686+1687The list above is ordered by decreasing precedence; a URL that matches1688a config key's path is preferred to one that matches its user name. For example,1689if the URL is `https://user@example.com/foo/bar` a config key match of1690`https://example.com/foo` will be preferred over a config key match of1691`https://user@example.com`.1692+1693All URLs are normalized before attempting any matching (the password part,1694if embedded in the URL, is always ignored for matching purposes) so that1695equivalent URLs that are simply spelled differently will match properly.1696Environment variable settings always override any matches. The URLs that are1697matched against are those given directly to Git commands. This means any URLs1698visited as a result of a redirection do not participate in matching.16991700i18n.commitEncoding::1701 Character encoding the commit messages are stored in; Git itself1702 does not care per se, but this information is necessary e.g. when1703 importing commits from emails or in the gitk graphical history1704 browser (and possibly at other places in the future or in other1705 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.17061707i18n.logOutputEncoding::1708 Character encoding the commit messages are converted to when1709 running 'git log' and friends.17101711imap::1712 The configuration variables in the 'imap' section are described1713 in linkgit:git-imap-send[1].17141715index.version::1716 Specify the version with which new index files should be1717 initialized. This does not affect existing repositories.17181719init.templatedir::1720 Specify the directory from which templates will be copied.1721 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)17221723instaweb.browser::1724 Specify the program that will be used to browse your working1725 repository in gitweb. See linkgit:git-instaweb[1].17261727instaweb.httpd::1728 The HTTP daemon command-line to start gitweb on your working1729 repository. See linkgit:git-instaweb[1].17301731instaweb.local::1732 If true the web server started by linkgit:git-instaweb[1] will1733 be bound to the local IP (127.0.0.1).17341735instaweb.modulepath::1736 The default module path for linkgit:git-instaweb[1] to use1737 instead of /usr/lib/apache2/modules. Only used if httpd1738 is Apache.17391740instaweb.port::1741 The port number to bind the gitweb httpd to. See1742 linkgit:git-instaweb[1].17431744interactive.singlekey::1745 In interactive commands, allow the user to provide one-letter1746 input with a single key (i.e., without hitting enter).1747 Currently this is used by the `--patch` mode of1748 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1749 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1750 setting is silently ignored if portable keystroke input1751 is not available; requires the Perl module Term::ReadKey.17521753log.abbrevCommit::1754 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1755 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may1756 override this option with `--no-abbrev-commit`.17571758log.date::1759 Set the default date-time mode for the 'log' command.1760 Setting a value for log.date is similar to using 'git log''s1761 `--date` option. Possible values are `relative`, `local`,1762 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]1763 for details.17641765log.decorate::1766 Print out the ref names of any commits that are shown by the log1767 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1768 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1769 specified, the full ref name (including prefix) will be printed.1770 This is the same as the log commands '--decorate' option.17711772log.showroot::1773 If true, the initial commit will be shown as a big creation event.1774 This is equivalent to a diff against an empty tree.1775 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1776 normally hide the root commit will now show it. True by default.17771778log.mailmap::1779 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1780 linkgit:git-whatchanged[1] assume `--use-mailmap`.17811782mailinfo.scissors::1783 If true, makes linkgit:git-mailinfo[1] (and therefore1784 linkgit:git-am[1]) act by default as if the --scissors option1785 was provided on the command-line. When active, this features1786 removes everything from the message body before a scissors1787 line (i.e. consisting mainly of ">8", "8<" and "-").17881789mailmap.file::1790 The location of an augmenting mailmap file. The default1791 mailmap, located in the root of the repository, is loaded1792 first, then the mailmap file pointed to by this variable.1793 The location of the mailmap file may be in a repository1794 subdirectory, or somewhere outside of the repository itself.1795 See linkgit:git-shortlog[1] and linkgit:git-blame[1].17961797mailmap.blob::1798 Like `mailmap.file`, but consider the value as a reference to a1799 blob in the repository. If both `mailmap.file` and1800 `mailmap.blob` are given, both are parsed, with entries from1801 `mailmap.file` taking precedence. In a bare repository, this1802 defaults to `HEAD:.mailmap`. In a non-bare repository, it1803 defaults to empty.18041805man.viewer::1806 Specify the programs that may be used to display help in the1807 'man' format. See linkgit:git-help[1].18081809man.<tool>.cmd::1810 Specify the command to invoke the specified man viewer. The1811 specified command is evaluated in shell with the man page1812 passed as argument. (See linkgit:git-help[1].)18131814man.<tool>.path::1815 Override the path for the given tool that may be used to1816 display help in the 'man' format. See linkgit:git-help[1].18171818include::merge-config.txt[]18191820mergetool.<tool>.path::1821 Override the path for the given tool. This is useful in case1822 your tool is not in the PATH.18231824mergetool.<tool>.cmd::1825 Specify the command to invoke the specified merge tool. The1826 specified command is evaluated in shell with the following1827 variables available: 'BASE' is the name of a temporary file1828 containing the common base of the files to be merged, if available;1829 'LOCAL' is the name of a temporary file containing the contents of1830 the file on the current branch; 'REMOTE' is the name of a temporary1831 file containing the contents of the file from the branch being1832 merged; 'MERGED' contains the name of the file to which the merge1833 tool should write the results of a successful merge.18341835mergetool.<tool>.trustExitCode::1836 For a custom merge command, specify whether the exit code of1837 the merge command can be used to determine whether the merge was1838 successful. If this is not set to true then the merge target file1839 timestamp is checked and the merge assumed to have been successful1840 if the file has been updated, otherwise the user is prompted to1841 indicate the success of the merge.18421843mergetool.meld.hasOutput::1844 Older versions of `meld` do not support the `--output` option.1845 Git will attempt to detect whether `meld` supports `--output`1846 by inspecting the output of `meld --help`. Configuring1847 `mergetool.meld.hasOutput` will make Git skip these checks and1848 use the configured value instead. Setting `mergetool.meld.hasOutput`1849 to `true` tells Git to unconditionally use the `--output` option,1850 and `false` avoids using `--output`.18511852mergetool.keepBackup::1853 After performing a merge, the original file with conflict markers1854 can be saved as a file with a `.orig` extension. If this variable1855 is set to `false` then this file is not preserved. Defaults to1856 `true` (i.e. keep the backup files).18571858mergetool.keepTemporaries::1859 When invoking a custom merge tool, Git uses a set of temporary1860 files to pass to the tool. If the tool returns an error and this1861 variable is set to `true`, then these temporary files will be1862 preserved, otherwise they will be removed after the tool has1863 exited. Defaults to `false`.18641865mergetool.writeToTemp::1866 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of1867 conflicting files in the worktree by default. Git will attempt1868 to use a temporary directory for these files when set `true`.1869 Defaults to `false`.18701871mergetool.prompt::1872 Prompt before each invocation of the merge resolution program.18731874notes.displayRef::1875 The (fully qualified) refname from which to show notes when1876 showing commit messages. The value of this variable can be set1877 to a glob, in which case notes from all matching refs will be1878 shown. You may also specify this configuration variable1879 several times. A warning will be issued for refs that do not1880 exist, but a glob that does not match any refs is silently1881 ignored.1882+1883This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1884environment variable, which must be a colon separated list of refs or1885globs.1886+1887The effective value of "core.notesRef" (possibly overridden by1888GIT_NOTES_REF) is also implicitly added to the list of refs to be1889displayed.18901891notes.rewrite.<command>::1892 When rewriting commits with <command> (currently `amend` or1893 `rebase`) and this variable is set to `true`, Git1894 automatically copies your notes from the original to the1895 rewritten commit. Defaults to `true`, but see1896 "notes.rewriteRef" below.18971898notes.rewriteMode::1899 When copying notes during a rewrite (see the1900 "notes.rewrite.<command>" option), determines what to do if1901 the target commit already has a note. Must be one of1902 `overwrite`, `concatenate`, or `ignore`. Defaults to1903 `concatenate`.1904+1905This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1906environment variable.19071908notes.rewriteRef::1909 When copying notes during a rewrite, specifies the (fully1910 qualified) ref whose notes should be copied. The ref may be a1911 glob, in which case notes in all matching refs will be copied.1912 You may also specify this configuration several times.1913+1914Does not have a default value; you must configure this variable to1915enable note rewriting. Set it to `refs/notes/commits` to enable1916rewriting for the default commit notes.1917+1918This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1919environment variable, which must be a colon separated list of refs or1920globs.19211922pack.window::1923 The size of the window used by linkgit:git-pack-objects[1] when no1924 window size is given on the command line. Defaults to 10.19251926pack.depth::1927 The maximum delta depth used by linkgit:git-pack-objects[1] when no1928 maximum depth is given on the command line. Defaults to 50.19291930pack.windowMemory::1931 The maximum size of memory that is consumed by each thread1932 in linkgit:git-pack-objects[1] for pack window memory when1933 no limit is given on the command line. The value can be1934 suffixed with "k", "m", or "g". When left unconfigured (or1935 set explicitly to 0), there will be no limit.19361937pack.compression::1938 An integer -1..9, indicating the compression level for objects1939 in a pack file. -1 is the zlib default. 0 means no1940 compression, and 1..9 are various speed/size tradeoffs, 9 being1941 slowest. If not set, defaults to core.compression. If that is1942 not set, defaults to -1, the zlib default, which is "a default1943 compromise between speed and compression (currently equivalent1944 to level 6)."1945+1946Note that changing the compression level will not automatically recompress1947all existing objects. You can force recompression by passing the -F option1948to linkgit:git-repack[1].19491950pack.deltaCacheSize::1951 The maximum memory in bytes used for caching deltas in1952 linkgit:git-pack-objects[1] before writing them out to a pack.1953 This cache is used to speed up the writing object phase by not1954 having to recompute the final delta result once the best match1955 for all objects is found. Repacking large repositories on machines1956 which are tight with memory might be badly impacted by this though,1957 especially if this cache pushes the system into swapping.1958 A value of 0 means no limit. The smallest size of 1 byte may be1959 used to virtually disable this cache. Defaults to 256 MiB.19601961pack.deltaCacheLimit::1962 The maximum size of a delta, that is cached in1963 linkgit:git-pack-objects[1]. This cache is used to speed up the1964 writing object phase by not having to recompute the final delta1965 result once the best match for all objects is found. Defaults to 1000.19661967pack.threads::1968 Specifies the number of threads to spawn when searching for best1969 delta matches. This requires that linkgit:git-pack-objects[1]1970 be compiled with pthreads otherwise this option is ignored with a1971 warning. This is meant to reduce packing time on multiprocessor1972 machines. The required amount of memory for the delta search window1973 is however multiplied by the number of threads.1974 Specifying 0 will cause Git to auto-detect the number of CPU's1975 and set the number of threads accordingly.19761977pack.indexVersion::1978 Specify the default pack index version. Valid values are 1 for1979 legacy pack index used by Git versions prior to 1.5.2, and 2 for1980 the new pack index with capabilities for packs larger than 4 GB1981 as well as proper protection against the repacking of corrupted1982 packs. Version 2 is the default. Note that version 2 is enforced1983 and this config option ignored whenever the corresponding pack is1984 larger than 2 GB.1985+1986If you have an old Git that does not understand the version 2 `*.idx` file,1987cloning or fetching over a non native protocol (e.g. "http" and "rsync")1988that will copy both `*.pack` file and corresponding `*.idx` file from the1989other side may give you a repository that cannot be accessed with your1990older version of Git. If the `*.pack` file is smaller than 2 GB, however,1991you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1992the `*.idx` file.19931994pack.packSizeLimit::1995 The maximum size of a pack. This setting only affects1996 packing to a file when repacking, i.e. the git:// protocol1997 is unaffected. It can be overridden by the `--max-pack-size`1998 option of linkgit:git-repack[1]. The minimum size allowed is1999 limited to 1 MiB. The default is unlimited.2000 Common unit suffixes of 'k', 'm', or 'g' are2001 supported.20022003pack.useBitmaps::2004 When true, git will use pack bitmaps (if available) when packing2005 to stdout (e.g., during the server side of a fetch). Defaults to2006 true. You should not generally need to turn this off unless2007 you are debugging pack bitmaps.20082009pack.writebitmaps (deprecated)::2010 This is a deprecated synonym for `repack.writeBitmaps`.20112012pack.writeBitmapHashCache::2013 When true, git will include a "hash cache" section in the bitmap2014 index (if one is written). This cache can be used to feed git's2015 delta heuristics, potentially leading to better deltas between2016 bitmapped and non-bitmapped objects (e.g., when serving a fetch2017 between an older, bitmapped pack and objects that have been2018 pushed since the last gc). The downside is that it consumes 42019 bytes per object of disk space, and that JGit's bitmap2020 implementation does not understand it, causing it to complain if2021 Git and JGit are used on the same repository. Defaults to false.20222023pager.<cmd>::2024 If the value is boolean, turns on or off pagination of the2025 output of a particular Git subcommand when writing to a tty.2026 Otherwise, turns on pagination for the subcommand using the2027 pager specified by the value of `pager.<cmd>`. If `--paginate`2028 or `--no-pager` is specified on the command line, it takes2029 precedence over this option. To disable pagination for all2030 commands, set `core.pager` or `GIT_PAGER` to `cat`.20312032pretty.<name>::2033 Alias for a --pretty= format string, as specified in2034 linkgit:git-log[1]. Any aliases defined here can be used just2035 as the built-in pretty formats could. For example,2036 running `git config pretty.changelog "format:* %H %s"`2037 would cause the invocation `git log --pretty=changelog`2038 to be equivalent to running `git log "--pretty=format:* %H %s"`.2039 Note that an alias with the same name as a built-in format2040 will be silently ignored.20412042pull.ff::2043 By default, Git does not create an extra merge commit when merging2044 a commit that is a descendant of the current commit. Instead, the2045 tip of the current branch is fast-forwarded. When set to `false`,2046 this variable tells Git to create an extra merge commit in such2047 a case (equivalent to giving the `--no-ff` option from the command2048 line). When set to `only`, only such fast-forward merges are2049 allowed (equivalent to giving the `--ff-only` option from the2050 command line).20512052pull.rebase::2053 When true, rebase branches on top of the fetched branch, instead2054 of merging the default branch from the default remote when "git2055 pull" is run. See "branch.<name>.rebase" for setting this on a2056 per-branch basis.2057+2058 When preserve, also pass `--preserve-merges` along to 'git rebase'2059 so that locally committed merge commits will not be flattened2060 by running 'git pull'.2061+2062*NOTE*: this is a possibly dangerous operation; do *not* use2063it unless you understand the implications (see linkgit:git-rebase[1]2064for details).20652066pull.octopus::2067 The default merge strategy to use when pulling multiple branches2068 at once.20692070pull.twohead::2071 The default merge strategy to use when pulling a single branch.20722073push.default::2074 Defines the action `git push` should take if no refspec is2075 explicitly given. Different values are well-suited for2076 specific workflows; for instance, in a purely central workflow2077 (i.e. the fetch source is equal to the push destination),2078 `upstream` is probably what you want. Possible values are:2079+2080--20812082* `nothing` - do not push anything (error out) unless a refspec is2083 explicitly given. This is primarily meant for people who want to2084 avoid mistakes by always being explicit.20852086* `current` - push the current branch to update a branch with the same2087 name on the receiving end. Works in both central and non-central2088 workflows.20892090* `upstream` - push the current branch back to the branch whose2091 changes are usually integrated into the current branch (which is2092 called `@{upstream}`). This mode only makes sense if you are2093 pushing to the same repository you would normally pull from2094 (i.e. central workflow).20952096* `simple` - in centralized workflow, work like `upstream` with an2097 added safety to refuse to push if the upstream branch's name is2098 different from the local one.2099+2100When pushing to a remote that is different from the remote you normally2101pull from, work as `current`. This is the safest option and is suited2102for beginners.2103+2104This mode has become the default in Git 2.0.21052106* `matching` - push all branches having the same name on both ends.2107 This makes the repository you are pushing to remember the set of2108 branches that will be pushed out (e.g. if you always push 'maint'2109 and 'master' there and no other branches, the repository you push2110 to will have these two branches, and your local 'maint' and2111 'master' will be pushed there).2112+2113To use this mode effectively, you have to make sure _all_ the2114branches you would push out are ready to be pushed out before2115running 'git push', as the whole point of this mode is to allow you2116to push all of the branches in one go. If you usually finish work2117on only one branch and push out the result, while other branches are2118unfinished, this mode is not for you. Also this mode is not2119suitable for pushing into a shared central repository, as other2120people may add new branches there, or update the tip of existing2121branches outside your control.2122+2123This used to be the default, but not since Git 2.0 (`simple` is the2124new default).21252126--21272128rebase.stat::2129 Whether to show a diffstat of what changed upstream since the last2130 rebase. False by default.21312132rebase.autosquash::2133 If set to true enable '--autosquash' option by default.21342135rebase.autostash::2136 When set to true, automatically create a temporary stash2137 before the operation begins, and apply it after the operation2138 ends. This means that you can run rebase on a dirty worktree.2139 However, use with care: the final stash application after a2140 successful rebase might result in non-trivial conflicts.2141 Defaults to false.21422143receive.autogc::2144 By default, git-receive-pack will run "git-gc --auto" after2145 receiving data from git-push and updating refs. You can stop2146 it by setting this variable to false.21472148receive.certnonceseed::2149 By setting this variable to a string, `git receive-pack`2150 will accept a `git push --signed` and verifies it by using2151 a "nonce" protected by HMAC using this string as a secret2152 key.21532154receive.certnonceslop::2155 When a `git push --signed` sent a push certificate with a2156 "nonce" that was issued by a receive-pack serving the same2157 repository within this many seconds, export the "nonce"2158 found in the certificate to `GIT_PUSH_CERT_NONCE` to the2159 hooks (instead of what the receive-pack asked the sending2160 side to include). This may allow writing checks in2161 `pre-receive` and `post-receive` a bit easier. Instead of2162 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable2163 that records by how many seconds the nonce is stale to2164 decide if they want to accept the certificate, they only2165 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.21662167receive.fsckObjects::2168 If it is set to true, git-receive-pack will check all received2169 objects. It will abort in the case of a malformed object or a2170 broken link. The result of an abort are only dangling objects.2171 Defaults to false. If not set, the value of `transfer.fsckObjects`2172 is used instead.21732174receive.unpackLimit::2175 If the number of objects received in a push is below this2176 limit then the objects will be unpacked into loose object2177 files. However if the number of received objects equals or2178 exceeds this limit then the received pack will be stored as2179 a pack, after adding any missing delta bases. Storing the2180 pack from a push can make the push operation complete faster,2181 especially on slow filesystems. If not set, the value of2182 `transfer.unpackLimit` is used instead.21832184receive.denyDeletes::2185 If set to true, git-receive-pack will deny a ref update that deletes2186 the ref. Use this to prevent such a ref deletion via a push.21872188receive.denyDeleteCurrent::2189 If set to true, git-receive-pack will deny a ref update that2190 deletes the currently checked out branch of a non-bare repository.21912192receive.denyCurrentBranch::2193 If set to true or "refuse", git-receive-pack will deny a ref update2194 to the currently checked out branch of a non-bare repository.2195 Such a push is potentially dangerous because it brings the HEAD2196 out of sync with the index and working tree. If set to "warn",2197 print a warning of such a push to stderr, but allow the push to2198 proceed. If set to false or "ignore", allow such pushes with no2199 message. Defaults to "refuse".2200+2201Another option is "updateInstead" which will update the working2202directory (must be clean) if pushing into the current branch. This option is2203intended for synchronizing working directories when one side is not easily2204accessible via interactive ssh (e.g. a live web site, hence the requirement2205that the working directory be clean). This mode also comes in handy when2206developing inside a VM to test and fix code on different Operating Systems.22072208receive.denyNonFastForwards::2209 If set to true, git-receive-pack will deny a ref update which is2210 not a fast-forward. Use this to prevent such an update via a push,2211 even if that push is forced. This configuration variable is2212 set when initializing a shared repository.22132214receive.hiderefs::2215 String(s) `receive-pack` uses to decide which refs to omit2216 from its initial advertisement. Use more than one2217 definitions to specify multiple prefix strings. A ref that2218 are under the hierarchies listed on the value of this2219 variable is excluded, and is hidden when responding to `git2220 push`, and an attempt to update or delete a hidden ref by2221 `git push` is rejected.22222223receive.updateserverinfo::2224 If set to true, git-receive-pack will run git-update-server-info2225 after receiving data from git-push and updating refs.22262227receive.shallowupdate::2228 If set to true, .git/shallow can be updated when new refs2229 require new shallow roots. Otherwise those refs are rejected.22302231remote.pushdefault::2232 The remote to push to by default. Overrides2233 `branch.<name>.remote` for all branches, and is overridden by2234 `branch.<name>.pushremote` for specific branches.22352236remote.<name>.url::2237 The URL of a remote repository. See linkgit:git-fetch[1] or2238 linkgit:git-push[1].22392240remote.<name>.pushurl::2241 The push URL of a remote repository. See linkgit:git-push[1].22422243remote.<name>.proxy::2244 For remotes that require curl (http, https and ftp), the URL to2245 the proxy to use for that remote. Set to the empty string to2246 disable proxying for that remote.22472248remote.<name>.fetch::2249 The default set of "refspec" for linkgit:git-fetch[1]. See2250 linkgit:git-fetch[1].22512252remote.<name>.push::2253 The default set of "refspec" for linkgit:git-push[1]. See2254 linkgit:git-push[1].22552256remote.<name>.mirror::2257 If true, pushing to this remote will automatically behave2258 as if the `--mirror` option was given on the command line.22592260remote.<name>.skipDefaultUpdate::2261 If true, this remote will be skipped by default when updating2262 using linkgit:git-fetch[1] or the `update` subcommand of2263 linkgit:git-remote[1].22642265remote.<name>.skipFetchAll::2266 If true, this remote will be skipped by default when updating2267 using linkgit:git-fetch[1] or the `update` subcommand of2268 linkgit:git-remote[1].22692270remote.<name>.receivepack::2271 The default program to execute on the remote side when pushing. See2272 option \--receive-pack of linkgit:git-push[1].22732274remote.<name>.uploadpack::2275 The default program to execute on the remote side when fetching. See2276 option \--upload-pack of linkgit:git-fetch-pack[1].22772278remote.<name>.tagopt::2279 Setting this value to \--no-tags disables automatic tag following when2280 fetching from remote <name>. Setting it to \--tags will fetch every2281 tag from remote <name>, even if they are not reachable from remote2282 branch heads. Passing these flags directly to linkgit:git-fetch[1] can2283 override this setting. See options \--tags and \--no-tags of2284 linkgit:git-fetch[1].22852286remote.<name>.vcs::2287 Setting this to a value <vcs> will cause Git to interact with2288 the remote with the git-remote-<vcs> helper.22892290remote.<name>.prune::2291 When set to true, fetching from this remote by default will also2292 remove any remote-tracking references that no longer exist on the2293 remote (as if the `--prune` option was given on the command line).2294 Overrides `fetch.prune` settings, if any.22952296remotes.<group>::2297 The list of remotes which are fetched by "git remote update2298 <group>". See linkgit:git-remote[1].22992300repack.usedeltabaseoffset::2301 By default, linkgit:git-repack[1] creates packs that use2302 delta-base offset. If you need to share your repository with2303 Git older than version 1.4.4, either directly or via a dumb2304 protocol such as http, then you need to set this option to2305 "false" and repack. Access from old Git versions over the2306 native protocol are unaffected by this option.23072308repack.packKeptObjects::2309 If set to true, makes `git repack` act as if2310 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for2311 details. Defaults to `false` normally, but `true` if a bitmap2312 index is being written (either via `--write-bitmap-index` or2313 `repack.writeBitmaps`).23142315repack.writeBitmaps::2316 When true, git will write a bitmap index when packing all2317 objects to disk (e.g., when `git repack -a` is run). This2318 index can speed up the "counting objects" phase of subsequent2319 packs created for clones and fetches, at the cost of some disk2320 space and extra time spent on the initial repack. Defaults to2321 false.23222323rerere.autoupdate::2324 When set to true, `git-rerere` updates the index with the2325 resulting contents after it cleanly resolves conflicts using2326 previously recorded resolution. Defaults to false.23272328rerere.enabled::2329 Activate recording of resolved conflicts, so that identical2330 conflict hunks can be resolved automatically, should they be2331 encountered again. By default, linkgit:git-rerere[1] is2332 enabled if there is an `rr-cache` directory under the2333 `$GIT_DIR`, e.g. if "rerere" was previously used in the2334 repository.23352336sendemail.identity::2337 A configuration identity. When given, causes values in the2338 'sendemail.<identity>' subsection to take precedence over2339 values in the 'sendemail' section. The default identity is2340 the value of 'sendemail.identity'.23412342sendemail.smtpencryption::2343 See linkgit:git-send-email[1] for description. Note that this2344 setting is not subject to the 'identity' mechanism.23452346sendemail.smtpssl (deprecated)::2347 Deprecated alias for 'sendemail.smtpencryption = ssl'.23482349sendemail.smtpsslcertpath::2350 Path to ca-certificates (either a directory or a single file).2351 Set it to an empty string to disable certificate verification.23522353sendemail.<identity>.*::2354 Identity-specific versions of the 'sendemail.*' parameters2355 found below, taking precedence over those when the this2356 identity is selected, through command-line or2357 'sendemail.identity'.23582359sendemail.aliasesfile::2360sendemail.aliasfiletype::2361sendemail.annotate::2362sendemail.bcc::2363sendemail.cc::2364sendemail.cccmd::2365sendemail.chainreplyto::2366sendemail.confirm::2367sendemail.envelopesender::2368sendemail.from::2369sendemail.multiedit::2370sendemail.signedoffbycc::2371sendemail.smtppass::2372sendemail.suppresscc::2373sendemail.suppressfrom::2374sendemail.to::2375sendemail.smtpdomain::2376sendemail.smtpserver::2377sendemail.smtpserverport::2378sendemail.smtpserveroption::2379sendemail.smtpuser::2380sendemail.thread::2381sendemail.transferencoding::2382sendemail.validate::2383sendemail.xmailer::2384 See linkgit:git-send-email[1] for description.23852386sendemail.signedoffcc (deprecated)::2387 Deprecated alias for 'sendemail.signedoffbycc'.23882389showbranch.default::2390 The default set of branches for linkgit:git-show-branch[1].2391 See linkgit:git-show-branch[1].23922393status.relativePaths::2394 By default, linkgit:git-status[1] shows paths relative to the2395 current directory. Setting this variable to `false` shows paths2396 relative to the repository root (this was the default for Git2397 prior to v1.5.4).23982399status.short::2400 Set to true to enable --short by default in linkgit:git-status[1].2401 The option --no-short takes precedence over this variable.24022403status.branch::2404 Set to true to enable --branch by default in linkgit:git-status[1].2405 The option --no-branch takes precedence over this variable.24062407status.displayCommentPrefix::2408 If set to true, linkgit:git-status[1] will insert a comment2409 prefix before each output line (starting with2410 `core.commentChar`, i.e. `#` by default). This was the2411 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.2412 Defaults to false.24132414status.showUntrackedFiles::2415 By default, linkgit:git-status[1] and linkgit:git-commit[1] show2416 files which are not currently tracked by Git. Directories which2417 contain only untracked files, are shown with the directory name2418 only. Showing untracked files means that Git needs to lstat() all2419 the files in the whole repository, which might be slow on some2420 systems. So, this variable controls how the commands displays2421 the untracked files. Possible values are:2422+2423--2424* `no` - Show no untracked files.2425* `normal` - Show untracked files and directories.2426* `all` - Show also individual files in untracked directories.2427--2428+2429If this variable is not specified, it defaults to 'normal'.2430This variable can be overridden with the -u|--untracked-files option2431of linkgit:git-status[1] and linkgit:git-commit[1].24322433status.submodulesummary::2434 Defaults to false.2435 If this is set to a non zero number or true (identical to -1 or an2436 unlimited number), the submodule summary will be enabled and a2437 summary of commits for modified submodules will be shown (see2438 --summary-limit option of linkgit:git-submodule[1]). Please note2439 that the summary output command will be suppressed for all2440 submodules when `diff.ignoreSubmodules` is set to 'all' or only2441 for those submodules where `submodule.<name>.ignore=all`. The only2442 exception to that rule is that status and commit will show staged2443 submodule changes. To2444 also view the summary for ignored submodules you can either use2445 the --ignore-submodules=dirty command-line option or the 'git2446 submodule summary' command, which shows a similar output but does2447 not honor these settings.24482449submodule.<name>.path::2450submodule.<name>.url::2451 The path within this project and URL for a submodule. These2452 variables are initially populated by 'git submodule init'. See2453 linkgit:git-submodule[1] and linkgit:gitmodules[5] for2454 details.24552456submodule.<name>.update::2457 The default update procedure for a submodule. This variable2458 is populated by `git submodule init` from the2459 linkgit:gitmodules[5] file. See description of 'update'2460 command in linkgit:git-submodule[1].24612462submodule.<name>.branch::2463 The remote branch name for a submodule, used by `git submodule2464 update --remote`. Set this option to override the value found in2465 the `.gitmodules` file. See linkgit:git-submodule[1] and2466 linkgit:gitmodules[5] for details.24672468submodule.<name>.fetchRecurseSubmodules::2469 This option can be used to control recursive fetching of this2470 submodule. It can be overridden by using the --[no-]recurse-submodules2471 command-line option to "git fetch" and "git pull".2472 This setting will override that from in the linkgit:gitmodules[5]2473 file.24742475submodule.<name>.ignore::2476 Defines under what circumstances "git status" and the diff family show2477 a submodule as modified. When set to "all", it will never be considered2478 modified (but it will nonetheless show up in the output of status and2479 commit when it has been staged), "dirty" will ignore all changes2480 to the submodules work tree and2481 takes only differences between the HEAD of the submodule and the commit2482 recorded in the superproject into account. "untracked" will additionally2483 let submodules with modified tracked files in their work tree show up.2484 Using "none" (the default when this option is not set) also shows2485 submodules that have untracked files in their work tree as changed.2486 This setting overrides any setting made in .gitmodules for this submodule,2487 both settings can be overridden on the command line by using the2488 "--ignore-submodules" option. The 'git submodule' commands are not2489 affected by this setting.24902491tag.sort::2492 This variable controls the sort ordering of tags when displayed by2493 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the2494 value of this variable will be used as the default.24952496tar.umask::2497 This variable can be used to restrict the permission bits of2498 tar archive entries. The default is 0002, which turns off the2499 world write bit. The special value "user" indicates that the2500 archiving user's umask will be used instead. See umask(2) and2501 linkgit:git-archive[1].25022503transfer.fsckObjects::2504 When `fetch.fsckObjects` or `receive.fsckObjects` are2505 not set, the value of this variable is used instead.2506 Defaults to false.25072508transfer.hiderefs::2509 This variable can be used to set both `receive.hiderefs`2510 and `uploadpack.hiderefs` at the same time to the same2511 values. See entries for these other variables.25122513transfer.unpackLimit::2514 When `fetch.unpackLimit` or `receive.unpackLimit` are2515 not set, the value of this variable is used instead.2516 The default value is 100.25172518uploadarchive.allowUnreachable::2519 If true, allow clients to use `git archive --remote` to request2520 any tree, whether reachable from the ref tips or not. See the2521 discussion in the `SECURITY` section of2522 linkgit:git-upload-archive[1] for more details. Defaults to2523 `false`.25242525uploadpack.hiderefs::2526 String(s) `upload-pack` uses to decide which refs to omit2527 from its initial advertisement. Use more than one2528 definitions to specify multiple prefix strings. A ref that2529 are under the hierarchies listed on the value of this2530 variable is excluded, and is hidden from `git ls-remote`,2531 `git fetch`, etc. An attempt to fetch a hidden ref by `git2532 fetch` will fail. See also `uploadpack.allowtipsha1inwant`.25332534uploadpack.allowtipsha1inwant::2535 When `uploadpack.hiderefs` is in effect, allow `upload-pack`2536 to accept a fetch request that asks for an object at the tip2537 of a hidden ref (by default, such a request is rejected).2538 see also `uploadpack.hiderefs`.25392540uploadpack.keepalive::2541 When `upload-pack` has started `pack-objects`, there may be a2542 quiet period while `pack-objects` prepares the pack. Normally2543 it would output progress information, but if `--quiet` was used2544 for the fetch, `pack-objects` will output nothing at all until2545 the pack data begins. Some clients and networks may consider2546 the server to be hung and give up. Setting this option instructs2547 `upload-pack` to send an empty keepalive packet every2548 `uploadpack.keepalive` seconds. Setting this option to 02549 disables keepalive packets entirely. The default is 5 seconds.25502551url.<base>.insteadOf::2552 Any URL that starts with this value will be rewritten to2553 start, instead, with <base>. In cases where some site serves a2554 large number of repositories, and serves them with multiple2555 access methods, and some users need to use different access2556 methods, this feature allows people to specify any of the2557 equivalent URLs and have Git automatically rewrite the URL to2558 the best alternative for the particular user, even for a2559 never-before-seen repository on the site. When more than one2560 insteadOf strings match a given URL, the longest match is used.25612562url.<base>.pushInsteadOf::2563 Any URL that starts with this value will not be pushed to;2564 instead, it will be rewritten to start with <base>, and the2565 resulting URL will be pushed to. In cases where some site serves2566 a large number of repositories, and serves them with multiple2567 access methods, some of which do not allow push, this feature2568 allows people to specify a pull-only URL and have Git2569 automatically use an appropriate URL to push, even for a2570 never-before-seen repository on the site. When more than one2571 pushInsteadOf strings match a given URL, the longest match is2572 used. If a remote has an explicit pushurl, Git will ignore this2573 setting for that remote.25742575user.email::2576 Your email address to be recorded in any newly created commits.2577 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and2578 'EMAIL' environment variables. See linkgit:git-commit-tree[1].25792580user.name::2581 Your full name to be recorded in any newly created commits.2582 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'2583 environment variables. See linkgit:git-commit-tree[1].25842585user.signingkey::2586 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the2587 key you want it to automatically when creating a signed tag or2588 commit, you can override the default selection with this variable.2589 This option is passed unchanged to gpg's --local-user parameter,2590 so you may specify a key using any method that gpg supports.25912592web.browser::2593 Specify a web browser that may be used by some commands.2594 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]2595 may use it.