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 84variable takes a pathname as its value, and is subject to tilde 85expansion. 86 87The 88included file is expanded immediately, as if its contents had been 89found at the location of the include directive. If the value of the 90`include.path` variable is a relative path, the path is considered to be 91relative to the configuration file in which the include directive was 92found. See below for examples. 93 94 95Example 96~~~~~~~ 97 98 # Core variables 99 [core] 100 ; Don't trust file modes 101 filemode = false 102 103 # Our diff algorithm 104 [diff] 105 external = /usr/local/bin/diff-wrapper 106 renames = true 107 108 [branch "devel"] 109 remote = origin 110 merge = refs/heads/devel 111 112 # Proxy settings 113 [core] 114 gitProxy="ssh" for "kernel.org" 115 gitProxy=default-proxy ; for the rest 116 117 [include] 118 path = /path/to/foo.inc ; include by absolute path 119 path = foo ; expand "foo" relative to the current file 120 path = ~/foo ; expand "foo" in your $HOME directory 121 122 123Values 124~~~~~~ 125 126Values of many variables are treated as a simple string, but there 127are variables that take values of specific types and there are rules 128as to how to spell them. 129 130boolean:: 131 132 When a variable is said to take a boolean value, many 133 synonyms are accepted for 'true' and 'false'; these are all 134 case-insensitive. 135 136 true;; Boolean true can be spelled as `yes`, `on`, `true`, 137 or `1`. Also, a variable defined without `= <value>` 138 is taken as true. 139 140 false;; Boolean false can be spelled as `no`, `off`, 141 `false`, or `0`. 142+ 143When converting value to the canonical form using '--bool' type 144specifier; 'git config' will ensure that the output is "true" or 145"false" (spelled in lowercase). 146 147integer:: 148 The value for many variables that specify various sizes can 149 be suffixed with `k`, `M`,... to mean "scale the number by 150 1024", "by 1024x1024", etc. 151 152color:: 153 The value for a variables that takes a color is a list of 154 colors (at most two) and attributes (at most one), separated 155 by spaces. The colors accepted are `normal`, `black`, 156 `red`, `green`, `yellow`, `blue`, `magenta`, `cyan` and 157 `white`; the attributes are `bold`, `dim`, `ul`, `blink` and 158 `reverse`. The first color given is the foreground; the 159 second is the background. The position of the attribute, if 160 any, doesn't matter. Attributes may be turned off specifically 161 by prefixing them with `no` (e.g., `noreverse`, `noul`, etc). 162+ 163Colors (foreground and background) may also be given as numbers between 1640 and 255; these use ANSI 256-color mode (but note that not all 165terminals may support this). If your terminal supports it, you may also 166specify 24-bit RGB values as hex, like `#ff0ab3`. 167+ 168The attributes are meant to be reset at the beginning of each item 169in the colored output, so setting color.decorate.branch to `black` 170will paint that branch name in a plain `black`, even if the previous 171thing on the same output line (e.g. opening parenthesis before the 172list of branch names in `log --decorate` output) is set to be 173painted with `bold` or some other attribute. 174 175pathname:: 176 A variable that takes a pathname value can be given a 177 string that begins with "`~/`" or "`~user/`", and the usual 178 tilde expansion happens to such a string: `~/` 179 is expanded to the value of `$HOME`, and `~user/` to the 180 specified user's home directory. 181 182 183Variables 184~~~~~~~~~ 185 186Note that this list is non-comprehensive and not necessarily complete. 187For command-specific variables, you will find a more detailed description 188in the appropriate manual page. 189 190Other git-related tools may and do use their own variables. When 191inventing new variables for use in your own tool, make sure their 192names do not conflict with those that are used by Git itself and 193other popular tools, and describe them in your documentation. 194 195 196advice.*:: 197 These variables control various optional help messages designed to 198 aid new users. All 'advice.*' variables default to 'true', and you 199 can tell Git that you do not need help by setting these to 'false': 200+ 201-- 202 pushUpdateRejected:: 203 Set this variable to 'false' if you want to disable 204 'pushNonFFCurrent', 205 'pushNonFFMatching', 'pushAlreadyExists', 206 'pushFetchFirst', and 'pushNeedsForce' 207 simultaneously. 208 pushNonFFCurrent:: 209 Advice shown when linkgit:git-push[1] fails due to a 210 non-fast-forward update to the current branch. 211 pushNonFFMatching:: 212 Advice shown when you ran linkgit:git-push[1] and pushed 213 'matching refs' explicitly (i.e. you used ':', or 214 specified a refspec that isn't your current branch) and 215 it resulted in a non-fast-forward error. 216 pushAlreadyExists:: 217 Shown when linkgit:git-push[1] rejects an update that 218 does not qualify for fast-forwarding (e.g., a tag.) 219 pushFetchFirst:: 220 Shown when linkgit:git-push[1] rejects an update that 221 tries to overwrite a remote ref that points at an 222 object we do not have. 223 pushNeedsForce:: 224 Shown when linkgit:git-push[1] rejects an update that 225 tries to overwrite a remote ref that points at an 226 object that is not a commit-ish, or make the remote 227 ref point at an object that is not a commit-ish. 228 statusHints:: 229 Show directions on how to proceed from the current 230 state in the output of linkgit:git-status[1], in 231 the template shown when writing commit messages in 232 linkgit:git-commit[1], and in the help message shown 233 by linkgit:git-checkout[1] when switching branch. 234 statusUoption:: 235 Advise to consider using the `-u` option to linkgit:git-status[1] 236 when the command takes more than 2 seconds to enumerate untracked 237 files. 238 commitBeforeMerge:: 239 Advice shown when linkgit:git-merge[1] refuses to 240 merge to avoid overwriting local changes. 241 resolveConflict:: 242 Advice shown by various commands when conflicts 243 prevent the operation from being performed. 244 implicitIdentity:: 245 Advice on how to set your identity configuration when 246 your information is guessed from the system username and 247 domain name. 248 detachedHead:: 249 Advice shown when you used linkgit:git-checkout[1] to 250 move to the detach HEAD state, to instruct how to create 251 a local branch after the fact. 252 amWorkDir:: 253 Advice that shows the location of the patch file when 254 linkgit:git-am[1] fails to apply it. 255 rmHints:: 256 In case of failure in the output of linkgit:git-rm[1], 257 show directions on how to proceed from the current state. 258-- 259 260core.fileMode:: 261 Tells Git if the executable bit of files in the working tree 262 is to be honored. 263+ 264Some filesystems lose the executable bit when a file that is 265marked as executable is checked out, or checks out an 266non-executable file with executable bit on. 267linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 268to see if it handles the executable bit correctly 269and this variable is automatically set as necessary. 270+ 271A repository, however, may be on a filesystem that handles 272the filemode correctly, and this variable is set to 'true' 273when created, but later may be made accessible from another 274environment that loses the filemode (e.g. exporting ext4 via 275CIFS mount, visiting a Cygwin created repository with 276Git for Windows or Eclipse). 277In such a case it may be necessary to set this variable to 'false'. 278See linkgit:git-update-index[1]. 279+ 280The default is true (when core.filemode is not specified in the config file). 281 282core.ignoreCase:: 283 If true, this option enables various workarounds to enable 284 Git to work better on filesystems that are not case sensitive, 285 like FAT. For example, if a directory listing finds 286 "makefile" when Git expects "Makefile", Git will assume 287 it is really the same file, and continue to remember it as 288 "Makefile". 289+ 290The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 291will probe and set core.ignoreCase true if appropriate when the repository 292is created. 293 294core.precomposeUnicode:: 295 This option is only used by Mac OS implementation of Git. 296 When core.precomposeUnicode=true, Git reverts the unicode decomposition 297 of filenames done by Mac OS. This is useful when sharing a repository 298 between Mac OS and Linux or Windows. 299 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 300 When false, file names are handled fully transparent by Git, 301 which is backward compatible with older versions of Git. 302 303core.protectHFS:: 304 If set to true, do not allow checkout of paths that would 305 be considered equivalent to `.git` on an HFS+ filesystem. 306 Defaults to `true` on Mac OS, and `false` elsewhere. 307 308core.protectNTFS:: 309 If set to true, do not allow checkout of paths that would 310 cause problems with the NTFS filesystem, e.g. conflict with 311 8.3 "short" names. 312 Defaults to `true` on Windows, and `false` elsewhere. 313 314core.trustctime:: 315 If false, the ctime differences between the index and the 316 working tree are ignored; useful when the inode change time 317 is regularly modified by something outside Git (file system 318 crawlers and some backup systems). 319 See linkgit:git-update-index[1]. True by default. 320 321core.untrackedCache:: 322 Determines what to do about the untracked cache feature of the 323 index. It will be kept, if this variable is unset or set to 324 `keep`. It will automatically be added if set to `true`. And 325 it will automatically be removed, if set to `false`. Before 326 setting it to `true`, you should check that mtime is working 327 properly on your system. 328 See linkgit:git-update-index[1]. `keep` by default. 329 330core.checkStat:: 331 Determines which stat fields to match between the index 332 and work tree. The user can set this to 'default' or 333 'minimal'. Default (or explicitly 'default'), is to check 334 all fields, including the sub-second part of mtime and ctime. 335 336core.quotePath:: 337 The commands that output paths (e.g. 'ls-files', 338 'diff'), when not given the `-z` option, will quote 339 "unusual" characters in the pathname by enclosing the 340 pathname in a double-quote pair and with backslashes the 341 same way strings in C source code are quoted. If this 342 variable is set to false, the bytes higher than 0x80 are 343 not quoted but output as verbatim. Note that double 344 quote, backslash and control characters are always 345 quoted without `-z` regardless of the setting of this 346 variable. 347 348core.eol:: 349 Sets the line ending type to use in the working directory for 350 files that have the `text` property set. Alternatives are 351 'lf', 'crlf' and 'native', which uses the platform's native 352 line ending. The default value is `native`. See 353 linkgit:gitattributes[5] for more information on end-of-line 354 conversion. 355 356core.safecrlf:: 357 If true, makes Git check if converting `CRLF` is reversible when 358 end-of-line conversion is active. Git will verify if a command 359 modifies a file in the work tree either directly or indirectly. 360 For example, committing a file followed by checking out the 361 same file should yield the original file in the work tree. If 362 this is not the case for the current setting of 363 `core.autocrlf`, Git will reject the file. The variable can 364 be set to "warn", in which case Git will only warn about an 365 irreversible conversion but continue the operation. 366+ 367CRLF conversion bears a slight chance of corrupting data. 368When it is enabled, Git will convert CRLF to LF during commit and LF to 369CRLF during checkout. A file that contains a mixture of LF and 370CRLF before the commit cannot be recreated by Git. For text 371files this is the right thing to do: it corrects line endings 372such that we have only LF line endings in the repository. 373But for binary files that are accidentally classified as text the 374conversion can corrupt data. 375+ 376If you recognize such corruption early you can easily fix it by 377setting the conversion type explicitly in .gitattributes. Right 378after committing you still have the original file in your work 379tree and this file is not yet corrupted. You can explicitly tell 380Git that this file is binary and Git will handle the file 381appropriately. 382+ 383Unfortunately, the desired effect of cleaning up text files with 384mixed line endings and the undesired effect of corrupting binary 385files cannot be distinguished. In both cases CRLFs are removed 386in an irreversible way. For text files this is the right thing 387to do because CRLFs are line endings, while for binary files 388converting CRLFs corrupts data. 389+ 390Note, this safety check does not mean that a checkout will generate a 391file identical to the original file for a different setting of 392`core.eol` and `core.autocrlf`, but only for the current one. For 393example, a text file with `LF` would be accepted with `core.eol=lf` 394and could later be checked out with `core.eol=crlf`, in which case the 395resulting file would contain `CRLF`, although the original file 396contained `LF`. However, in both work trees the line endings would be 397consistent, that is either all `LF` or all `CRLF`, but never mixed. A 398file with mixed line endings would be reported by the `core.safecrlf` 399mechanism. 400 401core.autocrlf:: 402 Setting this variable to "true" is almost the same as setting 403 the `text` attribute to "auto" on all files except that text 404 files are not guaranteed to be normalized: files that contain 405 `CRLF` in the repository will not be touched. Use this 406 setting if you want to have `CRLF` line endings in your 407 working directory even though the repository does not have 408 normalized line endings. This variable can be set to 'input', 409 in which case no output conversion is performed. 410 411core.symlinks:: 412 If false, symbolic links are checked out as small plain files that 413 contain the link text. linkgit:git-update-index[1] and 414 linkgit:git-add[1] will not change the recorded type to regular 415 file. Useful on filesystems like FAT that do not support 416 symbolic links. 417+ 418The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 419will probe and set core.symlinks false if appropriate when the repository 420is created. 421 422core.gitProxy:: 423 A "proxy command" to execute (as 'command host port') instead 424 of establishing direct connection to the remote server when 425 using the Git protocol for fetching. If the variable value is 426 in the "COMMAND for DOMAIN" format, the command is applied only 427 on hostnames ending with the specified domain string. This variable 428 may be set multiple times and is matched in the given order; 429 the first match wins. 430+ 431Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 432(which always applies universally, without the special "for" 433handling). 434+ 435The special string `none` can be used as the proxy command to 436specify that no proxy be used for a given domain pattern. 437This is useful for excluding servers inside a firewall from 438proxy use, while defaulting to a common proxy for external domains. 439 440core.ignoreStat:: 441 If true, Git will avoid using lstat() calls to detect if files have 442 changed by setting the "assume-unchanged" bit for those tracked files 443 which it has updated identically in both the index and working tree. 444+ 445When files are modified outside of Git, the user will need to stage 446the modified files explicitly (e.g. see 'Examples' section in 447linkgit:git-update-index[1]). 448Git will not normally detect changes to those files. 449+ 450This is useful on systems where lstat() calls are very slow, such as 451CIFS/Microsoft Windows. 452+ 453False by default. 454 455core.preferSymlinkRefs:: 456 Instead of the default "symref" format for HEAD 457 and other symbolic reference files, use symbolic links. 458 This is sometimes needed to work with old scripts that 459 expect HEAD to be a symbolic link. 460 461core.bare:: 462 If true this repository is assumed to be 'bare' and has no 463 working directory associated with it. If this is the case a 464 number of commands that require a working directory will be 465 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 466+ 467This setting is automatically guessed by linkgit:git-clone[1] or 468linkgit:git-init[1] when the repository was created. By default a 469repository that ends in "/.git" is assumed to be not bare (bare = 470false), while all other repositories are assumed to be bare (bare 471= true). 472 473core.worktree:: 474 Set the path to the root of the working tree. 475 If GIT_COMMON_DIR environment variable is set, core.worktree 476 is ignored and not used for determining the root of working tree. 477 This can be overridden by the GIT_WORK_TREE environment 478 variable and the '--work-tree' command-line option. 479 The value can be an absolute path or relative to the path to 480 the .git directory, which is either specified by --git-dir 481 or GIT_DIR, or automatically discovered. 482 If --git-dir or GIT_DIR is specified but none of 483 --work-tree, GIT_WORK_TREE and core.worktree is specified, 484 the current working directory is regarded as the top level 485 of your working tree. 486+ 487Note that this variable is honored even when set in a configuration 488file in a ".git" subdirectory of a directory and its value differs 489from the latter directory (e.g. "/path/to/.git/config" has 490core.worktree set to "/different/path"), which is most likely a 491misconfiguration. Running Git commands in the "/path/to" directory will 492still use "/different/path" as the root of the work tree and can cause 493confusion unless you know what you are doing (e.g. you are creating a 494read-only snapshot of the same index to a location different from the 495repository's usual working tree). 496 497core.logAllRefUpdates:: 498 Enable the reflog. Updates to a ref <ref> is logged to the file 499 "$GIT_DIR/logs/<ref>", by appending the new and old 500 SHA-1, the date/time and the reason of the update, but 501 only when the file exists. If this configuration 502 variable is set to true, missing "$GIT_DIR/logs/<ref>" 503 file is automatically created for branch heads (i.e. under 504 refs/heads/), remote refs (i.e. under refs/remotes/), 505 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 506+ 507This information can be used to determine what commit 508was the tip of a branch "2 days ago". 509+ 510This value is true by default in a repository that has 511a working directory associated with it, and false by 512default in a bare repository. 513 514core.repositoryFormatVersion:: 515 Internal variable identifying the repository format and layout 516 version. 517 518core.sharedRepository:: 519 When 'group' (or 'true'), the repository is made shareable between 520 several users in a group (making sure all the files and objects are 521 group-writable). When 'all' (or 'world' or 'everybody'), the 522 repository will be readable by all users, additionally to being 523 group-shareable. When 'umask' (or 'false'), Git will use permissions 524 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 525 files in the repository will have this mode value. '0xxx' will override 526 user's umask value (whereas the other options will only override 527 requested parts of the user's umask value). Examples: '0660' will make 528 the repo read/write-able for the owner and group, but inaccessible to 529 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 530 repository that is group-readable but not group-writable. 531 See linkgit:git-init[1]. False by default. 532 533core.warnAmbiguousRefs:: 534 If true, Git will warn you if the ref name you passed it is ambiguous 535 and might match multiple refs in the repository. True by default. 536 537core.compression:: 538 An integer -1..9, indicating a default compression level. 539 -1 is the zlib default. 0 means no compression, 540 and 1..9 are various speed/size tradeoffs, 9 being slowest. 541 If set, this provides a default to other compression variables, 542 such as 'core.looseCompression' and 'pack.compression'. 543 544core.looseCompression:: 545 An integer -1..9, indicating the compression level for objects that 546 are not in a pack file. -1 is the zlib default. 0 means no 547 compression, and 1..9 are various speed/size tradeoffs, 9 being 548 slowest. If not set, defaults to core.compression. If that is 549 not set, defaults to 1 (best speed). 550 551core.packedGitWindowSize:: 552 Number of bytes of a pack file to map into memory in a 553 single mapping operation. Larger window sizes may allow 554 your system to process a smaller number of large pack files 555 more quickly. Smaller window sizes will negatively affect 556 performance due to increased calls to the operating system's 557 memory manager, but may improve performance when accessing 558 a large number of large pack files. 559+ 560Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 561MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 562be reasonable for all users/operating systems. You probably do 563not need to adjust this value. 564+ 565Common unit suffixes of 'k', 'm', or 'g' are supported. 566 567core.packedGitLimit:: 568 Maximum number of bytes to map simultaneously into memory 569 from pack files. If Git needs to access more than this many 570 bytes at once to complete an operation it will unmap existing 571 regions to reclaim virtual address space within the process. 572+ 573Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 574This should be reasonable for all users/operating systems, except on 575the largest projects. You probably do not need to adjust this value. 576+ 577Common unit suffixes of 'k', 'm', or 'g' are supported. 578 579core.deltaBaseCacheLimit:: 580 Maximum number of bytes to reserve for caching base objects 581 that may be referenced by multiple deltified objects. By storing the 582 entire decompressed base objects in a cache Git is able 583 to avoid unpacking and decompressing frequently used base 584 objects multiple times. 585+ 586Default is 96 MiB on all platforms. This should be reasonable 587for all users/operating systems, except on the largest projects. 588You probably do not need to adjust this value. 589+ 590Common unit suffixes of 'k', 'm', or 'g' are supported. 591 592core.bigFileThreshold:: 593 Files larger than this size are stored deflated, without 594 attempting delta compression. Storing large files without 595 delta compression avoids excessive memory usage, at the 596 slight expense of increased disk usage. Additionally files 597 larger than this size are always treated as binary. 598+ 599Default is 512 MiB on all platforms. This should be reasonable 600for most projects as source code and other text files can still 601be delta compressed, but larger binary media files won't be. 602+ 603Common unit suffixes of 'k', 'm', or 'g' are supported. 604 605core.excludesFile:: 606 Specifies the pathname to the file that contains patterns to 607 describe paths that are not meant to be tracked, in addition 608 to '.gitignore' (per-directory) and '.git/info/exclude'. 609 Defaults to $XDG_CONFIG_HOME/git/ignore. 610 If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore 611 is used instead. See linkgit:gitignore[5]. 612 613core.askPass:: 614 Some commands (e.g. svn and http interfaces) that interactively 615 ask for a password can be told to use an external program given 616 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 617 environment variable. If not set, fall back to the value of the 618 'SSH_ASKPASS' environment variable or, failing that, a simple password 619 prompt. The external program shall be given a suitable prompt as 620 command-line argument and write the password on its STDOUT. 621 622core.attributesFile:: 623 In addition to '.gitattributes' (per-directory) and 624 '.git/info/attributes', Git looks into this file for attributes 625 (see linkgit:gitattributes[5]). Path expansions are made the same 626 way as for `core.excludesFile`. Its default value is 627 $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not 628 set or empty, $HOME/.config/git/attributes is used instead. 629 630core.hooksPath:: 631 By default Git will look for your hooks in the 632 '$GIT_DIR/hooks' directory. Set this to different path, 633 e.g. '/etc/git/hooks', and Git will try to find your hooks in 634 that directory, e.g. '/etc/git/hooks/pre-receive' instead of 635 in '$GIT_DIR/hooks/pre-receive'. 636+ 637The path can be either absolute or relative. A relative path is 638taken as relative to the directory where the hooks are run (see 639the "DESCRIPTION" section of linkgit:githooks[5]). 640+ 641This configuration variable is useful in cases where you'd like to 642centrally configure your Git hooks instead of configuring them on a 643per-repository basis, or as a more flexible and centralized 644alternative to having an `init.templateDir` where you've changed 645default hooks. 646 647core.editor:: 648 Commands such as `commit` and `tag` that lets you edit 649 messages by launching an editor uses the value of this 650 variable when it is set, and the environment variable 651 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 652 653core.commentChar:: 654 Commands such as `commit` and `tag` that lets you edit 655 messages consider a line that begins with this character 656 commented, and removes them after the editor returns 657 (default '#'). 658+ 659If set to "auto", `git-commit` would select a character that is not 660the beginning character of any line in existing commit messages. 661 662core.packedRefsTimeout:: 663 The length of time, in milliseconds, to retry when trying to 664 lock the `packed-refs` file. Value 0 means not to retry at 665 all; -1 means to try indefinitely. Default is 1000 (i.e., 666 retry for 1 second). 667 668sequence.editor:: 669 Text editor used by `git rebase -i` for editing the rebase instruction file. 670 The value is meant to be interpreted by the shell when it is used. 671 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 672 When not configured the default commit message editor is used instead. 673 674core.pager:: 675 Text viewer for use by Git commands (e.g., 'less'). The value 676 is meant to be interpreted by the shell. The order of preference 677 is the `$GIT_PAGER` environment variable, then `core.pager` 678 configuration, then `$PAGER`, and then the default chosen at 679 compile time (usually 'less'). 680+ 681When the `LESS` environment variable is unset, Git sets it to `FRX` 682(if `LESS` environment variable is set, Git does not change it at 683all). If you want to selectively override Git's default setting 684for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 685be passed to the shell by Git, which will translate the final 686command to `LESS=FRX less -S`. The environment does not set the 687`S` option but the command line does, instructing less to truncate 688long lines. Similarly, setting `core.pager` to `less -+F` will 689deactivate the `F` option specified by the environment from the 690command-line, deactivating the "quit if one screen" behavior of 691`less`. One can specifically activate some flags for particular 692commands: for example, setting `pager.blame` to `less -S` enables 693line truncation only for `git blame`. 694+ 695Likewise, when the `LV` environment variable is unset, Git sets it 696to `-c`. You can override this setting by exporting `LV` with 697another value or setting `core.pager` to `lv +c`. 698 699core.whitespace:: 700 A comma separated list of common whitespace problems to 701 notice. 'git diff' will use `color.diff.whitespace` to 702 highlight them, and 'git apply --whitespace=error' will 703 consider them as errors. You can prefix `-` to disable 704 any of them (e.g. `-trailing-space`): 705+ 706* `blank-at-eol` treats trailing whitespaces at the end of the line 707 as an error (enabled by default). 708* `space-before-tab` treats a space character that appears immediately 709 before a tab character in the initial indent part of the line as an 710 error (enabled by default). 711* `indent-with-non-tab` treats a line that is indented with space 712 characters instead of the equivalent tabs as an error (not enabled by 713 default). 714* `tab-in-indent` treats a tab character in the initial indent part of 715 the line as an error (not enabled by default). 716* `blank-at-eof` treats blank lines added at the end of file as an error 717 (enabled by default). 718* `trailing-space` is a short-hand to cover both `blank-at-eol` and 719 `blank-at-eof`. 720* `cr-at-eol` treats a carriage-return at the end of line as 721 part of the line terminator, i.e. with it, `trailing-space` 722 does not trigger if the character before such a carriage-return 723 is not a whitespace (not enabled by default). 724* `tabwidth=<n>` tells how many character positions a tab occupies; this 725 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 726 errors. The default tab width is 8. Allowed values are 1 to 63. 727 728core.fsyncObjectFiles:: 729 This boolean will enable 'fsync()' when writing object files. 730+ 731This is a total waste of time and effort on a filesystem that orders 732data writes properly, but can be useful for filesystems that do not use 733journalling (traditional UNIX filesystems) or that only journal metadata 734and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 735 736core.preloadIndex:: 737 Enable parallel index preload for operations like 'git diff' 738+ 739This can speed up operations like 'git diff' and 'git status' especially 740on filesystems like NFS that have weak caching semantics and thus 741relatively high IO latencies. When enabled, Git will do the 742index comparison to the filesystem data in parallel, allowing 743overlapping IO's. Defaults to true. 744 745core.createObject:: 746 You can set this to 'link', in which case a hardlink followed by 747 a delete of the source are used to make sure that object creation 748 will not overwrite existing objects. 749+ 750On some file system/operating system combinations, this is unreliable. 751Set this config setting to 'rename' there; However, This will remove the 752check that makes sure that existing object files will not get overwritten. 753 754core.notesRef:: 755 When showing commit messages, also show notes which are stored in 756 the given ref. The ref must be fully qualified. If the given 757 ref does not exist, it is not an error but means that no 758 notes should be printed. 759+ 760This setting defaults to "refs/notes/commits", and it can be overridden by 761the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 762 763core.sparseCheckout:: 764 Enable "sparse checkout" feature. See section "Sparse checkout" in 765 linkgit:git-read-tree[1] for more information. 766 767core.abbrev:: 768 Set the length object names are abbreviated to. If unspecified, 769 many commands abbreviate to 7 hexdigits, which may not be enough 770 for abbreviated object names to stay unique for sufficiently long 771 time. 772 773add.ignoreErrors:: 774add.ignore-errors (deprecated):: 775 Tells 'git add' to continue adding files when some files cannot be 776 added due to indexing errors. Equivalent to the '--ignore-errors' 777 option of linkgit:git-add[1]. `add.ignore-errors` is deprecated, 778 as it does not follow the usual naming convention for configuration 779 variables. 780 781alias.*:: 782 Command aliases for the linkgit:git[1] command wrapper - e.g. 783 after defining "alias.last = cat-file commit HEAD", the invocation 784 "git last" is equivalent to "git cat-file commit HEAD". To avoid 785 confusion and troubles with script usage, aliases that 786 hide existing Git commands are ignored. Arguments are split by 787 spaces, the usual shell quoting and escaping is supported. 788 A quote pair or a backslash can be used to quote them. 789+ 790If the alias expansion is prefixed with an exclamation point, 791it will be treated as a shell command. For example, defining 792"alias.new = !gitk --all --not ORIG_HEAD", the invocation 793"git new" is equivalent to running the shell command 794"gitk --all --not ORIG_HEAD". Note that shell commands will be 795executed from the top-level directory of a repository, which may 796not necessarily be the current directory. 797'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 798from the original current directory. See linkgit:git-rev-parse[1]. 799 800am.keepcr:: 801 If true, git-am will call git-mailsplit for patches in mbox format 802 with parameter '--keep-cr'. In this case git-mailsplit will 803 not remove `\r` from lines ending with `\r\n`. Can be overridden 804 by giving '--no-keep-cr' from the command line. 805 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 806 807am.threeWay:: 808 By default, `git am` will fail if the patch does not apply cleanly. When 809 set to true, this setting tells `git am` to fall back on 3-way merge if 810 the patch records the identity of blobs it is supposed to apply to and 811 we have those blobs available locally (equivalent to giving the `--3way` 812 option from the command line). Defaults to `false`. 813 See linkgit:git-am[1]. 814 815apply.ignoreWhitespace:: 816 When set to 'change', tells 'git apply' to ignore changes in 817 whitespace, in the same way as the '--ignore-space-change' 818 option. 819 When set to one of: no, none, never, false tells 'git apply' to 820 respect all whitespace differences. 821 See linkgit:git-apply[1]. 822 823apply.whitespace:: 824 Tells 'git apply' how to handle whitespaces, in the same way 825 as the '--whitespace' option. See linkgit:git-apply[1]. 826 827branch.autoSetupMerge:: 828 Tells 'git branch' and 'git checkout' to set up new branches 829 so that linkgit:git-pull[1] will appropriately merge from the 830 starting point branch. Note that even if this option is not set, 831 this behavior can be chosen per-branch using the `--track` 832 and `--no-track` options. The valid settings are: `false` -- no 833 automatic setup is done; `true` -- automatic setup is done when the 834 starting point is a remote-tracking branch; `always` -- 835 automatic setup is done when the starting point is either a 836 local branch or remote-tracking 837 branch. This option defaults to true. 838 839branch.autoSetupRebase:: 840 When a new branch is created with 'git branch' or 'git checkout' 841 that tracks another branch, this variable tells Git to set 842 up pull to rebase instead of merge (see "branch.<name>.rebase"). 843 When `never`, rebase is never automatically set to true. 844 When `local`, rebase is set to true for tracked branches of 845 other local branches. 846 When `remote`, rebase is set to true for tracked branches of 847 remote-tracking branches. 848 When `always`, rebase will be set to true for all tracking 849 branches. 850 See "branch.autoSetupMerge" for details on how to set up a 851 branch to track another branch. 852 This option defaults to never. 853 854branch.<name>.remote:: 855 When on branch <name>, it tells 'git fetch' and 'git push' 856 which remote to fetch from/push to. The remote to push to 857 may be overridden with `remote.pushDefault` (for all branches). 858 The remote to push to, for the current branch, may be further 859 overridden by `branch.<name>.pushRemote`. If no remote is 860 configured, or if you are not on any branch, it defaults to 861 `origin` for fetching and `remote.pushDefault` for pushing. 862 Additionally, `.` (a period) is the current local repository 863 (a dot-repository), see `branch.<name>.merge`'s final note below. 864 865branch.<name>.pushRemote:: 866 When on branch <name>, it overrides `branch.<name>.remote` for 867 pushing. It also overrides `remote.pushDefault` for pushing 868 from branch <name>. When you pull from one place (e.g. your 869 upstream) and push to another place (e.g. your own publishing 870 repository), you would want to set `remote.pushDefault` to 871 specify the remote to push to for all branches, and use this 872 option to override it for a specific branch. 873 874branch.<name>.merge:: 875 Defines, together with branch.<name>.remote, the upstream branch 876 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 877 branch to merge and can also affect 'git push' (see push.default). 878 When in branch <name>, it tells 'git fetch' the default 879 refspec to be marked for merging in FETCH_HEAD. The value is 880 handled like the remote part of a refspec, and must match a 881 ref which is fetched from the remote given by 882 "branch.<name>.remote". 883 The merge information is used by 'git pull' (which at first calls 884 'git fetch') to lookup the default branch for merging. Without 885 this option, 'git pull' defaults to merge the first refspec fetched. 886 Specify multiple values to get an octopus merge. 887 If you wish to setup 'git pull' so that it merges into <name> from 888 another branch in the local repository, you can point 889 branch.<name>.merge to the desired branch, and use the relative path 890 setting `.` (a period) for branch.<name>.remote. 891 892branch.<name>.mergeOptions:: 893 Sets default options for merging into branch <name>. The syntax and 894 supported options are the same as those of linkgit:git-merge[1], but 895 option values containing whitespace characters are currently not 896 supported. 897 898branch.<name>.rebase:: 899 When true, rebase the branch <name> on top of the fetched branch, 900 instead of merging the default branch from the default remote when 901 "git pull" is run. See "pull.rebase" for doing this in a non 902 branch-specific manner. 903+ 904When preserve, also pass `--preserve-merges` along to 'git rebase' 905so that locally committed merge commits will not be flattened 906by running 'git pull'. 907+ 908When the value is `interactive`, the rebase is run in interactive mode. 909+ 910*NOTE*: this is a possibly dangerous operation; do *not* use 911it unless you understand the implications (see linkgit:git-rebase[1] 912for details). 913 914branch.<name>.description:: 915 Branch description, can be edited with 916 `git branch --edit-description`. Branch description is 917 automatically added in the format-patch cover letter or 918 request-pull summary. 919 920browser.<tool>.cmd:: 921 Specify the command to invoke the specified browser. The 922 specified command is evaluated in shell with the URLs passed 923 as arguments. (See linkgit:git-web{litdd}browse[1].) 924 925browser.<tool>.path:: 926 Override the path for the given tool that may be used to 927 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 928 working repository in gitweb (see linkgit:git-instaweb[1]). 929 930clean.requireForce:: 931 A boolean to make git-clean do nothing unless given -f, 932 -i or -n. Defaults to true. 933 934color.branch:: 935 A boolean to enable/disable color in the output of 936 linkgit:git-branch[1]. May be set to `always`, 937 `false` (or `never`) or `auto` (or `true`), in which case colors are used 938 only when the output is to a terminal. Defaults to false. 939 940color.branch.<slot>:: 941 Use customized color for branch coloration. `<slot>` is one of 942 `current` (the current branch), `local` (a local branch), 943 `remote` (a remote-tracking branch in refs/remotes/), 944 `upstream` (upstream tracking branch), `plain` (other 945 refs). 946 947color.diff:: 948 Whether to use ANSI escape sequences to add color to patches. 949 If this is set to `always`, linkgit:git-diff[1], 950 linkgit:git-log[1], and linkgit:git-show[1] will use color 951 for all patches. If it is set to `true` or `auto`, those 952 commands will only use color when output is to the terminal. 953 Defaults to false. 954+ 955This does not affect linkgit:git-format-patch[1] or the 956'git-diff-{asterisk}' plumbing commands. Can be overridden on the 957command line with the `--color[=<when>]` option. 958 959color.diff.<slot>:: 960 Use customized color for diff colorization. `<slot>` specifies 961 which part of the patch to use the specified color, and is one 962 of `context` (context text - `plain` is a historical synonym), 963 `meta` (metainformation), `frag` 964 (hunk header), 'func' (function in hunk header), `old` (removed lines), 965 `new` (added lines), `commit` (commit headers), or `whitespace` 966 (highlighting whitespace errors). 967 968color.decorate.<slot>:: 969 Use customized color for 'git log --decorate' output. `<slot>` is one 970 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 971 branches, remote-tracking branches, tags, stash and HEAD, respectively. 972 973color.grep:: 974 When set to `always`, always highlight matches. When `false` (or 975 `never`), never. When set to `true` or `auto`, use color only 976 when the output is written to the terminal. Defaults to `false`. 977 978color.grep.<slot>:: 979 Use customized color for grep colorization. `<slot>` specifies which 980 part of the line to use the specified color, and is one of 981+ 982-- 983`context`;; 984 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 985`filename`;; 986 filename prefix (when not using `-h`) 987`function`;; 988 function name lines (when using `-p`) 989`linenumber`;; 990 line number prefix (when using `-n`) 991`match`;; 992 matching text (same as setting `matchContext` and `matchSelected`) 993`matchContext`;; 994 matching text in context lines 995`matchSelected`;; 996 matching text in selected lines 997`selected`;; 998 non-matching text in selected lines 999`separator`;;1000 separators between fields on a line (`:`, `-`, and `=`)1001 and between hunks (`--`)1002--10031004color.interactive::1005 When set to `always`, always use colors for interactive prompts1006 and displays (such as those used by "git-add --interactive" and1007 "git-clean --interactive"). When false (or `never`), never.1008 When set to `true` or `auto`, use colors only when the output is1009 to the terminal. Defaults to false.10101011color.interactive.<slot>::1012 Use customized color for 'git add --interactive' and 'git clean1013 --interactive' output. `<slot>` may be `prompt`, `header`, `help`1014 or `error`, for four distinct types of normal output from1015 interactive commands.10161017color.pager::1018 A boolean to enable/disable colored output when the pager is in1019 use (default is true).10201021color.showBranch::1022 A boolean to enable/disable color in the output of1023 linkgit:git-show-branch[1]. May be set to `always`,1024 `false` (or `never`) or `auto` (or `true`), in which case colors are used1025 only when the output is to a terminal. Defaults to false.10261027color.status::1028 A boolean to enable/disable color in the output of1029 linkgit:git-status[1]. May be set to `always`,1030 `false` (or `never`) or `auto` (or `true`), in which case colors are used1031 only when the output is to a terminal. Defaults to false.10321033color.status.<slot>::1034 Use customized color for status colorization. `<slot>` is1035 one of `header` (the header text of the status message),1036 `added` or `updated` (files which are added but not committed),1037 `changed` (files which are changed but not added in the index),1038 `untracked` (files which are not tracked by Git),1039 `branch` (the current branch),1040 `nobranch` (the color the 'no branch' warning is shown in, defaulting1041 to red), or1042 `unmerged` (files which have unmerged changes).10431044color.ui::1045 This variable determines the default value for variables such1046 as `color.diff` and `color.grep` that control the use of color1047 per command family. Its scope will expand as more commands learn1048 configuration to set a default for the `--color` option. Set it1049 to `false` or `never` if you prefer Git commands not to use1050 color unless enabled explicitly with some other configuration1051 or the `--color` option. Set it to `always` if you want all1052 output not intended for machine consumption to use color, to1053 `true` or `auto` (this is the default since Git 1.8.4) if you1054 want such output to use color when written to the terminal.10551056column.ui::1057 Specify whether supported commands should output in columns.1058 This variable consists of a list of tokens separated by spaces1059 or commas:1060+1061These options control when the feature should be enabled1062(defaults to 'never'):1063+1064--1065`always`;;1066 always show in columns1067`never`;;1068 never show in columns1069`auto`;;1070 show in columns if the output is to the terminal1071--1072+1073These options control layout (defaults to 'column'). Setting any1074of these implies 'always' if none of 'always', 'never', or 'auto' are1075specified.1076+1077--1078`column`;;1079 fill columns before rows1080`row`;;1081 fill rows before columns1082`plain`;;1083 show in one column1084--1085+1086Finally, these options can be combined with a layout option (defaults1087to 'nodense'):1088+1089--1090`dense`;;1091 make unequal size columns to utilize more space1092`nodense`;;1093 make equal size columns1094--10951096column.branch::1097 Specify whether to output branch listing in `git branch` in columns.1098 See `column.ui` for details.10991100column.clean::1101 Specify the layout when list items in `git clean -i`, which always1102 shows files and directories in columns. See `column.ui` for details.11031104column.status::1105 Specify whether to output untracked files in `git status` in columns.1106 See `column.ui` for details.11071108column.tag::1109 Specify whether to output tag listing in `git tag` in columns.1110 See `column.ui` for details.11111112commit.cleanup::1113 This setting overrides the default of the `--cleanup` option in1114 `git commit`. See linkgit:git-commit[1] for details. Changing the1115 default can be useful when you always want to keep lines that begin1116 with comment character `#` in your log message, in which case you1117 would do `git config commit.cleanup whitespace` (note that you will1118 have to remove the help lines that begin with `#` in the commit log1119 template yourself, if you do this).11201121commit.gpgSign::11221123 A boolean to specify whether all commits should be GPG signed.1124 Use of this option when doing operations such as rebase can1125 result in a large number of commits being signed. It may be1126 convenient to use an agent to avoid typing your GPG passphrase1127 several times.11281129commit.status::1130 A boolean to enable/disable inclusion of status information in the1131 commit message template when using an editor to prepare the commit1132 message. Defaults to true.11331134commit.template::1135 Specify the pathname of a file to use as the template for1136 new commit messages.11371138credential.helper::1139 Specify an external helper to be called when a username or1140 password credential is needed; the helper may consult external1141 storage to avoid prompting the user for the credentials. Note1142 that multiple helpers may be defined. See linkgit:gitcredentials[7]1143 for details.11441145credential.useHttpPath::1146 When acquiring credentials, consider the "path" component of an http1147 or https URL to be important. Defaults to false. See1148 linkgit:gitcredentials[7] for more information.11491150credential.username::1151 If no username is set for a network authentication, use this username1152 by default. See credential.<context>.* below, and1153 linkgit:gitcredentials[7].11541155credential.<url>.*::1156 Any of the credential.* options above can be applied selectively to1157 some credentials. For example "credential.https://example.com.username"1158 would set the default username only for https connections to1159 example.com. See linkgit:gitcredentials[7] for details on how URLs are1160 matched.11611162credentialCache.ignoreSIGHUP::1163 Tell git-credential-cache--daemon to ignore SIGHUP, instead of quitting.11641165include::diff-config.txt[]11661167difftool.<tool>.path::1168 Override the path for the given tool. This is useful in case1169 your tool is not in the PATH.11701171difftool.<tool>.cmd::1172 Specify the command to invoke the specified diff tool.1173 The specified command is evaluated in shell with the following1174 variables available: 'LOCAL' is set to the name of the temporary1175 file containing the contents of the diff pre-image and 'REMOTE'1176 is set to the name of the temporary file containing the contents1177 of the diff post-image.11781179difftool.prompt::1180 Prompt before each invocation of the diff tool.11811182fetch.recurseSubmodules::1183 This option can be either set to a boolean value or to 'on-demand'.1184 Setting it to a boolean changes the behavior of fetch and pull to1185 unconditionally recurse into submodules when set to true or to not1186 recurse at all when set to false. When set to 'on-demand' (the default1187 value), fetch and pull will only recurse into a populated submodule1188 when its superproject retrieves a commit that updates the submodule's1189 reference.11901191fetch.fsckObjects::1192 If it is set to true, git-fetch-pack will check all fetched1193 objects. It will abort in the case of a malformed object or a1194 broken link. The result of an abort are only dangling objects.1195 Defaults to false. If not set, the value of `transfer.fsckObjects`1196 is used instead.11971198fetch.unpackLimit::1199 If the number of objects fetched over the Git native1200 transfer is below this1201 limit, then the objects will be unpacked into loose object1202 files. However if the number of received objects equals or1203 exceeds this limit then the received pack will be stored as1204 a pack, after adding any missing delta bases. Storing the1205 pack from a push can make the push operation complete faster,1206 especially on slow filesystems. If not set, the value of1207 `transfer.unpackLimit` is used instead.12081209fetch.prune::1210 If true, fetch will automatically behave as if the `--prune`1211 option was given on the command line. See also `remote.<name>.prune`.12121213format.attach::1214 Enable multipart/mixed attachments as the default for1215 'format-patch'. The value can also be a double quoted string1216 which will enable attachments as the default and set the1217 value as the boundary. See the --attach option in1218 linkgit:git-format-patch[1].12191220format.numbered::1221 A boolean which can enable or disable sequence numbers in patch1222 subjects. It defaults to "auto" which enables it only if there1223 is more than one patch. It can be enabled or disabled for all1224 messages by setting it to "true" or "false". See --numbered1225 option in linkgit:git-format-patch[1].12261227format.headers::1228 Additional email headers to include in a patch to be submitted1229 by mail. See linkgit:git-format-patch[1].12301231format.to::1232format.cc::1233 Additional recipients to include in a patch to be submitted1234 by mail. See the --to and --cc options in1235 linkgit:git-format-patch[1].12361237format.subjectPrefix::1238 The default for format-patch is to output files with the '[PATCH]'1239 subject prefix. Use this variable to change that prefix.12401241format.signature::1242 The default for format-patch is to output a signature containing1243 the Git version number. Use this variable to change that default.1244 Set this variable to the empty string ("") to suppress1245 signature generation.12461247format.signatureFile::1248 Works just like format.signature except the contents of the1249 file specified by this variable will be used as the signature.12501251format.suffix::1252 The default for format-patch is to output files with the suffix1253 `.patch`. Use this variable to change that suffix (make sure to1254 include the dot if you want it).12551256format.pretty::1257 The default pretty format for log/show/whatchanged command,1258 See linkgit:git-log[1], linkgit:git-show[1],1259 linkgit:git-whatchanged[1].12601261format.thread::1262 The default threading style for 'git format-patch'. Can be1263 a boolean value, or `shallow` or `deep`. `shallow` threading1264 makes every mail a reply to the head of the series,1265 where the head is chosen from the cover letter, the1266 `--in-reply-to`, and the first patch mail, in this order.1267 `deep` threading makes every mail a reply to the previous one.1268 A true boolean value is the same as `shallow`, and a false1269 value disables threading.12701271format.signOff::1272 A boolean value which lets you enable the `-s/--signoff` option of1273 format-patch by default. *Note:* Adding the Signed-off-by: line to a1274 patch should be a conscious act and means that you certify you have1275 the rights to submit this work under the same open source license.1276 Please see the 'SubmittingPatches' document for further discussion.12771278format.coverLetter::1279 A boolean that controls whether to generate a cover-letter when1280 format-patch is invoked, but in addition can be set to "auto", to1281 generate a cover-letter only when there's more than one patch.12821283format.outputDirectory::1284 Set a custom directory to store the resulting files instead of the1285 current working directory.12861287filter.<driver>.clean::1288 The command which is used to convert the content of a worktree1289 file to a blob upon checkin. See linkgit:gitattributes[5] for1290 details.12911292filter.<driver>.smudge::1293 The command which is used to convert the content of a blob1294 object to a worktree file upon checkout. See1295 linkgit:gitattributes[5] for details.12961297fsck.<msg-id>::1298 Allows overriding the message type (error, warn or ignore) of a1299 specific message ID such as `missingEmail`.1300+1301For convenience, fsck prefixes the error/warning with the message ID,1302e.g. "missingEmail: invalid author/committer line - missing email" means1303that setting `fsck.missingEmail = ignore` will hide that issue.1304+1305This feature is intended to support working with legacy repositories1306which cannot be repaired without disruptive changes.13071308fsck.skipList::1309 The path to a sorted list of object names (i.e. one SHA-1 per1310 line) that are known to be broken in a non-fatal way and should1311 be ignored. This feature is useful when an established project1312 should be accepted despite early commits containing errors that1313 can be safely ignored such as invalid committer email addresses.1314 Note: corrupt objects cannot be skipped with this setting.13151316gc.aggressiveDepth::1317 The depth parameter used in the delta compression1318 algorithm used by 'git gc --aggressive'. This defaults1319 to 250.13201321gc.aggressiveWindow::1322 The window size parameter used in the delta compression1323 algorithm used by 'git gc --aggressive'. This defaults1324 to 250.13251326gc.auto::1327 When there are approximately more than this many loose1328 objects in the repository, `git gc --auto` will pack them.1329 Some Porcelain commands use this command to perform a1330 light-weight garbage collection from time to time. The1331 default value is 6700. Setting this to 0 disables it.13321333gc.autoPackLimit::1334 When there are more than this many packs that are not1335 marked with `*.keep` file in the repository, `git gc1336 --auto` consolidates them into one larger pack. The1337 default value is 50. Setting this to 0 disables it.13381339gc.autoDetach::1340 Make `git gc --auto` return immediately and run in background1341 if the system supports it. Default is true.13421343gc.packRefs::1344 Running `git pack-refs` in a repository renders it1345 unclonable by Git versions prior to 1.5.1.2 over dumb1346 transports such as HTTP. This variable determines whether1347 'git gc' runs `git pack-refs`. This can be set to `notbare`1348 to enable it within all non-bare repos or it can be set to a1349 boolean value. The default is `true`.13501351gc.pruneExpire::1352 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1353 Override the grace period with this config variable. The value1354 "now" may be used to disable this grace period and always prune1355 unreachable objects immediately, or "never" may be used to1356 suppress pruning.13571358gc.worktreePruneExpire::1359 When 'git gc' is run, it calls1360 'git worktree prune --expire 3.months.ago'.1361 This config variable can be used to set a different grace1362 period. The value "now" may be used to disable the grace1363 period and prune $GIT_DIR/worktrees immediately, or "never"1364 may be used to suppress pruning.13651366gc.reflogExpire::1367gc.<pattern>.reflogExpire::1368 'git reflog expire' removes reflog entries older than1369 this time; defaults to 90 days. The value "now" expires all1370 entries immediately, and "never" suppresses expiration1371 altogether. With "<pattern>" (e.g.1372 "refs/stash") in the middle the setting applies only to1373 the refs that match the <pattern>.13741375gc.reflogExpireUnreachable::1376gc.<pattern>.reflogExpireUnreachable::1377 'git reflog expire' removes reflog entries older than1378 this time and are not reachable from the current tip;1379 defaults to 30 days. The value "now" expires all entries1380 immediately, and "never" suppresses expiration altogether.1381 With "<pattern>" (e.g. "refs/stash")1382 in the middle, the setting applies only to the refs that1383 match the <pattern>.13841385gc.rerereResolved::1386 Records of conflicted merge you resolved earlier are1387 kept for this many days when 'git rerere gc' is run.1388 The default is 60 days. See linkgit:git-rerere[1].13891390gc.rerereUnresolved::1391 Records of conflicted merge you have not resolved are1392 kept for this many days when 'git rerere gc' is run.1393 The default is 15 days. See linkgit:git-rerere[1].13941395gitcvs.commitMsgAnnotation::1396 Append this string to each commit message. Set to empty string1397 to disable this feature. Defaults to "via git-CVS emulator".13981399gitcvs.enabled::1400 Whether the CVS server interface is enabled for this repository.1401 See linkgit:git-cvsserver[1].14021403gitcvs.logFile::1404 Path to a log file where the CVS server interface well... logs1405 various stuff. See linkgit:git-cvsserver[1].14061407gitcvs.usecrlfattr::1408 If true, the server will look up the end-of-line conversion1409 attributes for files to determine the '-k' modes to use. If1410 the attributes force Git to treat a file as text,1411 the '-k' mode will be left blank so CVS clients will1412 treat it as text. If they suppress text conversion, the file1413 will be set with '-kb' mode, which suppresses any newline munging1414 the client might otherwise do. If the attributes do not allow1415 the file type to be determined, then 'gitcvs.allBinary' is1416 used. See linkgit:gitattributes[5].14171418gitcvs.allBinary::1419 This is used if 'gitcvs.usecrlfattr' does not resolve1420 the correct '-kb' mode to use. If true, all1421 unresolved files are sent to the client in1422 mode '-kb'. This causes the client to treat them1423 as binary files, which suppresses any newline munging it1424 otherwise might do. Alternatively, if it is set to "guess",1425 then the contents of the file are examined to decide if1426 it is binary, similar to 'core.autocrlf'.14271428gitcvs.dbName::1429 Database used by git-cvsserver to cache revision information1430 derived from the Git repository. The exact meaning depends on the1431 used database driver, for SQLite (which is the default driver) this1432 is a filename. Supports variable substitution (see1433 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1434 Default: '%Ggitcvs.%m.sqlite'14351436gitcvs.dbDriver::1437 Used Perl DBI driver. You can specify any available driver1438 for this here, but it might not work. git-cvsserver is tested1439 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1440 reported *not* to work with 'DBD::mysql'. Experimental feature.1441 May not contain double colons (`:`). Default: 'SQLite'.1442 See linkgit:git-cvsserver[1].14431444gitcvs.dbUser, gitcvs.dbPass::1445 Database user and password. Only useful if setting 'gitcvs.dbDriver',1446 since SQLite has no concept of database users and/or passwords.1447 'gitcvs.dbUser' supports variable substitution (see1448 linkgit:git-cvsserver[1] for details).14491450gitcvs.dbTableNamePrefix::1451 Database table name prefix. Prepended to the names of any1452 database tables used, allowing a single database to be used1453 for several repositories. Supports variable substitution (see1454 linkgit:git-cvsserver[1] for details). Any non-alphabetic1455 characters will be replaced with underscores.14561457All gitcvs variables except for 'gitcvs.usecrlfattr' and1458'gitcvs.allBinary' can also be specified as1459'gitcvs.<access_method>.<varname>' (where 'access_method'1460is one of "ext" and "pserver") to make them apply only for the given1461access method.14621463gitweb.category::1464gitweb.description::1465gitweb.owner::1466gitweb.url::1467 See linkgit:gitweb[1] for description.14681469gitweb.avatar::1470gitweb.blame::1471gitweb.grep::1472gitweb.highlight::1473gitweb.patches::1474gitweb.pickaxe::1475gitweb.remote_heads::1476gitweb.showSizes::1477gitweb.snapshot::1478 See linkgit:gitweb.conf[5] for description.14791480grep.lineNumber::1481 If set to true, enable '-n' option by default.14821483grep.patternType::1484 Set the default matching behavior. Using a value of 'basic', 'extended',1485 'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',1486 '--fixed-strings', or '--perl-regexp' option accordingly, while the1487 value 'default' will return to the default matching behavior.14881489grep.extendedRegexp::1490 If set to true, enable '--extended-regexp' option by default. This1491 option is ignored when the 'grep.patternType' option is set to a value1492 other than 'default'.14931494grep.threads::1495 Number of grep worker threads to use.1496 See `grep.threads` in linkgit:git-grep[1] for more information.14971498grep.fallbackToNoIndex::1499 If set to true, fall back to git grep --no-index if git grep1500 is executed outside of a git repository. Defaults to false.15011502gpg.program::1503 Use this custom program instead of "gpg" found on $PATH when1504 making or verifying a PGP signature. The program must support the1505 same command-line interface as GPG, namely, to verify a detached1506 signature, "gpg --verify $file - <$signature" is run, and the1507 program is expected to signal a good signature by exiting with1508 code 0, and to generate an ASCII-armored detached signature, the1509 standard input of "gpg -bsau $key" is fed with the contents to be1510 signed, and the program is expected to send the result to its1511 standard output.15121513gui.commitMsgWidth::1514 Defines how wide the commit message window is in the1515 linkgit:git-gui[1]. "75" is the default.15161517gui.diffContext::1518 Specifies how many context lines should be used in calls to diff1519 made by the linkgit:git-gui[1]. The default is "5".15201521gui.displayUntracked::1522 Determines if linkgit::git-gui[1] shows untracked files1523 in the file list. The default is "true".15241525gui.encoding::1526 Specifies the default encoding to use for displaying of1527 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1528 It can be overridden by setting the 'encoding' attribute1529 for relevant files (see linkgit:gitattributes[5]).1530 If this option is not set, the tools default to the1531 locale encoding.15321533gui.matchTrackingBranch::1534 Determines if new branches created with linkgit:git-gui[1] should1535 default to tracking remote branches with matching names or1536 not. Default: "false".15371538gui.newBranchTemplate::1539 Is used as suggested name when creating new branches using the1540 linkgit:git-gui[1].15411542gui.pruneDuringFetch::1543 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1544 performing a fetch. The default value is "false".15451546gui.trustmtime::1547 Determines if linkgit:git-gui[1] should trust the file modification1548 timestamp or not. By default the timestamps are not trusted.15491550gui.spellingDictionary::1551 Specifies the dictionary used for spell checking commit messages in1552 the linkgit:git-gui[1]. When set to "none" spell checking is turned1553 off.15541555gui.fastCopyBlame::1556 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1557 location detection. It makes blame significantly faster on huge1558 repositories at the expense of less thorough copy detection.15591560gui.copyBlameThreshold::1561 Specifies the threshold to use in 'git gui blame' original location1562 detection, measured in alphanumeric characters. See the1563 linkgit:git-blame[1] manual for more information on copy detection.15641565gui.blamehistoryctx::1566 Specifies the radius of history context in days to show in1567 linkgit:gitk[1] for the selected commit, when the `Show History1568 Context` menu item is invoked from 'git gui blame'. If this1569 variable is set to zero, the whole history is shown.15701571guitool.<name>.cmd::1572 Specifies the shell command line to execute when the corresponding item1573 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1574 mandatory for every tool. The command is executed from the root of1575 the working directory, and in the environment it receives the name of1576 the tool as 'GIT_GUITOOL', the name of the currently selected file as1577 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1578 the head is detached, 'CUR_BRANCH' is empty).15791580guitool.<name>.needsFile::1581 Run the tool only if a diff is selected in the GUI. It guarantees1582 that 'FILENAME' is not empty.15831584guitool.<name>.noConsole::1585 Run the command silently, without creating a window to display its1586 output.15871588guitool.<name>.noRescan::1589 Don't rescan the working directory for changes after the tool1590 finishes execution.15911592guitool.<name>.confirm::1593 Show a confirmation dialog before actually running the tool.15941595guitool.<name>.argPrompt::1596 Request a string argument from the user, and pass it to the tool1597 through the 'ARGS' environment variable. Since requesting an1598 argument implies confirmation, the 'confirm' option has no effect1599 if this is enabled. If the option is set to 'true', 'yes', or '1',1600 the dialog uses a built-in generic prompt; otherwise the exact1601 value of the variable is used.16021603guitool.<name>.revPrompt::1604 Request a single valid revision from the user, and set the1605 'REVISION' environment variable. In other aspects this option1606 is similar to 'argPrompt', and can be used together with it.16071608guitool.<name>.revUnmerged::1609 Show only unmerged branches in the 'revPrompt' subdialog.1610 This is useful for tools similar to merge or rebase, but not1611 for things like checkout or reset.16121613guitool.<name>.title::1614 Specifies the title to use for the prompt dialog. The default1615 is the tool name.16161617guitool.<name>.prompt::1618 Specifies the general prompt string to display at the top of1619 the dialog, before subsections for 'argPrompt' and 'revPrompt'.1620 The default value includes the actual command.16211622help.browser::1623 Specify the browser that will be used to display help in the1624 'web' format. See linkgit:git-help[1].16251626help.format::1627 Override the default help format used by linkgit:git-help[1].1628 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1629 the default. 'web' and 'html' are the same.16301631help.autoCorrect::1632 Automatically correct and execute mistyped commands after1633 waiting for the given number of deciseconds (0.1 sec). If more1634 than one command can be deduced from the entered text, nothing1635 will be executed. If the value of this option is negative,1636 the corrected command will be executed immediately. If the1637 value is 0 - the command will be just shown but not executed.1638 This is the default.16391640help.htmlPath::1641 Specify the path where the HTML documentation resides. File system paths1642 and URLs are supported. HTML pages will be prefixed with this path when1643 help is displayed in the 'web' format. This defaults to the documentation1644 path of your Git installation.16451646http.proxy::1647 Override the HTTP proxy, normally configured using the 'http_proxy',1648 'https_proxy', and 'all_proxy' environment variables (see `curl(1)`). In1649 addition to the syntax understood by curl, it is possible to specify a1650 proxy string with a user name but no password, in which case git will1651 attempt to acquire one in the same way it does for other credentials. See1652 linkgit:gitcredentials[7] for more information. The syntax thus is1653 '[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden1654 on a per-remote basis; see remote.<name>.proxy16551656http.proxyAuthMethod::1657 Set the method with which to authenticate against the HTTP proxy. This1658 only takes effect if the configured proxy string contains a user name part1659 (i.e. is of the form 'user@host' or 'user@host:port'). This can be1660 overridden on a per-remote basis; see `remote.<name>.proxyAuthMethod`.1661 Both can be overridden by the 'GIT_HTTP_PROXY_AUTHMETHOD' environment1662 variable. Possible values are:1663+1664--1665* `anyauth` - Automatically pick a suitable authentication method. It is1666 assumed that the proxy answers an unauthenticated request with a 4071667 status code and one or more Proxy-authenticate headers with supported1668 authentication methods. This is the default.1669* `basic` - HTTP Basic authentication1670* `digest` - HTTP Digest authentication; this prevents the password from being1671 transmitted to the proxy in clear text1672* `negotiate` - GSS-Negotiate authentication (compare the --negotiate option1673 of `curl(1)`)1674* `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`)1675--16761677http.emptyAuth::1678 Attempt authentication without seeking a username or password. This1679 can be used to attempt GSS-Negotiate authentication without specifying1680 a username in the URL, as libcurl normally requires a username for1681 authentication.16821683http.extraHeader::1684 Pass an additional HTTP header when communicating with a server. If1685 more than one such entry exists, all of them are added as extra1686 headers. To allow overriding the settings inherited from the system1687 config, an empty value will reset the extra headers to the empty list.16881689http.cookieFile::1690 The pathname of a file containing previously stored cookie lines,1691 which should be used1692 in the Git http session, if they match the server. The file format1693 of the file to read cookies from should be plain HTTP headers or1694 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1695 NOTE that the file specified with http.cookieFile is used only as1696 input unless http.saveCookies is set.16971698http.saveCookies::1699 If set, store cookies received during requests to the file specified by1700 http.cookieFile. Has no effect if http.cookieFile is unset.17011702http.sslVersion::1703 The SSL version to use when negotiating an SSL connection, if you1704 want to force the default. The available and default version1705 depend on whether libcurl was built against NSS or OpenSSL and the1706 particular configuration of the crypto library in use. Internally1707 this sets the 'CURLOPT_SSL_VERSION' option; see the libcurl1708 documentation for more details on the format of this option and1709 for the ssl version supported. Actually the possible values of1710 this option are:17111712 - sslv21713 - sslv31714 - tlsv11715 - tlsv1.01716 - tlsv1.11717 - tlsv1.217181719+1720Can be overridden by the 'GIT_SSL_VERSION' environment variable.1721To force git to use libcurl's default ssl version and ignore any1722explicit http.sslversion option, set 'GIT_SSL_VERSION' to the1723empty string.17241725http.sslCipherList::1726 A list of SSL ciphers to use when negotiating an SSL connection.1727 The available ciphers depend on whether libcurl was built against1728 NSS or OpenSSL and the particular configuration of the crypto1729 library in use. Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'1730 option; see the libcurl documentation for more details on the format1731 of this list.1732+1733Can be overridden by the 'GIT_SSL_CIPHER_LIST' environment variable.1734To force git to use libcurl's default cipher list and ignore any1735explicit http.sslCipherList option, set 'GIT_SSL_CIPHER_LIST' to the1736empty string.17371738http.sslVerify::1739 Whether to verify the SSL certificate when fetching or pushing1740 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1741 variable.17421743http.sslCert::1744 File containing the SSL certificate when fetching or pushing1745 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1746 variable.17471748http.sslKey::1749 File containing the SSL private key when fetching or pushing1750 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1751 variable.17521753http.sslCertPasswordProtected::1754 Enable Git's password prompt for the SSL certificate. Otherwise1755 OpenSSL will prompt the user, possibly many times, if the1756 certificate or private key is encrypted. Can be overridden by the1757 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.17581759http.sslCAInfo::1760 File containing the certificates to verify the peer with when1761 fetching or pushing over HTTPS. Can be overridden by the1762 'GIT_SSL_CAINFO' environment variable.17631764http.sslCAPath::1765 Path containing files with the CA certificates to verify the peer1766 with when fetching or pushing over HTTPS. Can be overridden1767 by the 'GIT_SSL_CAPATH' environment variable.17681769http.pinnedpubkey::1770 Public key of the https service. It may either be the filename of1771 a PEM or DER encoded public key file or a string starting with1772 'sha256//' followed by the base64 encoded sha256 hash of the1773 public key. See also libcurl 'CURLOPT_PINNEDPUBLICKEY'. git will1774 exit with an error if this option is set but not supported by1775 cURL.17761777http.sslTry::1778 Attempt to use AUTH SSL/TLS and encrypted data transfers1779 when connecting via regular FTP protocol. This might be needed1780 if the FTP server requires it for security reasons or you wish1781 to connect securely whenever remote FTP server supports it.1782 Default is false since it might trigger certificate verification1783 errors on misconfigured servers.17841785http.maxRequests::1786 How many HTTP requests to launch in parallel. Can be overridden1787 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.17881789http.minSessions::1790 The number of curl sessions (counted across slots) to be kept across1791 requests. They will not be ended with curl_easy_cleanup() until1792 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1793 value will be capped at 1. Defaults to 1.17941795http.postBuffer::1796 Maximum size in bytes of the buffer used by smart HTTP1797 transports when POSTing data to the remote system.1798 For requests larger than this buffer size, HTTP/1.1 and1799 Transfer-Encoding: chunked is used to avoid creating a1800 massive pack file locally. Default is 1 MiB, which is1801 sufficient for most requests.18021803http.lowSpeedLimit, http.lowSpeedTime::1804 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1805 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1806 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1807 'GIT_HTTP_LOW_SPEED_TIME' environment variables.18081809http.noEPSV::1810 A boolean which disables using of EPSV ftp command by curl.1811 This can helpful with some "poor" ftp servers which don't1812 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1813 environment variable. Default is false (curl will use EPSV).18141815http.userAgent::1816 The HTTP USER_AGENT string presented to an HTTP server. The default1817 value represents the version of the client Git such as git/1.7.1.1818 This option allows you to override this value to a more common value1819 such as Mozilla/4.0. This may be necessary, for instance, if1820 connecting through a firewall that restricts HTTP connections to a set1821 of common USER_AGENT strings (but not including those like git/1.7.1).1822 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.18231824http.<url>.*::1825 Any of the http.* options above can be applied selectively to some URLs.1826 For a config key to match a URL, each element of the config key is1827 compared to that of the URL, in the following order:1828+1829--1830. Scheme (e.g., `https` in `https://example.com/`). This field1831 must match exactly between the config key and the URL.18321833. Host/domain name (e.g., `example.com` in `https://example.com/`).1834 This field must match exactly between the config key and the URL.18351836. Port number (e.g., `8080` in `http://example.com:8080/`).1837 This field must match exactly between the config key and the URL.1838 Omitted port numbers are automatically converted to the correct1839 default for the scheme before matching.18401841. Path (e.g., `repo.git` in `https://example.com/repo.git`). The1842 path field of the config key must match the path field of the URL1843 either exactly or as a prefix of slash-delimited path elements. This means1844 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only1845 match on a slash (`/`) boundary. Longer matches take precedence (so a config1846 key with path `foo/bar` is a better match to URL path `foo/bar` than a config1847 key with just path `foo/`).18481849. User name (e.g., `user` in `https://user@example.com/repo.git`). If1850 the config key has a user name it must match the user name in the1851 URL exactly. If the config key does not have a user name, that1852 config key will match a URL with any user name (including none),1853 but at a lower precedence than a config key with a user name.1854--1855+1856The list above is ordered by decreasing precedence; a URL that matches1857a config key's path is preferred to one that matches its user name. For example,1858if the URL is `https://user@example.com/foo/bar` a config key match of1859`https://example.com/foo` will be preferred over a config key match of1860`https://user@example.com`.1861+1862All URLs are normalized before attempting any matching (the password part,1863if embedded in the URL, is always ignored for matching purposes) so that1864equivalent URLs that are simply spelled differently will match properly.1865Environment variable settings always override any matches. The URLs that are1866matched against are those given directly to Git commands. This means any URLs1867visited as a result of a redirection do not participate in matching.18681869i18n.commitEncoding::1870 Character encoding the commit messages are stored in; Git itself1871 does not care per se, but this information is necessary e.g. when1872 importing commits from emails or in the gitk graphical history1873 browser (and possibly at other places in the future or in other1874 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.18751876i18n.logOutputEncoding::1877 Character encoding the commit messages are converted to when1878 running 'git log' and friends.18791880imap::1881 The configuration variables in the 'imap' section are described1882 in linkgit:git-imap-send[1].18831884index.version::1885 Specify the version with which new index files should be1886 initialized. This does not affect existing repositories.18871888init.templateDir::1889 Specify the directory from which templates will be copied.1890 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)18911892instaweb.browser::1893 Specify the program that will be used to browse your working1894 repository in gitweb. See linkgit:git-instaweb[1].18951896instaweb.httpd::1897 The HTTP daemon command-line to start gitweb on your working1898 repository. See linkgit:git-instaweb[1].18991900instaweb.local::1901 If true the web server started by linkgit:git-instaweb[1] will1902 be bound to the local IP (127.0.0.1).19031904instaweb.modulePath::1905 The default module path for linkgit:git-instaweb[1] to use1906 instead of /usr/lib/apache2/modules. Only used if httpd1907 is Apache.19081909instaweb.port::1910 The port number to bind the gitweb httpd to. See1911 linkgit:git-instaweb[1].19121913interactive.singleKey::1914 In interactive commands, allow the user to provide one-letter1915 input with a single key (i.e., without hitting enter).1916 Currently this is used by the `--patch` mode of1917 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1918 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1919 setting is silently ignored if portable keystroke input1920 is not available; requires the Perl module Term::ReadKey.19211922interactive.diffFilter::1923 When an interactive command (such as `git add --patch`) shows1924 a colorized diff, git will pipe the diff through the shell1925 command defined by this configuration variable. The command may1926 mark up the diff further for human consumption, provided that it1927 retains a one-to-one correspondence with the lines in the1928 original diff. Defaults to disabled (no filtering).19291930log.abbrevCommit::1931 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1932 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may1933 override this option with `--no-abbrev-commit`.19341935log.date::1936 Set the default date-time mode for the 'log' command.1937 Setting a value for log.date is similar to using 'git log''s1938 `--date` option. See linkgit:git-log[1] for details.19391940log.decorate::1941 Print out the ref names of any commits that are shown by the log1942 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1943 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1944 specified, the full ref name (including prefix) will be printed.1945 This is the same as the log commands '--decorate' option.19461947log.follow::1948 If `true`, `git log` will act as if the `--follow` option was used when1949 a single <path> is given. This has the same limitations as `--follow`,1950 i.e. it cannot be used to follow multiple files and does not work well1951 on non-linear history.19521953log.showRoot::1954 If true, the initial commit will be shown as a big creation event.1955 This is equivalent to a diff against an empty tree.1956 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1957 normally hide the root commit will now show it. True by default.19581959log.mailmap::1960 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1961 linkgit:git-whatchanged[1] assume `--use-mailmap`.19621963mailinfo.scissors::1964 If true, makes linkgit:git-mailinfo[1] (and therefore1965 linkgit:git-am[1]) act by default as if the --scissors option1966 was provided on the command-line. When active, this features1967 removes everything from the message body before a scissors1968 line (i.e. consisting mainly of ">8", "8<" and "-").19691970mailmap.file::1971 The location of an augmenting mailmap file. The default1972 mailmap, located in the root of the repository, is loaded1973 first, then the mailmap file pointed to by this variable.1974 The location of the mailmap file may be in a repository1975 subdirectory, or somewhere outside of the repository itself.1976 See linkgit:git-shortlog[1] and linkgit:git-blame[1].19771978mailmap.blob::1979 Like `mailmap.file`, but consider the value as a reference to a1980 blob in the repository. If both `mailmap.file` and1981 `mailmap.blob` are given, both are parsed, with entries from1982 `mailmap.file` taking precedence. In a bare repository, this1983 defaults to `HEAD:.mailmap`. In a non-bare repository, it1984 defaults to empty.19851986man.viewer::1987 Specify the programs that may be used to display help in the1988 'man' format. See linkgit:git-help[1].19891990man.<tool>.cmd::1991 Specify the command to invoke the specified man viewer. The1992 specified command is evaluated in shell with the man page1993 passed as argument. (See linkgit:git-help[1].)19941995man.<tool>.path::1996 Override the path for the given tool that may be used to1997 display help in the 'man' format. See linkgit:git-help[1].19981999include::merge-config.txt[]20002001mergetool.<tool>.path::2002 Override the path for the given tool. This is useful in case2003 your tool is not in the PATH.20042005mergetool.<tool>.cmd::2006 Specify the command to invoke the specified merge tool. The2007 specified command is evaluated in shell with the following2008 variables available: 'BASE' is the name of a temporary file2009 containing the common base of the files to be merged, if available;2010 'LOCAL' is the name of a temporary file containing the contents of2011 the file on the current branch; 'REMOTE' is the name of a temporary2012 file containing the contents of the file from the branch being2013 merged; 'MERGED' contains the name of the file to which the merge2014 tool should write the results of a successful merge.20152016mergetool.<tool>.trustExitCode::2017 For a custom merge command, specify whether the exit code of2018 the merge command can be used to determine whether the merge was2019 successful. If this is not set to true then the merge target file2020 timestamp is checked and the merge assumed to have been successful2021 if the file has been updated, otherwise the user is prompted to2022 indicate the success of the merge.20232024mergetool.meld.hasOutput::2025 Older versions of `meld` do not support the `--output` option.2026 Git will attempt to detect whether `meld` supports `--output`2027 by inspecting the output of `meld --help`. Configuring2028 `mergetool.meld.hasOutput` will make Git skip these checks and2029 use the configured value instead. Setting `mergetool.meld.hasOutput`2030 to `true` tells Git to unconditionally use the `--output` option,2031 and `false` avoids using `--output`.20322033mergetool.keepBackup::2034 After performing a merge, the original file with conflict markers2035 can be saved as a file with a `.orig` extension. If this variable2036 is set to `false` then this file is not preserved. Defaults to2037 `true` (i.e. keep the backup files).20382039mergetool.keepTemporaries::2040 When invoking a custom merge tool, Git uses a set of temporary2041 files to pass to the tool. If the tool returns an error and this2042 variable is set to `true`, then these temporary files will be2043 preserved, otherwise they will be removed after the tool has2044 exited. Defaults to `false`.20452046mergetool.writeToTemp::2047 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of2048 conflicting files in the worktree by default. Git will attempt2049 to use a temporary directory for these files when set `true`.2050 Defaults to `false`.20512052mergetool.prompt::2053 Prompt before each invocation of the merge resolution program.20542055notes.mergeStrategy::2056 Which merge strategy to choose by default when resolving notes2057 conflicts. Must be one of `manual`, `ours`, `theirs`, `union`, or2058 `cat_sort_uniq`. Defaults to `manual`. See "NOTES MERGE STRATEGIES"2059 section of linkgit:git-notes[1] for more information on each strategy.20602061notes.<name>.mergeStrategy::2062 Which merge strategy to choose when doing a notes merge into2063 refs/notes/<name>. This overrides the more general2064 "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES" section in2065 linkgit:git-notes[1] for more information on the available strategies.20662067notes.displayRef::2068 The (fully qualified) refname from which to show notes when2069 showing commit messages. The value of this variable can be set2070 to a glob, in which case notes from all matching refs will be2071 shown. You may also specify this configuration variable2072 several times. A warning will be issued for refs that do not2073 exist, but a glob that does not match any refs is silently2074 ignored.2075+2076This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`2077environment variable, which must be a colon separated list of refs or2078globs.2079+2080The effective value of "core.notesRef" (possibly overridden by2081GIT_NOTES_REF) is also implicitly added to the list of refs to be2082displayed.20832084notes.rewrite.<command>::2085 When rewriting commits with <command> (currently `amend` or2086 `rebase`) and this variable is set to `true`, Git2087 automatically copies your notes from the original to the2088 rewritten commit. Defaults to `true`, but see2089 "notes.rewriteRef" below.20902091notes.rewriteMode::2092 When copying notes during a rewrite (see the2093 "notes.rewrite.<command>" option), determines what to do if2094 the target commit already has a note. Must be one of2095 `overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`.2096 Defaults to `concatenate`.2097+2098This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`2099environment variable.21002101notes.rewriteRef::2102 When copying notes during a rewrite, specifies the (fully2103 qualified) ref whose notes should be copied. The ref may be a2104 glob, in which case notes in all matching refs will be copied.2105 You may also specify this configuration several times.2106+2107Does not have a default value; you must configure this variable to2108enable note rewriting. Set it to `refs/notes/commits` to enable2109rewriting for the default commit notes.2110+2111This setting can be overridden with the `GIT_NOTES_REWRITE_REF`2112environment variable, which must be a colon separated list of refs or2113globs.21142115pack.window::2116 The size of the window used by linkgit:git-pack-objects[1] when no2117 window size is given on the command line. Defaults to 10.21182119pack.depth::2120 The maximum delta depth used by linkgit:git-pack-objects[1] when no2121 maximum depth is given on the command line. Defaults to 50.21222123pack.windowMemory::2124 The maximum size of memory that is consumed by each thread2125 in linkgit:git-pack-objects[1] for pack window memory when2126 no limit is given on the command line. The value can be2127 suffixed with "k", "m", or "g". When left unconfigured (or2128 set explicitly to 0), there will be no limit.21292130pack.compression::2131 An integer -1..9, indicating the compression level for objects2132 in a pack file. -1 is the zlib default. 0 means no2133 compression, and 1..9 are various speed/size tradeoffs, 9 being2134 slowest. If not set, defaults to core.compression. If that is2135 not set, defaults to -1, the zlib default, which is "a default2136 compromise between speed and compression (currently equivalent2137 to level 6)."2138+2139Note that changing the compression level will not automatically recompress2140all existing objects. You can force recompression by passing the -F option2141to linkgit:git-repack[1].21422143pack.deltaCacheSize::2144 The maximum memory in bytes used for caching deltas in2145 linkgit:git-pack-objects[1] before writing them out to a pack.2146 This cache is used to speed up the writing object phase by not2147 having to recompute the final delta result once the best match2148 for all objects is found. Repacking large repositories on machines2149 which are tight with memory might be badly impacted by this though,2150 especially if this cache pushes the system into swapping.2151 A value of 0 means no limit. The smallest size of 1 byte may be2152 used to virtually disable this cache. Defaults to 256 MiB.21532154pack.deltaCacheLimit::2155 The maximum size of a delta, that is cached in2156 linkgit:git-pack-objects[1]. This cache is used to speed up the2157 writing object phase by not having to recompute the final delta2158 result once the best match for all objects is found. Defaults to 1000.21592160pack.threads::2161 Specifies the number of threads to spawn when searching for best2162 delta matches. This requires that linkgit:git-pack-objects[1]2163 be compiled with pthreads otherwise this option is ignored with a2164 warning. This is meant to reduce packing time on multiprocessor2165 machines. The required amount of memory for the delta search window2166 is however multiplied by the number of threads.2167 Specifying 0 will cause Git to auto-detect the number of CPU's2168 and set the number of threads accordingly.21692170pack.indexVersion::2171 Specify the default pack index version. Valid values are 1 for2172 legacy pack index used by Git versions prior to 1.5.2, and 2 for2173 the new pack index with capabilities for packs larger than 4 GB2174 as well as proper protection against the repacking of corrupted2175 packs. Version 2 is the default. Note that version 2 is enforced2176 and this config option ignored whenever the corresponding pack is2177 larger than 2 GB.2178+2179If you have an old Git that does not understand the version 2 `*.idx` file,2180cloning or fetching over a non native protocol (e.g. "http")2181that will copy both `*.pack` file and corresponding `*.idx` file from the2182other side may give you a repository that cannot be accessed with your2183older version of Git. If the `*.pack` file is smaller than 2 GB, however,2184you can use linkgit:git-index-pack[1] on the *.pack file to regenerate2185the `*.idx` file.21862187pack.packSizeLimit::2188 The maximum size of a pack. This setting only affects2189 packing to a file when repacking, i.e. the git:// protocol2190 is unaffected. It can be overridden by the `--max-pack-size`2191 option of linkgit:git-repack[1]. Reaching this limit results2192 in the creation of multiple packfiles; which in turn prevents2193 bitmaps from being created.2194 The minimum size allowed is limited to 1 MiB.2195 The default is unlimited.2196 Common unit suffixes of 'k', 'm', or 'g' are2197 supported.21982199pack.useBitmaps::2200 When true, git will use pack bitmaps (if available) when packing2201 to stdout (e.g., during the server side of a fetch). Defaults to2202 true. You should not generally need to turn this off unless2203 you are debugging pack bitmaps.22042205pack.writeBitmaps (deprecated)::2206 This is a deprecated synonym for `repack.writeBitmaps`.22072208pack.writeBitmapHashCache::2209 When true, git will include a "hash cache" section in the bitmap2210 index (if one is written). This cache can be used to feed git's2211 delta heuristics, potentially leading to better deltas between2212 bitmapped and non-bitmapped objects (e.g., when serving a fetch2213 between an older, bitmapped pack and objects that have been2214 pushed since the last gc). The downside is that it consumes 42215 bytes per object of disk space, and that JGit's bitmap2216 implementation does not understand it, causing it to complain if2217 Git and JGit are used on the same repository. Defaults to false.22182219pager.<cmd>::2220 If the value is boolean, turns on or off pagination of the2221 output of a particular Git subcommand when writing to a tty.2222 Otherwise, turns on pagination for the subcommand using the2223 pager specified by the value of `pager.<cmd>`. If `--paginate`2224 or `--no-pager` is specified on the command line, it takes2225 precedence over this option. To disable pagination for all2226 commands, set `core.pager` or `GIT_PAGER` to `cat`.22272228pretty.<name>::2229 Alias for a --pretty= format string, as specified in2230 linkgit:git-log[1]. Any aliases defined here can be used just2231 as the built-in pretty formats could. For example,2232 running `git config pretty.changelog "format:* %H %s"`2233 would cause the invocation `git log --pretty=changelog`2234 to be equivalent to running `git log "--pretty=format:* %H %s"`.2235 Note that an alias with the same name as a built-in format2236 will be silently ignored.22372238pull.ff::2239 By default, Git does not create an extra merge commit when merging2240 a commit that is a descendant of the current commit. Instead, the2241 tip of the current branch is fast-forwarded. When set to `false`,2242 this variable tells Git to create an extra merge commit in such2243 a case (equivalent to giving the `--no-ff` option from the command2244 line). When set to `only`, only such fast-forward merges are2245 allowed (equivalent to giving the `--ff-only` option from the2246 command line). This setting overrides `merge.ff` when pulling.22472248pull.rebase::2249 When true, rebase branches on top of the fetched branch, instead2250 of merging the default branch from the default remote when "git2251 pull" is run. See "branch.<name>.rebase" for setting this on a2252 per-branch basis.2253+2254When preserve, also pass `--preserve-merges` along to 'git rebase'2255so that locally committed merge commits will not be flattened2256by running 'git pull'.2257+2258When the value is `interactive`, the rebase is run in interactive mode.2259+2260*NOTE*: this is a possibly dangerous operation; do *not* use2261it unless you understand the implications (see linkgit:git-rebase[1]2262for details).22632264pull.octopus::2265 The default merge strategy to use when pulling multiple branches2266 at once.22672268pull.twohead::2269 The default merge strategy to use when pulling a single branch.22702271push.default::2272 Defines the action `git push` should take if no refspec is2273 explicitly given. Different values are well-suited for2274 specific workflows; for instance, in a purely central workflow2275 (i.e. the fetch source is equal to the push destination),2276 `upstream` is probably what you want. Possible values are:2277+2278--22792280* `nothing` - do not push anything (error out) unless a refspec is2281 explicitly given. This is primarily meant for people who want to2282 avoid mistakes by always being explicit.22832284* `current` - push the current branch to update a branch with the same2285 name on the receiving end. Works in both central and non-central2286 workflows.22872288* `upstream` - push the current branch back to the branch whose2289 changes are usually integrated into the current branch (which is2290 called `@{upstream}`). This mode only makes sense if you are2291 pushing to the same repository you would normally pull from2292 (i.e. central workflow).22932294* `simple` - in centralized workflow, work like `upstream` with an2295 added safety to refuse to push if the upstream branch's name is2296 different from the local one.2297+2298When pushing to a remote that is different from the remote you normally2299pull from, work as `current`. This is the safest option and is suited2300for beginners.2301+2302This mode has become the default in Git 2.0.23032304* `matching` - push all branches having the same name on both ends.2305 This makes the repository you are pushing to remember the set of2306 branches that will be pushed out (e.g. if you always push 'maint'2307 and 'master' there and no other branches, the repository you push2308 to will have these two branches, and your local 'maint' and2309 'master' will be pushed there).2310+2311To use this mode effectively, you have to make sure _all_ the2312branches you would push out are ready to be pushed out before2313running 'git push', as the whole point of this mode is to allow you2314to push all of the branches in one go. If you usually finish work2315on only one branch and push out the result, while other branches are2316unfinished, this mode is not for you. Also this mode is not2317suitable for pushing into a shared central repository, as other2318people may add new branches there, or update the tip of existing2319branches outside your control.2320+2321This used to be the default, but not since Git 2.0 (`simple` is the2322new default).23232324--23252326push.followTags::2327 If set to true enable '--follow-tags' option by default. You2328 may override this configuration at time of push by specifying2329 '--no-follow-tags'.23302331push.gpgSign::2332 May be set to a boolean value, or the string 'if-asked'. A true2333 value causes all pushes to be GPG signed, as if '--signed' is2334 passed to linkgit:git-push[1]. The string 'if-asked' causes2335 pushes to be signed if the server supports it, as if2336 '--signed=if-asked' is passed to 'git push'. A false value may2337 override a value from a lower-priority config file. An explicit2338 command-line flag always overrides this config option.23392340push.recurseSubmodules::2341 Make sure all submodule commits used by the revisions to be pushed2342 are available on a remote-tracking branch. If the value is 'check'2343 then Git will verify that all submodule commits that changed in the2344 revisions to be pushed are available on at least one remote of the2345 submodule. If any commits are missing, the push will be aborted and2346 exit with non-zero status. If the value is 'on-demand' then all2347 submodules that changed in the revisions to be pushed will be2348 pushed. If on-demand was not able to push all necessary revisions2349 it will also be aborted and exit with non-zero status. If the value2350 is 'no' then default behavior of ignoring submodules when pushing2351 is retained. You may override this configuration at time of push by2352 specifying '--recurse-submodules=check|on-demand|no'.23532354rebase.stat::2355 Whether to show a diffstat of what changed upstream since the last2356 rebase. False by default.23572358rebase.autoSquash::2359 If set to true enable '--autosquash' option by default.23602361rebase.autoStash::2362 When set to true, automatically create a temporary stash2363 before the operation begins, and apply it after the operation2364 ends. This means that you can run rebase on a dirty worktree.2365 However, use with care: the final stash application after a2366 successful rebase might result in non-trivial conflicts.2367 Defaults to false.23682369rebase.missingCommitsCheck::2370 If set to "warn", git rebase -i will print a warning if some2371 commits are removed (e.g. a line was deleted), however the2372 rebase will still proceed. If set to "error", it will print2373 the previous warning and stop the rebase, 'git rebase2374 --edit-todo' can then be used to correct the error. If set to2375 "ignore", no checking is done.2376 To drop a commit without warning or error, use the `drop`2377 command in the todo-list.2378 Defaults to "ignore".23792380rebase.instructionFormat2381 A format string, as specified in linkgit:git-log[1], to be used for2382 the instruction list during an interactive rebase. The format will automatically2383 have the long commit hash prepended to the format.23842385receive.advertiseAtomic::2386 By default, git-receive-pack will advertise the atomic push2387 capability to its clients. If you don't want to this capability2388 to be advertised, set this variable to false.23892390receive.autogc::2391 By default, git-receive-pack will run "git-gc --auto" after2392 receiving data from git-push and updating refs. You can stop2393 it by setting this variable to false.23942395receive.certNonceSeed::2396 By setting this variable to a string, `git receive-pack`2397 will accept a `git push --signed` and verifies it by using2398 a "nonce" protected by HMAC using this string as a secret2399 key.24002401receive.certNonceSlop::2402 When a `git push --signed` sent a push certificate with a2403 "nonce" that was issued by a receive-pack serving the same2404 repository within this many seconds, export the "nonce"2405 found in the certificate to `GIT_PUSH_CERT_NONCE` to the2406 hooks (instead of what the receive-pack asked the sending2407 side to include). This may allow writing checks in2408 `pre-receive` and `post-receive` a bit easier. Instead of2409 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable2410 that records by how many seconds the nonce is stale to2411 decide if they want to accept the certificate, they only2412 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.24132414receive.fsckObjects::2415 If it is set to true, git-receive-pack will check all received2416 objects. It will abort in the case of a malformed object or a2417 broken link. The result of an abort are only dangling objects.2418 Defaults to false. If not set, the value of `transfer.fsckObjects`2419 is used instead.24202421receive.fsck.<msg-id>::2422 When `receive.fsckObjects` is set to true, errors can be switched2423 to warnings and vice versa by configuring the `receive.fsck.<msg-id>`2424 setting where the `<msg-id>` is the fsck message ID and the value2425 is one of `error`, `warn` or `ignore`. For convenience, fsck prefixes2426 the error/warning with the message ID, e.g. "missingEmail: invalid2427 author/committer line - missing email" means that setting2428 `receive.fsck.missingEmail = ignore` will hide that issue.2429+2430This feature is intended to support working with legacy repositories2431which would not pass pushing when `receive.fsckObjects = true`, allowing2432the host to accept repositories with certain known issues but still catch2433other issues.24342435receive.fsck.skipList::2436 The path to a sorted list of object names (i.e. one SHA-1 per2437 line) that are known to be broken in a non-fatal way and should2438 be ignored. This feature is useful when an established project2439 should be accepted despite early commits containing errors that2440 can be safely ignored such as invalid committer email addresses.2441 Note: corrupt objects cannot be skipped with this setting.24422443receive.unpackLimit::2444 If the number of objects received in a push is below this2445 limit then the objects will be unpacked into loose object2446 files. However if the number of received objects equals or2447 exceeds this limit then the received pack will be stored as2448 a pack, after adding any missing delta bases. Storing the2449 pack from a push can make the push operation complete faster,2450 especially on slow filesystems. If not set, the value of2451 `transfer.unpackLimit` is used instead.24522453receive.denyDeletes::2454 If set to true, git-receive-pack will deny a ref update that deletes2455 the ref. Use this to prevent such a ref deletion via a push.24562457receive.denyDeleteCurrent::2458 If set to true, git-receive-pack will deny a ref update that2459 deletes the currently checked out branch of a non-bare repository.24602461receive.denyCurrentBranch::2462 If set to true or "refuse", git-receive-pack will deny a ref update2463 to the currently checked out branch of a non-bare repository.2464 Such a push is potentially dangerous because it brings the HEAD2465 out of sync with the index and working tree. If set to "warn",2466 print a warning of such a push to stderr, but allow the push to2467 proceed. If set to false or "ignore", allow such pushes with no2468 message. Defaults to "refuse".2469+2470Another option is "updateInstead" which will update the working2471tree if pushing into the current branch. This option is2472intended for synchronizing working directories when one side is not easily2473accessible via interactive ssh (e.g. a live web site, hence the requirement2474that the working directory be clean). This mode also comes in handy when2475developing inside a VM to test and fix code on different Operating Systems.2476+2477By default, "updateInstead" will refuse the push if the working tree or2478the index have any difference from the HEAD, but the `push-to-checkout`2479hook can be used to customize this. See linkgit:githooks[5].24802481receive.denyNonFastForwards::2482 If set to true, git-receive-pack will deny a ref update which is2483 not a fast-forward. Use this to prevent such an update via a push,2484 even if that push is forced. This configuration variable is2485 set when initializing a shared repository.24862487receive.hideRefs::2488 This variable is the same as `transfer.hideRefs`, but applies2489 only to `receive-pack` (and so affects pushes, but not fetches).2490 An attempt to update or delete a hidden ref by `git push` is2491 rejected.24922493receive.updateServerInfo::2494 If set to true, git-receive-pack will run git-update-server-info2495 after receiving data from git-push and updating refs.24962497receive.shallowUpdate::2498 If set to true, .git/shallow can be updated when new refs2499 require new shallow roots. Otherwise those refs are rejected.25002501remote.pushDefault::2502 The remote to push to by default. Overrides2503 `branch.<name>.remote` for all branches, and is overridden by2504 `branch.<name>.pushRemote` for specific branches.25052506remote.<name>.url::2507 The URL of a remote repository. See linkgit:git-fetch[1] or2508 linkgit:git-push[1].25092510remote.<name>.pushurl::2511 The push URL of a remote repository. See linkgit:git-push[1].25122513remote.<name>.proxy::2514 For remotes that require curl (http, https and ftp), the URL to2515 the proxy to use for that remote. Set to the empty string to2516 disable proxying for that remote.25172518remote.<name>.proxyAuthMethod::2519 For remotes that require curl (http, https and ftp), the method to use for2520 authenticating against the proxy in use (probably set in2521 `remote.<name>.proxy`). See `http.proxyAuthMethod`.25222523remote.<name>.fetch::2524 The default set of "refspec" for linkgit:git-fetch[1]. See2525 linkgit:git-fetch[1].25262527remote.<name>.push::2528 The default set of "refspec" for linkgit:git-push[1]. See2529 linkgit:git-push[1].25302531remote.<name>.mirror::2532 If true, pushing to this remote will automatically behave2533 as if the `--mirror` option was given on the command line.25342535remote.<name>.skipDefaultUpdate::2536 If true, this remote will be skipped by default when updating2537 using linkgit:git-fetch[1] or the `update` subcommand of2538 linkgit:git-remote[1].25392540remote.<name>.skipFetchAll::2541 If true, this remote will be skipped by default when updating2542 using linkgit:git-fetch[1] or the `update` subcommand of2543 linkgit:git-remote[1].25442545remote.<name>.receivepack::2546 The default program to execute on the remote side when pushing. See2547 option --receive-pack of linkgit:git-push[1].25482549remote.<name>.uploadpack::2550 The default program to execute on the remote side when fetching. See2551 option --upload-pack of linkgit:git-fetch-pack[1].25522553remote.<name>.tagOpt::2554 Setting this value to --no-tags disables automatic tag following when2555 fetching from remote <name>. Setting it to --tags will fetch every2556 tag from remote <name>, even if they are not reachable from remote2557 branch heads. Passing these flags directly to linkgit:git-fetch[1] can2558 override this setting. See options --tags and --no-tags of2559 linkgit:git-fetch[1].25602561remote.<name>.vcs::2562 Setting this to a value <vcs> will cause Git to interact with2563 the remote with the git-remote-<vcs> helper.25642565remote.<name>.prune::2566 When set to true, fetching from this remote by default will also2567 remove any remote-tracking references that no longer exist on the2568 remote (as if the `--prune` option was given on the command line).2569 Overrides `fetch.prune` settings, if any.25702571remotes.<group>::2572 The list of remotes which are fetched by "git remote update2573 <group>". See linkgit:git-remote[1].25742575repack.useDeltaBaseOffset::2576 By default, linkgit:git-repack[1] creates packs that use2577 delta-base offset. If you need to share your repository with2578 Git older than version 1.4.4, either directly or via a dumb2579 protocol such as http, then you need to set this option to2580 "false" and repack. Access from old Git versions over the2581 native protocol are unaffected by this option.25822583repack.packKeptObjects::2584 If set to true, makes `git repack` act as if2585 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for2586 details. Defaults to `false` normally, but `true` if a bitmap2587 index is being written (either via `--write-bitmap-index` or2588 `repack.writeBitmaps`).25892590repack.writeBitmaps::2591 When true, git will write a bitmap index when packing all2592 objects to disk (e.g., when `git repack -a` is run). This2593 index can speed up the "counting objects" phase of subsequent2594 packs created for clones and fetches, at the cost of some disk2595 space and extra time spent on the initial repack. This has2596 no effect if multiple packfiles are created.2597 Defaults to false.25982599rerere.autoUpdate::2600 When set to true, `git-rerere` updates the index with the2601 resulting contents after it cleanly resolves conflicts using2602 previously recorded resolution. Defaults to false.26032604rerere.enabled::2605 Activate recording of resolved conflicts, so that identical2606 conflict hunks can be resolved automatically, should they be2607 encountered again. By default, linkgit:git-rerere[1] is2608 enabled if there is an `rr-cache` directory under the2609 `$GIT_DIR`, e.g. if "rerere" was previously used in the2610 repository.26112612sendemail.identity::2613 A configuration identity. When given, causes values in the2614 'sendemail.<identity>' subsection to take precedence over2615 values in the 'sendemail' section. The default identity is2616 the value of 'sendemail.identity'.26172618sendemail.smtpEncryption::2619 See linkgit:git-send-email[1] for description. Note that this2620 setting is not subject to the 'identity' mechanism.26212622sendemail.smtpssl (deprecated)::2623 Deprecated alias for 'sendemail.smtpEncryption = ssl'.26242625sendemail.smtpsslcertpath::2626 Path to ca-certificates (either a directory or a single file).2627 Set it to an empty string to disable certificate verification.26282629sendemail.<identity>.*::2630 Identity-specific versions of the 'sendemail.*' parameters2631 found below, taking precedence over those when the this2632 identity is selected, through command-line or2633 'sendemail.identity'.26342635sendemail.aliasesFile::2636sendemail.aliasFileType::2637sendemail.annotate::2638sendemail.bcc::2639sendemail.cc::2640sendemail.ccCmd::2641sendemail.chainReplyTo::2642sendemail.confirm::2643sendemail.envelopeSender::2644sendemail.from::2645sendemail.multiEdit::2646sendemail.signedoffbycc::2647sendemail.smtpPass::2648sendemail.suppresscc::2649sendemail.suppressFrom::2650sendemail.to::2651sendemail.smtpDomain::2652sendemail.smtpServer::2653sendemail.smtpServerPort::2654sendemail.smtpServerOption::2655sendemail.smtpUser::2656sendemail.thread::2657sendemail.transferEncoding::2658sendemail.validate::2659sendemail.xmailer::2660 See linkgit:git-send-email[1] for description.26612662sendemail.signedoffcc (deprecated)::2663 Deprecated alias for 'sendemail.signedoffbycc'.26642665showbranch.default::2666 The default set of branches for linkgit:git-show-branch[1].2667 See linkgit:git-show-branch[1].26682669status.relativePaths::2670 By default, linkgit:git-status[1] shows paths relative to the2671 current directory. Setting this variable to `false` shows paths2672 relative to the repository root (this was the default for Git2673 prior to v1.5.4).26742675status.short::2676 Set to true to enable --short by default in linkgit:git-status[1].2677 The option --no-short takes precedence over this variable.26782679status.branch::2680 Set to true to enable --branch by default in linkgit:git-status[1].2681 The option --no-branch takes precedence over this variable.26822683status.displayCommentPrefix::2684 If set to true, linkgit:git-status[1] will insert a comment2685 prefix before each output line (starting with2686 `core.commentChar`, i.e. `#` by default). This was the2687 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.2688 Defaults to false.26892690status.showUntrackedFiles::2691 By default, linkgit:git-status[1] and linkgit:git-commit[1] show2692 files which are not currently tracked by Git. Directories which2693 contain only untracked files, are shown with the directory name2694 only. Showing untracked files means that Git needs to lstat() all2695 the files in the whole repository, which might be slow on some2696 systems. So, this variable controls how the commands displays2697 the untracked files. Possible values are:2698+2699--2700* `no` - Show no untracked files.2701* `normal` - Show untracked files and directories.2702* `all` - Show also individual files in untracked directories.2703--2704+2705If this variable is not specified, it defaults to 'normal'.2706This variable can be overridden with the -u|--untracked-files option2707of linkgit:git-status[1] and linkgit:git-commit[1].27082709status.submoduleSummary::2710 Defaults to false.2711 If this is set to a non zero number or true (identical to -1 or an2712 unlimited number), the submodule summary will be enabled and a2713 summary of commits for modified submodules will be shown (see2714 --summary-limit option of linkgit:git-submodule[1]). Please note2715 that the summary output command will be suppressed for all2716 submodules when `diff.ignoreSubmodules` is set to 'all' or only2717 for those submodules where `submodule.<name>.ignore=all`. The only2718 exception to that rule is that status and commit will show staged2719 submodule changes. To2720 also view the summary for ignored submodules you can either use2721 the --ignore-submodules=dirty command-line option or the 'git2722 submodule summary' command, which shows a similar output but does2723 not honor these settings.27242725stash.showPatch::2726 If this is set to true, the `git stash show` command without an2727 option will show the stash in patch form. Defaults to false.2728 See description of 'show' command in linkgit:git-stash[1].27292730stash.showStat::2731 If this is set to true, the `git stash show` command without an2732 option will show diffstat of the stash. Defaults to true.2733 See description of 'show' command in linkgit:git-stash[1].27342735submodule.<name>.path::2736submodule.<name>.url::2737 The path within this project and URL for a submodule. These2738 variables are initially populated by 'git submodule init'. See2739 linkgit:git-submodule[1] and linkgit:gitmodules[5] for2740 details.27412742submodule.<name>.update::2743 The default update procedure for a submodule. This variable2744 is populated by `git submodule init` from the2745 linkgit:gitmodules[5] file. See description of 'update'2746 command in linkgit:git-submodule[1].27472748submodule.<name>.branch::2749 The remote branch name for a submodule, used by `git submodule2750 update --remote`. Set this option to override the value found in2751 the `.gitmodules` file. See linkgit:git-submodule[1] and2752 linkgit:gitmodules[5] for details.27532754submodule.<name>.fetchRecurseSubmodules::2755 This option can be used to control recursive fetching of this2756 submodule. It can be overridden by using the --[no-]recurse-submodules2757 command-line option to "git fetch" and "git pull".2758 This setting will override that from in the linkgit:gitmodules[5]2759 file.27602761submodule.<name>.ignore::2762 Defines under what circumstances "git status" and the diff family show2763 a submodule as modified. When set to "all", it will never be considered2764 modified (but it will nonetheless show up in the output of status and2765 commit when it has been staged), "dirty" will ignore all changes2766 to the submodules work tree and2767 takes only differences between the HEAD of the submodule and the commit2768 recorded in the superproject into account. "untracked" will additionally2769 let submodules with modified tracked files in their work tree show up.2770 Using "none" (the default when this option is not set) also shows2771 submodules that have untracked files in their work tree as changed.2772 This setting overrides any setting made in .gitmodules for this submodule,2773 both settings can be overridden on the command line by using the2774 "--ignore-submodules" option. The 'git submodule' commands are not2775 affected by this setting.27762777submodule.fetchJobs::2778 Specifies how many submodules are fetched/cloned at the same time.2779 A positive integer allows up to that number of submodules fetched2780 in parallel. A value of 0 will give some reasonable default.2781 If unset, it defaults to 1.27822783tag.forceSignAnnotated::2784 A boolean to specify whether annotated tags created should be GPG signed.2785 If `--annotate` is specified on the command line, it takes2786 precedence over this option.27872788tag.sort::2789 This variable controls the sort ordering of tags when displayed by2790 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the2791 value of this variable will be used as the default.27922793tar.umask::2794 This variable can be used to restrict the permission bits of2795 tar archive entries. The default is 0002, which turns off the2796 world write bit. The special value "user" indicates that the2797 archiving user's umask will be used instead. See umask(2) and2798 linkgit:git-archive[1].27992800transfer.fsckObjects::2801 When `fetch.fsckObjects` or `receive.fsckObjects` are2802 not set, the value of this variable is used instead.2803 Defaults to false.28042805transfer.hideRefs::2806 String(s) `receive-pack` and `upload-pack` use to decide which2807 refs to omit from their initial advertisements. Use more than2808 one definition to specify multiple prefix strings. A ref that is2809 under the hierarchies listed in the value of this variable is2810 excluded, and is hidden when responding to `git push` or `git2811 fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for2812 program-specific versions of this config.2813+2814You may also include a `!` in front of the ref name to negate the entry,2815explicitly exposing it, even if an earlier entry marked it as hidden.2816If you have multiple hideRefs values, later entries override earlier ones2817(and entries in more-specific config files override less-specific ones).2818+2819If a namespace is in use, the namespace prefix is stripped from each2820reference before it is matched against `transfer.hiderefs` patterns.2821For example, if `refs/heads/master` is specified in `transfer.hideRefs` and2822the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`2823is omitted from the advertisements but `refs/heads/master` and2824`refs/namespaces/bar/refs/heads/master` are still advertised as so-called2825"have" lines. In order to match refs before stripping, add a `^` in front of2826the ref name. If you combine `!` and `^`, `!` must be specified first.28272828transfer.unpackLimit::2829 When `fetch.unpackLimit` or `receive.unpackLimit` are2830 not set, the value of this variable is used instead.2831 The default value is 100.28322833uploadarchive.allowUnreachable::2834 If true, allow clients to use `git archive --remote` to request2835 any tree, whether reachable from the ref tips or not. See the2836 discussion in the `SECURITY` section of2837 linkgit:git-upload-archive[1] for more details. Defaults to2838 `false`.28392840uploadpack.hideRefs::2841 This variable is the same as `transfer.hideRefs`, but applies2842 only to `upload-pack` (and so affects only fetches, not pushes).2843 An attempt to fetch a hidden ref by `git fetch` will fail. See2844 also `uploadpack.allowTipSHA1InWant`.28452846uploadpack.allowTipSHA1InWant::2847 When `uploadpack.hideRefs` is in effect, allow `upload-pack`2848 to accept a fetch request that asks for an object at the tip2849 of a hidden ref (by default, such a request is rejected).2850 see also `uploadpack.hideRefs`.28512852uploadpack.allowReachableSHA1InWant::2853 Allow `upload-pack` to accept a fetch request that asks for an2854 object that is reachable from any ref tip. However, note that2855 calculating object reachability is computationally expensive.2856 Defaults to `false`.28572858uploadpack.keepAlive::2859 When `upload-pack` has started `pack-objects`, there may be a2860 quiet period while `pack-objects` prepares the pack. Normally2861 it would output progress information, but if `--quiet` was used2862 for the fetch, `pack-objects` will output nothing at all until2863 the pack data begins. Some clients and networks may consider2864 the server to be hung and give up. Setting this option instructs2865 `upload-pack` to send an empty keepalive packet every2866 `uploadpack.keepAlive` seconds. Setting this option to 02867 disables keepalive packets entirely. The default is 5 seconds.28682869url.<base>.insteadOf::2870 Any URL that starts with this value will be rewritten to2871 start, instead, with <base>. In cases where some site serves a2872 large number of repositories, and serves them with multiple2873 access methods, and some users need to use different access2874 methods, this feature allows people to specify any of the2875 equivalent URLs and have Git automatically rewrite the URL to2876 the best alternative for the particular user, even for a2877 never-before-seen repository on the site. When more than one2878 insteadOf strings match a given URL, the longest match is used.28792880url.<base>.pushInsteadOf::2881 Any URL that starts with this value will not be pushed to;2882 instead, it will be rewritten to start with <base>, and the2883 resulting URL will be pushed to. In cases where some site serves2884 a large number of repositories, and serves them with multiple2885 access methods, some of which do not allow push, this feature2886 allows people to specify a pull-only URL and have Git2887 automatically use an appropriate URL to push, even for a2888 never-before-seen repository on the site. When more than one2889 pushInsteadOf strings match a given URL, the longest match is2890 used. If a remote has an explicit pushurl, Git will ignore this2891 setting for that remote.28922893user.email::2894 Your email address to be recorded in any newly created commits.2895 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and2896 'EMAIL' environment variables. See linkgit:git-commit-tree[1].28972898user.name::2899 Your full name to be recorded in any newly created commits.2900 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'2901 environment variables. See linkgit:git-commit-tree[1].29022903user.useConfigOnly::2904 Instruct Git to avoid trying to guess defaults for 'user.email'2905 and 'user.name', and instead retrieve the values only from the2906 configuration. For example, if you have multiple email addresses2907 and would like to use a different one for each repository, then2908 with this configuration option set to `true` in the global config2909 along with a name, Git will prompt you to set up an email before2910 making new commits in a newly cloned repository.2911 Defaults to `false`.29122913user.signingKey::2914 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the2915 key you want it to automatically when creating a signed tag or2916 commit, you can override the default selection with this variable.2917 This option is passed unchanged to gpg's --local-user parameter,2918 so you may specify a key using any method that gpg supports.29192920versionsort.prereleaseSuffix::2921 When version sort is used in linkgit:git-tag[1], prerelease2922 tags (e.g. "1.0-rc1") may appear after the main release2923 "1.0". By specifying the suffix "-rc" in this variable,2924 "1.0-rc1" will appear before "1.0".2925+2926This variable can be specified multiple times, once per suffix. The2927order of suffixes in the config file determines the sorting order2928(e.g. if "-pre" appears before "-rc" in the config file then 1.0-preXX2929is sorted before 1.0-rcXX). The sorting order between different2930suffixes is undefined if they are in multiple config files.29312932web.browser::2933 Specify a web browser that may be used by some commands.2934 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]2935 may use it.