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 82The `include` and `includeIf` sections allow you to include config 83directives from another source. These sections behave identically to 84each other with the exception that `includeIf` sections may be ignored 85if their condition does not evaluate to true; see "Conditional includes" 86below. 87 88You can include a config file from another by setting the special 89`include.path` (or `includeIf.*.path`) variable to the name of the file 90to be included. The variable takes a pathname as its value, and is 91subject to tilde expansion. These variables can be given multiple times. 92 93The contents of the included file are inserted immediately, as if they 94had been found at the location of the include directive. If the value of the 95variable is a relative path, the path is considered to 96be relative to the configuration file in which the include directive 97was found. See below for examples. 98 99Conditional includes 100~~~~~~~~~~~~~~~~~~~~ 101 102You can include a config file from another conditionally by setting a 103`includeIf.<condition>.path` variable to the name of the file to be 104included. 105 106The condition starts with a keyword followed by a colon and some data 107whose format and meaning depends on the keyword. Supported keywords 108are: 109 110`gitdir`:: 111 112 The data that follows the keyword `gitdir:` is used as a glob 113 pattern. If the location of the .git directory matches the 114 pattern, the include condition is met. 115+ 116The .git location may be auto-discovered, or come from `$GIT_DIR` 117environment variable. If the repository is auto discovered via a .git 118file (e.g. from submodules, or a linked worktree), the .git location 119would be the final location where the .git directory is, not where the 120.git file is. 121+ 122The pattern can contain standard globbing wildcards and two additional 123ones, `**/` and `/**`, that can match multiple path components. Please 124refer to linkgit:gitignore[5] for details. For convenience: 125 126 * If the pattern starts with `~/`, `~` will be substituted with the 127 content of the environment variable `HOME`. 128 129 * If the pattern starts with `./`, it is replaced with the directory 130 containing the current config file. 131 132 * If the pattern does not start with either `~/`, `./` or `/`, `**/` 133 will be automatically prepended. For example, the pattern `foo/bar` 134 becomes `**/foo/bar` and would match `/any/path/to/foo/bar`. 135 136 * If the pattern ends with `/`, `**` will be automatically added. For 137 example, the pattern `foo/` becomes `foo/**`. In other words, it 138 matches "foo" and everything inside, recursively. 139 140`gitdir/i`:: 141 This is the same as `gitdir` except that matching is done 142 case-insensitively (e.g. on case-insensitive file sytems) 143 144A few more notes on matching via `gitdir` and `gitdir/i`: 145 146 * Symlinks in `$GIT_DIR` are not resolved before matching. 147 148 * Note that "../" is not special and will match literally, which is 149 unlikely what you want. 150 151Example 152~~~~~~~ 153 154 # Core variables 155 [core] 156 ; Don't trust file modes 157 filemode = false 158 159 # Our diff algorithm 160 [diff] 161 external = /usr/local/bin/diff-wrapper 162 renames = true 163 164 [branch "devel"] 165 remote = origin 166 merge = refs/heads/devel 167 168 # Proxy settings 169 [core] 170 gitProxy="ssh" for "kernel.org" 171 gitProxy=default-proxy ; for the rest 172 173 [include] 174 path = /path/to/foo.inc ; include by absolute path 175 path = foo.inc ; find "foo.inc" relative to the current file 176 path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory 177 178 ; include if $GIT_DIR is /path/to/foo/.git 179 [includeIf "gitdir:/path/to/foo/.git"] 180 path = /path/to/foo.inc 181 182 ; include for all repositories inside /path/to/group 183 [includeIf "gitdir:/path/to/group/"] 184 path = /path/to/foo.inc 185 186 ; include for all repositories inside $HOME/to/group 187 [includeIf "gitdir:~/to/group/"] 188 path = /path/to/foo.inc 189 190 ; relative paths are always relative to the including 191 ; file (if the condition is true); their location is not 192 ; affected by the condition 193 [includeIf "gitdir:/path/to/group/"] 194 path = foo.inc 195 196Values 197~~~~~~ 198 199Values of many variables are treated as a simple string, but there 200are variables that take values of specific types and there are rules 201as to how to spell them. 202 203boolean:: 204 205 When a variable is said to take a boolean value, many 206 synonyms are accepted for 'true' and 'false'; these are all 207 case-insensitive. 208 209 true;; Boolean true can be spelled as `yes`, `on`, `true`, 210 or `1`. Also, a variable defined without `= <value>` 211 is taken as true. 212 213 false;; Boolean false can be spelled as `no`, `off`, 214 `false`, or `0`. 215+ 216When converting value to the canonical form using `--bool` type 217specifier; 'git config' will ensure that the output is "true" or 218"false" (spelled in lowercase). 219 220integer:: 221 The value for many variables that specify various sizes can 222 be suffixed with `k`, `M`,... to mean "scale the number by 223 1024", "by 1024x1024", etc. 224 225color:: 226 The value for a variable that takes a color is a list of 227 colors (at most two, one for foreground and one for background) 228 and attributes (as many as you want), separated by spaces. 229+ 230The basic colors accepted are `normal`, `black`, `red`, `green`, `yellow`, 231`blue`, `magenta`, `cyan` and `white`. The first color given is the 232foreground; the second is the background. 233+ 234Colors may also be given as numbers between 0 and 255; these use ANSI 235256-color mode (but note that not all terminals may support this). If 236your terminal supports it, you may also specify 24-bit RGB values as 237hex, like `#ff0ab3`. 238+ 239The accepted attributes are `bold`, `dim`, `ul`, `blink`, `reverse`, 240`italic`, and `strike` (for crossed-out or "strikethrough" letters). 241The position of any attributes with respect to the colors 242(before, after, or in between), doesn't matter. Specific attributes may 243be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`, 244`no-ul`, etc). 245+ 246An empty color string produces no color effect at all. This can be used 247to avoid coloring specific elements without disabling color entirely. 248+ 249For git's pre-defined color slots, the attributes are meant to be reset 250at the beginning of each item in the colored output. So setting 251`color.decorate.branch` to `black` will paint that branch name in a 252plain `black`, even if the previous thing on the same output line (e.g. 253opening parenthesis before the list of branch names in `log --decorate` 254output) is set to be painted with `bold` or some other attribute. 255However, custom log formats may do more complicated and layered 256coloring, and the negated forms may be useful there. 257 258pathname:: 259 A variable that takes a pathname value can be given a 260 string that begins with "`~/`" or "`~user/`", and the usual 261 tilde expansion happens to such a string: `~/` 262 is expanded to the value of `$HOME`, and `~user/` to the 263 specified user's home directory. 264 265 266Variables 267~~~~~~~~~ 268 269Note that this list is non-comprehensive and not necessarily complete. 270For command-specific variables, you will find a more detailed description 271in the appropriate manual page. 272 273Other git-related tools may and do use their own variables. When 274inventing new variables for use in your own tool, make sure their 275names do not conflict with those that are used by Git itself and 276other popular tools, and describe them in your documentation. 277 278 279advice.*:: 280 These variables control various optional help messages designed to 281 aid new users. All 'advice.*' variables default to 'true', and you 282 can tell Git that you do not need help by setting these to 'false': 283+ 284-- 285 pushUpdateRejected:: 286 Set this variable to 'false' if you want to disable 287 'pushNonFFCurrent', 288 'pushNonFFMatching', 'pushAlreadyExists', 289 'pushFetchFirst', and 'pushNeedsForce' 290 simultaneously. 291 pushNonFFCurrent:: 292 Advice shown when linkgit:git-push[1] fails due to a 293 non-fast-forward update to the current branch. 294 pushNonFFMatching:: 295 Advice shown when you ran linkgit:git-push[1] and pushed 296 'matching refs' explicitly (i.e. you used ':', or 297 specified a refspec that isn't your current branch) and 298 it resulted in a non-fast-forward error. 299 pushAlreadyExists:: 300 Shown when linkgit:git-push[1] rejects an update that 301 does not qualify for fast-forwarding (e.g., a tag.) 302 pushFetchFirst:: 303 Shown when linkgit:git-push[1] rejects an update that 304 tries to overwrite a remote ref that points at an 305 object we do not have. 306 pushNeedsForce:: 307 Shown when linkgit:git-push[1] rejects an update that 308 tries to overwrite a remote ref that points at an 309 object that is not a commit-ish, or make the remote 310 ref point at an object that is not a commit-ish. 311 statusHints:: 312 Show directions on how to proceed from the current 313 state in the output of linkgit:git-status[1], in 314 the template shown when writing commit messages in 315 linkgit:git-commit[1], and in the help message shown 316 by linkgit:git-checkout[1] when switching branch. 317 statusUoption:: 318 Advise to consider using the `-u` option to linkgit:git-status[1] 319 when the command takes more than 2 seconds to enumerate untracked 320 files. 321 commitBeforeMerge:: 322 Advice shown when linkgit:git-merge[1] refuses to 323 merge to avoid overwriting local changes. 324 resolveConflict:: 325 Advice shown by various commands when conflicts 326 prevent the operation from being performed. 327 implicitIdentity:: 328 Advice on how to set your identity configuration when 329 your information is guessed from the system username and 330 domain name. 331 detachedHead:: 332 Advice shown when you used linkgit:git-checkout[1] to 333 move to the detach HEAD state, to instruct how to create 334 a local branch after the fact. 335 amWorkDir:: 336 Advice that shows the location of the patch file when 337 linkgit:git-am[1] fails to apply it. 338 rmHints:: 339 In case of failure in the output of linkgit:git-rm[1], 340 show directions on how to proceed from the current state. 341-- 342 343core.fileMode:: 344 Tells Git if the executable bit of files in the working tree 345 is to be honored. 346+ 347Some filesystems lose the executable bit when a file that is 348marked as executable is checked out, or checks out an 349non-executable file with executable bit on. 350linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 351to see if it handles the executable bit correctly 352and this variable is automatically set as necessary. 353+ 354A repository, however, may be on a filesystem that handles 355the filemode correctly, and this variable is set to 'true' 356when created, but later may be made accessible from another 357environment that loses the filemode (e.g. exporting ext4 via 358CIFS mount, visiting a Cygwin created repository with 359Git for Windows or Eclipse). 360In such a case it may be necessary to set this variable to 'false'. 361See linkgit:git-update-index[1]. 362+ 363The default is true (when core.filemode is not specified in the config file). 364 365core.hideDotFiles:: 366 (Windows-only) If true, mark newly-created directories and files whose 367 name starts with a dot as hidden. If 'dotGitOnly', only the `.git/` 368 directory is hidden, but no other files starting with a dot. The 369 default mode is 'dotGitOnly'. 370 371core.ignoreCase:: 372 If true, this option enables various workarounds to enable 373 Git to work better on filesystems that are not case sensitive, 374 like FAT. For example, if a directory listing finds 375 "makefile" when Git expects "Makefile", Git will assume 376 it is really the same file, and continue to remember it as 377 "Makefile". 378+ 379The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 380will probe and set core.ignoreCase true if appropriate when the repository 381is created. 382 383core.precomposeUnicode:: 384 This option is only used by Mac OS implementation of Git. 385 When core.precomposeUnicode=true, Git reverts the unicode decomposition 386 of filenames done by Mac OS. This is useful when sharing a repository 387 between Mac OS and Linux or Windows. 388 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 389 When false, file names are handled fully transparent by Git, 390 which is backward compatible with older versions of Git. 391 392core.protectHFS:: 393 If set to true, do not allow checkout of paths that would 394 be considered equivalent to `.git` on an HFS+ filesystem. 395 Defaults to `true` on Mac OS, and `false` elsewhere. 396 397core.protectNTFS:: 398 If set to true, do not allow checkout of paths that would 399 cause problems with the NTFS filesystem, e.g. conflict with 400 8.3 "short" names. 401 Defaults to `true` on Windows, and `false` elsewhere. 402 403core.trustctime:: 404 If false, the ctime differences between the index and the 405 working tree are ignored; useful when the inode change time 406 is regularly modified by something outside Git (file system 407 crawlers and some backup systems). 408 See linkgit:git-update-index[1]. True by default. 409 410core.splitIndex:: 411 If true, the split-index feature of the index will be used. 412 See linkgit:git-update-index[1]. False by default. 413 414core.untrackedCache:: 415 Determines what to do about the untracked cache feature of the 416 index. It will be kept, if this variable is unset or set to 417 `keep`. It will automatically be added if set to `true`. And 418 it will automatically be removed, if set to `false`. Before 419 setting it to `true`, you should check that mtime is working 420 properly on your system. 421 See linkgit:git-update-index[1]. `keep` by default. 422 423core.checkStat:: 424 Determines which stat fields to match between the index 425 and work tree. The user can set this to 'default' or 426 'minimal'. Default (or explicitly 'default'), is to check 427 all fields, including the sub-second part of mtime and ctime. 428 429core.quotePath:: 430 Commands that output paths (e.g. 'ls-files', 'diff'), will 431 quote "unusual" characters in the pathname by enclosing the 432 pathname in double-quotes and escaping those characters with 433 backslashes in the same way C escapes control characters (e.g. 434 `\t` for TAB, `\n` for LF, `\\` for backslash) or bytes with 435 values larger than 0x80 (e.g. octal `\302\265` for "micro" in 436 UTF-8). If this variable is set to false, bytes higher than 437 0x80 are not considered "unusual" any more. Double-quotes, 438 backslash and control characters are always escaped regardless 439 of the setting of this variable. A simple space character is 440 not considered "unusual". Many commands can output pathnames 441 completely verbatim using the `-z` option. The default value 442 is true. 443 444core.eol:: 445 Sets the line ending type to use in the working directory for 446 files that have the `text` property set when core.autocrlf is false. 447 Alternatives are 'lf', 'crlf' and 'native', which uses the platform's 448 native line ending. The default value is `native`. See 449 linkgit:gitattributes[5] for more information on end-of-line 450 conversion. 451 452core.safecrlf:: 453 If true, makes Git check if converting `CRLF` is reversible when 454 end-of-line conversion is active. Git will verify if a command 455 modifies a file in the work tree either directly or indirectly. 456 For example, committing a file followed by checking out the 457 same file should yield the original file in the work tree. If 458 this is not the case for the current setting of 459 `core.autocrlf`, Git will reject the file. The variable can 460 be set to "warn", in which case Git will only warn about an 461 irreversible conversion but continue the operation. 462+ 463CRLF conversion bears a slight chance of corrupting data. 464When it is enabled, Git will convert CRLF to LF during commit and LF to 465CRLF during checkout. A file that contains a mixture of LF and 466CRLF before the commit cannot be recreated by Git. For text 467files this is the right thing to do: it corrects line endings 468such that we have only LF line endings in the repository. 469But for binary files that are accidentally classified as text the 470conversion can corrupt data. 471+ 472If you recognize such corruption early you can easily fix it by 473setting the conversion type explicitly in .gitattributes. Right 474after committing you still have the original file in your work 475tree and this file is not yet corrupted. You can explicitly tell 476Git that this file is binary and Git will handle the file 477appropriately. 478+ 479Unfortunately, the desired effect of cleaning up text files with 480mixed line endings and the undesired effect of corrupting binary 481files cannot be distinguished. In both cases CRLFs are removed 482in an irreversible way. For text files this is the right thing 483to do because CRLFs are line endings, while for binary files 484converting CRLFs corrupts data. 485+ 486Note, this safety check does not mean that a checkout will generate a 487file identical to the original file for a different setting of 488`core.eol` and `core.autocrlf`, but only for the current one. For 489example, a text file with `LF` would be accepted with `core.eol=lf` 490and could later be checked out with `core.eol=crlf`, in which case the 491resulting file would contain `CRLF`, although the original file 492contained `LF`. However, in both work trees the line endings would be 493consistent, that is either all `LF` or all `CRLF`, but never mixed. A 494file with mixed line endings would be reported by the `core.safecrlf` 495mechanism. 496 497core.autocrlf:: 498 Setting this variable to "true" is the same as setting 499 the `text` attribute to "auto" on all files and core.eol to "crlf". 500 Set to true if you want to have `CRLF` line endings in your 501 working directory and the repository has LF line endings. 502 This variable can be set to 'input', 503 in which case no output conversion is performed. 504 505core.symlinks:: 506 If false, symbolic links are checked out as small plain files that 507 contain the link text. linkgit:git-update-index[1] and 508 linkgit:git-add[1] will not change the recorded type to regular 509 file. Useful on filesystems like FAT that do not support 510 symbolic links. 511+ 512The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 513will probe and set core.symlinks false if appropriate when the repository 514is created. 515 516core.gitProxy:: 517 A "proxy command" to execute (as 'command host port') instead 518 of establishing direct connection to the remote server when 519 using the Git protocol for fetching. If the variable value is 520 in the "COMMAND for DOMAIN" format, the command is applied only 521 on hostnames ending with the specified domain string. This variable 522 may be set multiple times and is matched in the given order; 523 the first match wins. 524+ 525Can be overridden by the `GIT_PROXY_COMMAND` environment variable 526(which always applies universally, without the special "for" 527handling). 528+ 529The special string `none` can be used as the proxy command to 530specify that no proxy be used for a given domain pattern. 531This is useful for excluding servers inside a firewall from 532proxy use, while defaulting to a common proxy for external domains. 533 534core.sshCommand:: 535 If this variable is set, `git fetch` and `git push` will 536 use the specified command instead of `ssh` when they need to 537 connect to a remote system. The command is in the same form as 538 the `GIT_SSH_COMMAND` environment variable and is overridden 539 when the environment variable is set. 540 541core.ignoreStat:: 542 If true, Git will avoid using lstat() calls to detect if files have 543 changed by setting the "assume-unchanged" bit for those tracked files 544 which it has updated identically in both the index and working tree. 545+ 546When files are modified outside of Git, the user will need to stage 547the modified files explicitly (e.g. see 'Examples' section in 548linkgit:git-update-index[1]). 549Git will not normally detect changes to those files. 550+ 551This is useful on systems where lstat() calls are very slow, such as 552CIFS/Microsoft Windows. 553+ 554False by default. 555 556core.preferSymlinkRefs:: 557 Instead of the default "symref" format for HEAD 558 and other symbolic reference files, use symbolic links. 559 This is sometimes needed to work with old scripts that 560 expect HEAD to be a symbolic link. 561 562core.bare:: 563 If true this repository is assumed to be 'bare' and has no 564 working directory associated with it. If this is the case a 565 number of commands that require a working directory will be 566 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 567+ 568This setting is automatically guessed by linkgit:git-clone[1] or 569linkgit:git-init[1] when the repository was created. By default a 570repository that ends in "/.git" is assumed to be not bare (bare = 571false), while all other repositories are assumed to be bare (bare 572= true). 573 574core.worktree:: 575 Set the path to the root of the working tree. 576 If `GIT_COMMON_DIR` environment variable is set, core.worktree 577 is ignored and not used for determining the root of working tree. 578 This can be overridden by the `GIT_WORK_TREE` environment 579 variable and the `--work-tree` command-line option. 580 The value can be an absolute path or relative to the path to 581 the .git directory, which is either specified by --git-dir 582 or GIT_DIR, or automatically discovered. 583 If --git-dir or GIT_DIR is specified but none of 584 --work-tree, GIT_WORK_TREE and core.worktree is specified, 585 the current working directory is regarded as the top level 586 of your working tree. 587+ 588Note that this variable is honored even when set in a configuration 589file in a ".git" subdirectory of a directory and its value differs 590from the latter directory (e.g. "/path/to/.git/config" has 591core.worktree set to "/different/path"), which is most likely a 592misconfiguration. Running Git commands in the "/path/to" directory will 593still use "/different/path" as the root of the work tree and can cause 594confusion unless you know what you are doing (e.g. you are creating a 595read-only snapshot of the same index to a location different from the 596repository's usual working tree). 597 598core.logAllRefUpdates:: 599 Enable the reflog. Updates to a ref <ref> is logged to the file 600 "`$GIT_DIR/logs/<ref>`", by appending the new and old 601 SHA-1, the date/time and the reason of the update, but 602 only when the file exists. If this configuration 603 variable is set to `true`, missing "`$GIT_DIR/logs/<ref>`" 604 file is automatically created for branch heads (i.e. under 605 `refs/heads/`), remote refs (i.e. under `refs/remotes/`), 606 note refs (i.e. under `refs/notes/`), and the symbolic ref `HEAD`. 607 If it is set to `always`, then a missing reflog is automatically 608 created for any ref under `refs/`. 609+ 610This information can be used to determine what commit 611was the tip of a branch "2 days ago". 612+ 613This value is true by default in a repository that has 614a working directory associated with it, and false by 615default in a bare repository. 616 617core.repositoryFormatVersion:: 618 Internal variable identifying the repository format and layout 619 version. 620 621core.sharedRepository:: 622 When 'group' (or 'true'), the repository is made shareable between 623 several users in a group (making sure all the files and objects are 624 group-writable). When 'all' (or 'world' or 'everybody'), the 625 repository will be readable by all users, additionally to being 626 group-shareable. When 'umask' (or 'false'), Git will use permissions 627 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 628 files in the repository will have this mode value. '0xxx' will override 629 user's umask value (whereas the other options will only override 630 requested parts of the user's umask value). Examples: '0660' will make 631 the repo read/write-able for the owner and group, but inaccessible to 632 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 633 repository that is group-readable but not group-writable. 634 See linkgit:git-init[1]. False by default. 635 636core.warnAmbiguousRefs:: 637 If true, Git will warn you if the ref name you passed it is ambiguous 638 and might match multiple refs in the repository. True by default. 639 640core.compression:: 641 An integer -1..9, indicating a default compression level. 642 -1 is the zlib default. 0 means no compression, 643 and 1..9 are various speed/size tradeoffs, 9 being slowest. 644 If set, this provides a default to other compression variables, 645 such as `core.looseCompression` and `pack.compression`. 646 647core.looseCompression:: 648 An integer -1..9, indicating the compression level for objects that 649 are not in a pack file. -1 is the zlib default. 0 means no 650 compression, and 1..9 are various speed/size tradeoffs, 9 being 651 slowest. If not set, defaults to core.compression. If that is 652 not set, defaults to 1 (best speed). 653 654core.packedGitWindowSize:: 655 Number of bytes of a pack file to map into memory in a 656 single mapping operation. Larger window sizes may allow 657 your system to process a smaller number of large pack files 658 more quickly. Smaller window sizes will negatively affect 659 performance due to increased calls to the operating system's 660 memory manager, but may improve performance when accessing 661 a large number of large pack files. 662+ 663Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 664MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 665be reasonable for all users/operating systems. You probably do 666not need to adjust this value. 667+ 668Common unit suffixes of 'k', 'm', or 'g' are supported. 669 670core.packedGitLimit:: 671 Maximum number of bytes to map simultaneously into memory 672 from pack files. If Git needs to access more than this many 673 bytes at once to complete an operation it will unmap existing 674 regions to reclaim virtual address space within the process. 675+ 676Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 677This should be reasonable for all users/operating systems, except on 678the largest projects. You probably do not need to adjust this value. 679+ 680Common unit suffixes of 'k', 'm', or 'g' are supported. 681 682core.deltaBaseCacheLimit:: 683 Maximum number of bytes to reserve for caching base objects 684 that may be referenced by multiple deltified objects. By storing the 685 entire decompressed base objects in a cache Git is able 686 to avoid unpacking and decompressing frequently used base 687 objects multiple times. 688+ 689Default is 96 MiB on all platforms. This should be reasonable 690for all users/operating systems, except on the largest projects. 691You probably do not need to adjust this value. 692+ 693Common unit suffixes of 'k', 'm', or 'g' are supported. 694 695core.bigFileThreshold:: 696 Files larger than this size are stored deflated, without 697 attempting delta compression. Storing large files without 698 delta compression avoids excessive memory usage, at the 699 slight expense of increased disk usage. Additionally files 700 larger than this size are always treated as binary. 701+ 702Default is 512 MiB on all platforms. This should be reasonable 703for most projects as source code and other text files can still 704be delta compressed, but larger binary media files won't be. 705+ 706Common unit suffixes of 'k', 'm', or 'g' are supported. 707 708core.excludesFile:: 709 Specifies the pathname to the file that contains patterns to 710 describe paths that are not meant to be tracked, in addition 711 to '.gitignore' (per-directory) and '.git/info/exclude'. 712 Defaults to `$XDG_CONFIG_HOME/git/ignore`. 713 If `$XDG_CONFIG_HOME` is either not set or empty, `$HOME/.config/git/ignore` 714 is used instead. See linkgit:gitignore[5]. 715 716core.askPass:: 717 Some commands (e.g. svn and http interfaces) that interactively 718 ask for a password can be told to use an external program given 719 via the value of this variable. Can be overridden by the `GIT_ASKPASS` 720 environment variable. If not set, fall back to the value of the 721 `SSH_ASKPASS` environment variable or, failing that, a simple password 722 prompt. The external program shall be given a suitable prompt as 723 command-line argument and write the password on its STDOUT. 724 725core.attributesFile:: 726 In addition to '.gitattributes' (per-directory) and 727 '.git/info/attributes', Git looks into this file for attributes 728 (see linkgit:gitattributes[5]). Path expansions are made the same 729 way as for `core.excludesFile`. Its default value is 730 `$XDG_CONFIG_HOME/git/attributes`. If `$XDG_CONFIG_HOME` is either not 731 set or empty, `$HOME/.config/git/attributes` is used instead. 732 733core.hooksPath:: 734 By default Git will look for your hooks in the 735 '$GIT_DIR/hooks' directory. Set this to different path, 736 e.g. '/etc/git/hooks', and Git will try to find your hooks in 737 that directory, e.g. '/etc/git/hooks/pre-receive' instead of 738 in '$GIT_DIR/hooks/pre-receive'. 739+ 740The path can be either absolute or relative. A relative path is 741taken as relative to the directory where the hooks are run (see 742the "DESCRIPTION" section of linkgit:githooks[5]). 743+ 744This configuration variable is useful in cases where you'd like to 745centrally configure your Git hooks instead of configuring them on a 746per-repository basis, or as a more flexible and centralized 747alternative to having an `init.templateDir` where you've changed 748default hooks. 749 750core.editor:: 751 Commands such as `commit` and `tag` that let you edit 752 messages by launching an editor use the value of this 753 variable when it is set, and the environment variable 754 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 755 756core.commentChar:: 757 Commands such as `commit` and `tag` that let you edit 758 messages consider a line that begins with this character 759 commented, and removes them after the editor returns 760 (default '#'). 761+ 762If set to "auto", `git-commit` would select a character that is not 763the beginning character of any line in existing commit messages. 764 765core.packedRefsTimeout:: 766 The length of time, in milliseconds, to retry when trying to 767 lock the `packed-refs` file. Value 0 means not to retry at 768 all; -1 means to try indefinitely. Default is 1000 (i.e., 769 retry for 1 second). 770 771sequence.editor:: 772 Text editor used by `git rebase -i` for editing the rebase instruction file. 773 The value is meant to be interpreted by the shell when it is used. 774 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 775 When not configured the default commit message editor is used instead. 776 777core.pager:: 778 Text viewer for use by Git commands (e.g., 'less'). The value 779 is meant to be interpreted by the shell. The order of preference 780 is the `$GIT_PAGER` environment variable, then `core.pager` 781 configuration, then `$PAGER`, and then the default chosen at 782 compile time (usually 'less'). 783+ 784When the `LESS` environment variable is unset, Git sets it to `FRX` 785(if `LESS` environment variable is set, Git does not change it at 786all). If you want to selectively override Git's default setting 787for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 788be passed to the shell by Git, which will translate the final 789command to `LESS=FRX less -S`. The environment does not set the 790`S` option but the command line does, instructing less to truncate 791long lines. Similarly, setting `core.pager` to `less -+F` will 792deactivate the `F` option specified by the environment from the 793command-line, deactivating the "quit if one screen" behavior of 794`less`. One can specifically activate some flags for particular 795commands: for example, setting `pager.blame` to `less -S` enables 796line truncation only for `git blame`. 797+ 798Likewise, when the `LV` environment variable is unset, Git sets it 799to `-c`. You can override this setting by exporting `LV` with 800another value or setting `core.pager` to `lv +c`. 801 802core.whitespace:: 803 A comma separated list of common whitespace problems to 804 notice. 'git diff' will use `color.diff.whitespace` to 805 highlight them, and 'git apply --whitespace=error' will 806 consider them as errors. You can prefix `-` to disable 807 any of them (e.g. `-trailing-space`): 808+ 809* `blank-at-eol` treats trailing whitespaces at the end of the line 810 as an error (enabled by default). 811* `space-before-tab` treats a space character that appears immediately 812 before a tab character in the initial indent part of the line as an 813 error (enabled by default). 814* `indent-with-non-tab` treats a line that is indented with space 815 characters instead of the equivalent tabs as an error (not enabled by 816 default). 817* `tab-in-indent` treats a tab character in the initial indent part of 818 the line as an error (not enabled by default). 819* `blank-at-eof` treats blank lines added at the end of file as an error 820 (enabled by default). 821* `trailing-space` is a short-hand to cover both `blank-at-eol` and 822 `blank-at-eof`. 823* `cr-at-eol` treats a carriage-return at the end of line as 824 part of the line terminator, i.e. with it, `trailing-space` 825 does not trigger if the character before such a carriage-return 826 is not a whitespace (not enabled by default). 827* `tabwidth=<n>` tells how many character positions a tab occupies; this 828 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 829 errors. The default tab width is 8. Allowed values are 1 to 63. 830 831core.fsyncObjectFiles:: 832 This boolean will enable 'fsync()' when writing object files. 833+ 834This is a total waste of time and effort on a filesystem that orders 835data writes properly, but can be useful for filesystems that do not use 836journalling (traditional UNIX filesystems) or that only journal metadata 837and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 838 839core.preloadIndex:: 840 Enable parallel index preload for operations like 'git diff' 841+ 842This can speed up operations like 'git diff' and 'git status' especially 843on filesystems like NFS that have weak caching semantics and thus 844relatively high IO latencies. When enabled, Git will do the 845index comparison to the filesystem data in parallel, allowing 846overlapping IO's. Defaults to true. 847 848core.createObject:: 849 You can set this to 'link', in which case a hardlink followed by 850 a delete of the source are used to make sure that object creation 851 will not overwrite existing objects. 852+ 853On some file system/operating system combinations, this is unreliable. 854Set this config setting to 'rename' there; However, This will remove the 855check that makes sure that existing object files will not get overwritten. 856 857core.notesRef:: 858 When showing commit messages, also show notes which are stored in 859 the given ref. The ref must be fully qualified. If the given 860 ref does not exist, it is not an error but means that no 861 notes should be printed. 862+ 863This setting defaults to "refs/notes/commits", and it can be overridden by 864the `GIT_NOTES_REF` environment variable. See linkgit:git-notes[1]. 865 866core.sparseCheckout:: 867 Enable "sparse checkout" feature. See section "Sparse checkout" in 868 linkgit:git-read-tree[1] for more information. 869 870core.abbrev:: 871 Set the length object names are abbreviated to. If 872 unspecified or set to "auto", an appropriate value is 873 computed based on the approximate number of packed objects 874 in your repository, which hopefully is enough for 875 abbreviated object names to stay unique for some time. 876 877add.ignoreErrors:: 878add.ignore-errors (deprecated):: 879 Tells 'git add' to continue adding files when some files cannot be 880 added due to indexing errors. Equivalent to the `--ignore-errors` 881 option of linkgit:git-add[1]. `add.ignore-errors` is deprecated, 882 as it does not follow the usual naming convention for configuration 883 variables. 884 885alias.*:: 886 Command aliases for the linkgit:git[1] command wrapper - e.g. 887 after defining "alias.last = cat-file commit HEAD", the invocation 888 "git last" is equivalent to "git cat-file commit HEAD". To avoid 889 confusion and troubles with script usage, aliases that 890 hide existing Git commands are ignored. Arguments are split by 891 spaces, the usual shell quoting and escaping is supported. 892 A quote pair or a backslash can be used to quote them. 893+ 894If the alias expansion is prefixed with an exclamation point, 895it will be treated as a shell command. For example, defining 896"alias.new = !gitk --all --not ORIG_HEAD", the invocation 897"git new" is equivalent to running the shell command 898"gitk --all --not ORIG_HEAD". Note that shell commands will be 899executed from the top-level directory of a repository, which may 900not necessarily be the current directory. 901`GIT_PREFIX` is set as returned by running 'git rev-parse --show-prefix' 902from the original current directory. See linkgit:git-rev-parse[1]. 903 904am.keepcr:: 905 If true, git-am will call git-mailsplit for patches in mbox format 906 with parameter `--keep-cr`. In this case git-mailsplit will 907 not remove `\r` from lines ending with `\r\n`. Can be overridden 908 by giving `--no-keep-cr` from the command line. 909 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 910 911am.threeWay:: 912 By default, `git am` will fail if the patch does not apply cleanly. When 913 set to true, this setting tells `git am` to fall back on 3-way merge if 914 the patch records the identity of blobs it is supposed to apply to and 915 we have those blobs available locally (equivalent to giving the `--3way` 916 option from the command line). Defaults to `false`. 917 See linkgit:git-am[1]. 918 919apply.ignoreWhitespace:: 920 When set to 'change', tells 'git apply' to ignore changes in 921 whitespace, in the same way as the `--ignore-space-change` 922 option. 923 When set to one of: no, none, never, false tells 'git apply' to 924 respect all whitespace differences. 925 See linkgit:git-apply[1]. 926 927apply.whitespace:: 928 Tells 'git apply' how to handle whitespaces, in the same way 929 as the `--whitespace` option. See linkgit:git-apply[1]. 930 931branch.autoSetupMerge:: 932 Tells 'git branch' and 'git checkout' to set up new branches 933 so that linkgit:git-pull[1] will appropriately merge from the 934 starting point branch. Note that even if this option is not set, 935 this behavior can be chosen per-branch using the `--track` 936 and `--no-track` options. The valid settings are: `false` -- no 937 automatic setup is done; `true` -- automatic setup is done when the 938 starting point is a remote-tracking branch; `always` -- 939 automatic setup is done when the starting point is either a 940 local branch or remote-tracking 941 branch. This option defaults to true. 942 943branch.autoSetupRebase:: 944 When a new branch is created with 'git branch' or 'git checkout' 945 that tracks another branch, this variable tells Git to set 946 up pull to rebase instead of merge (see "branch.<name>.rebase"). 947 When `never`, rebase is never automatically set to true. 948 When `local`, rebase is set to true for tracked branches of 949 other local branches. 950 When `remote`, rebase is set to true for tracked branches of 951 remote-tracking branches. 952 When `always`, rebase will be set to true for all tracking 953 branches. 954 See "branch.autoSetupMerge" for details on how to set up a 955 branch to track another branch. 956 This option defaults to never. 957 958branch.<name>.remote:: 959 When on branch <name>, it tells 'git fetch' and 'git push' 960 which remote to fetch from/push to. The remote to push to 961 may be overridden with `remote.pushDefault` (for all branches). 962 The remote to push to, for the current branch, may be further 963 overridden by `branch.<name>.pushRemote`. If no remote is 964 configured, or if you are not on any branch, it defaults to 965 `origin` for fetching and `remote.pushDefault` for pushing. 966 Additionally, `.` (a period) is the current local repository 967 (a dot-repository), see `branch.<name>.merge`'s final note below. 968 969branch.<name>.pushRemote:: 970 When on branch <name>, it overrides `branch.<name>.remote` for 971 pushing. It also overrides `remote.pushDefault` for pushing 972 from branch <name>. When you pull from one place (e.g. your 973 upstream) and push to another place (e.g. your own publishing 974 repository), you would want to set `remote.pushDefault` to 975 specify the remote to push to for all branches, and use this 976 option to override it for a specific branch. 977 978branch.<name>.merge:: 979 Defines, together with branch.<name>.remote, the upstream branch 980 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 981 branch to merge and can also affect 'git push' (see push.default). 982 When in branch <name>, it tells 'git fetch' the default 983 refspec to be marked for merging in FETCH_HEAD. The value is 984 handled like the remote part of a refspec, and must match a 985 ref which is fetched from the remote given by 986 "branch.<name>.remote". 987 The merge information is used by 'git pull' (which at first calls 988 'git fetch') to lookup the default branch for merging. Without 989 this option, 'git pull' defaults to merge the first refspec fetched. 990 Specify multiple values to get an octopus merge. 991 If you wish to setup 'git pull' so that it merges into <name> from 992 another branch in the local repository, you can point 993 branch.<name>.merge to the desired branch, and use the relative path 994 setting `.` (a period) for branch.<name>.remote. 995 996branch.<name>.mergeOptions:: 997 Sets default options for merging into branch <name>. The syntax and 998 supported options are the same as those of linkgit:git-merge[1], but 999 option values containing whitespace characters are currently not1000 supported.10011002branch.<name>.rebase::1003 When true, rebase the branch <name> on top of the fetched branch,1004 instead of merging the default branch from the default remote when1005 "git pull" is run. See "pull.rebase" for doing this in a non1006 branch-specific manner.1007+1008When preserve, also pass `--preserve-merges` along to 'git rebase'1009so that locally committed merge commits will not be flattened1010by running 'git pull'.1011+1012When the value is `interactive`, the rebase is run in interactive mode.1013+1014*NOTE*: this is a possibly dangerous operation; do *not* use1015it unless you understand the implications (see linkgit:git-rebase[1]1016for details).10171018branch.<name>.description::1019 Branch description, can be edited with1020 `git branch --edit-description`. Branch description is1021 automatically added in the format-patch cover letter or1022 request-pull summary.10231024browser.<tool>.cmd::1025 Specify the command to invoke the specified browser. The1026 specified command is evaluated in shell with the URLs passed1027 as arguments. (See linkgit:git-web{litdd}browse[1].)10281029browser.<tool>.path::1030 Override the path for the given tool that may be used to1031 browse HTML help (see `-w` option in linkgit:git-help[1]) or a1032 working repository in gitweb (see linkgit:git-instaweb[1]).10331034clean.requireForce::1035 A boolean to make git-clean do nothing unless given -f,1036 -i or -n. Defaults to true.10371038color.branch::1039 A boolean to enable/disable color in the output of1040 linkgit:git-branch[1]. May be set to `always`,1041 `false` (or `never`) or `auto` (or `true`), in which case colors are used1042 only when the output is to a terminal. If unset, then the1043 value of `color.ui` is used (`auto` by default).10441045color.branch.<slot>::1046 Use customized color for branch coloration. `<slot>` is one of1047 `current` (the current branch), `local` (a local branch),1048 `remote` (a remote-tracking branch in refs/remotes/),1049 `upstream` (upstream tracking branch), `plain` (other1050 refs).10511052color.diff::1053 Whether to use ANSI escape sequences to add color to patches.1054 If this is set to `always`, linkgit:git-diff[1],1055 linkgit:git-log[1], and linkgit:git-show[1] will use color1056 for all patches. If it is set to `true` or `auto`, those1057 commands will only use color when output is to the terminal.1058 If unset, then the value of `color.ui` is used (`auto` by1059 default).1060+1061This does not affect linkgit:git-format-patch[1] or the1062'git-diff-{asterisk}' plumbing commands. Can be overridden on the1063command line with the `--color[=<when>]` option.10641065color.diff.<slot>::1066 Use customized color for diff colorization. `<slot>` specifies1067 which part of the patch to use the specified color, and is one1068 of `context` (context text - `plain` is a historical synonym),1069 `meta` (metainformation), `frag`1070 (hunk header), 'func' (function in hunk header), `old` (removed lines),1071 `new` (added lines), `commit` (commit headers), or `whitespace`1072 (highlighting whitespace errors).10731074color.decorate.<slot>::1075 Use customized color for 'git log --decorate' output. `<slot>` is one1076 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local1077 branches, remote-tracking branches, tags, stash and HEAD, respectively.10781079color.grep::1080 When set to `always`, always highlight matches. When `false` (or1081 `never`), never. When set to `true` or `auto`, use color only1082 when the output is written to the terminal. If unset, then the1083 value of `color.ui` is used (`auto` by default).10841085color.grep.<slot>::1086 Use customized color for grep colorization. `<slot>` specifies which1087 part of the line to use the specified color, and is one of1088+1089--1090`context`;;1091 non-matching text in context lines (when using `-A`, `-B`, or `-C`)1092`filename`;;1093 filename prefix (when not using `-h`)1094`function`;;1095 function name lines (when using `-p`)1096`linenumber`;;1097 line number prefix (when using `-n`)1098`match`;;1099 matching text (same as setting `matchContext` and `matchSelected`)1100`matchContext`;;1101 matching text in context lines1102`matchSelected`;;1103 matching text in selected lines1104`selected`;;1105 non-matching text in selected lines1106`separator`;;1107 separators between fields on a line (`:`, `-`, and `=`)1108 and between hunks (`--`)1109--11101111color.interactive::1112 When set to `always`, always use colors for interactive prompts1113 and displays (such as those used by "git-add --interactive" and1114 "git-clean --interactive"). When false (or `never`), never.1115 When set to `true` or `auto`, use colors only when the output is1116 to the terminal. If unset, then the value of `color.ui` is1117 used (`auto` by default).11181119color.interactive.<slot>::1120 Use customized color for 'git add --interactive' and 'git clean1121 --interactive' output. `<slot>` may be `prompt`, `header`, `help`1122 or `error`, for four distinct types of normal output from1123 interactive commands.11241125color.pager::1126 A boolean to enable/disable colored output when the pager is in1127 use (default is true).11281129color.showBranch::1130 A boolean to enable/disable color in the output of1131 linkgit:git-show-branch[1]. May be set to `always`,1132 `false` (or `never`) or `auto` (or `true`), in which case colors are used1133 only when the output is to a terminal. If unset, then the1134 value of `color.ui` is used (`auto` by default).11351136color.status::1137 A boolean to enable/disable color in the output of1138 linkgit:git-status[1]. May be set to `always`,1139 `false` (or `never`) or `auto` (or `true`), in which case colors are used1140 only when the output is to a terminal. If unset, then the1141 value of `color.ui` is used (`auto` by default).11421143color.status.<slot>::1144 Use customized color for status colorization. `<slot>` is1145 one of `header` (the header text of the status message),1146 `added` or `updated` (files which are added but not committed),1147 `changed` (files which are changed but not added in the index),1148 `untracked` (files which are not tracked by Git),1149 `branch` (the current branch),1150 `nobranch` (the color the 'no branch' warning is shown in, defaulting1151 to red), or1152 `unmerged` (files which have unmerged changes).11531154color.ui::1155 This variable determines the default value for variables such1156 as `color.diff` and `color.grep` that control the use of color1157 per command family. Its scope will expand as more commands learn1158 configuration to set a default for the `--color` option. Set it1159 to `false` or `never` if you prefer Git commands not to use1160 color unless enabled explicitly with some other configuration1161 or the `--color` option. Set it to `always` if you want all1162 output not intended for machine consumption to use color, to1163 `true` or `auto` (this is the default since Git 1.8.4) if you1164 want such output to use color when written to the terminal.11651166column.ui::1167 Specify whether supported commands should output in columns.1168 This variable consists of a list of tokens separated by spaces1169 or commas:1170+1171These options control when the feature should be enabled1172(defaults to 'never'):1173+1174--1175`always`;;1176 always show in columns1177`never`;;1178 never show in columns1179`auto`;;1180 show in columns if the output is to the terminal1181--1182+1183These options control layout (defaults to 'column'). Setting any1184of these implies 'always' if none of 'always', 'never', or 'auto' are1185specified.1186+1187--1188`column`;;1189 fill columns before rows1190`row`;;1191 fill rows before columns1192`plain`;;1193 show in one column1194--1195+1196Finally, these options can be combined with a layout option (defaults1197to 'nodense'):1198+1199--1200`dense`;;1201 make unequal size columns to utilize more space1202`nodense`;;1203 make equal size columns1204--12051206column.branch::1207 Specify whether to output branch listing in `git branch` in columns.1208 See `column.ui` for details.12091210column.clean::1211 Specify the layout when list items in `git clean -i`, which always1212 shows files and directories in columns. See `column.ui` for details.12131214column.status::1215 Specify whether to output untracked files in `git status` in columns.1216 See `column.ui` for details.12171218column.tag::1219 Specify whether to output tag listing in `git tag` in columns.1220 See `column.ui` for details.12211222commit.cleanup::1223 This setting overrides the default of the `--cleanup` option in1224 `git commit`. See linkgit:git-commit[1] for details. Changing the1225 default can be useful when you always want to keep lines that begin1226 with comment character `#` in your log message, in which case you1227 would do `git config commit.cleanup whitespace` (note that you will1228 have to remove the help lines that begin with `#` in the commit log1229 template yourself, if you do this).12301231commit.gpgSign::12321233 A boolean to specify whether all commits should be GPG signed.1234 Use of this option when doing operations such as rebase can1235 result in a large number of commits being signed. It may be1236 convenient to use an agent to avoid typing your GPG passphrase1237 several times.12381239commit.status::1240 A boolean to enable/disable inclusion of status information in the1241 commit message template when using an editor to prepare the commit1242 message. Defaults to true.12431244commit.template::1245 Specify the pathname of a file to use as the template for1246 new commit messages.12471248commit.verbose::1249 A boolean or int to specify the level of verbose with `git commit`.1250 See linkgit:git-commit[1].12511252credential.helper::1253 Specify an external helper to be called when a username or1254 password credential is needed; the helper may consult external1255 storage to avoid prompting the user for the credentials. Note1256 that multiple helpers may be defined. See linkgit:gitcredentials[7]1257 for details.12581259credential.useHttpPath::1260 When acquiring credentials, consider the "path" component of an http1261 or https URL to be important. Defaults to false. See1262 linkgit:gitcredentials[7] for more information.12631264credential.username::1265 If no username is set for a network authentication, use this username1266 by default. See credential.<context>.* below, and1267 linkgit:gitcredentials[7].12681269credential.<url>.*::1270 Any of the credential.* options above can be applied selectively to1271 some credentials. For example "credential.https://example.com.username"1272 would set the default username only for https connections to1273 example.com. See linkgit:gitcredentials[7] for details on how URLs are1274 matched.12751276credentialCache.ignoreSIGHUP::1277 Tell git-credential-cache--daemon to ignore SIGHUP, instead of quitting.12781279include::diff-config.txt[]12801281difftool.<tool>.path::1282 Override the path for the given tool. This is useful in case1283 your tool is not in the PATH.12841285difftool.<tool>.cmd::1286 Specify the command to invoke the specified diff tool.1287 The specified command is evaluated in shell with the following1288 variables available: 'LOCAL' is set to the name of the temporary1289 file containing the contents of the diff pre-image and 'REMOTE'1290 is set to the name of the temporary file containing the contents1291 of the diff post-image.12921293difftool.prompt::1294 Prompt before each invocation of the diff tool.12951296fastimport.unpackLimit::1297 If the number of objects imported by linkgit:git-fast-import[1]1298 is below this limit, then the objects will be unpacked into1299 loose object files. However if the number of imported objects1300 equals or exceeds this limit then the pack will be stored as a1301 pack. Storing the pack from a fast-import can make the import1302 operation complete faster, especially on slow filesystems. If1303 not set, the value of `transfer.unpackLimit` is used instead.13041305fetch.recurseSubmodules::1306 This option can be either set to a boolean value or to 'on-demand'.1307 Setting it to a boolean changes the behavior of fetch and pull to1308 unconditionally recurse into submodules when set to true or to not1309 recurse at all when set to false. When set to 'on-demand' (the default1310 value), fetch and pull will only recurse into a populated submodule1311 when its superproject retrieves a commit that updates the submodule's1312 reference.13131314fetch.fsckObjects::1315 If it is set to true, git-fetch-pack will check all fetched1316 objects. It will abort in the case of a malformed object or a1317 broken link. The result of an abort are only dangling objects.1318 Defaults to false. If not set, the value of `transfer.fsckObjects`1319 is used instead.13201321fetch.unpackLimit::1322 If the number of objects fetched over the Git native1323 transfer is below this1324 limit, then the objects will be unpacked into loose object1325 files. However if the number of received objects equals or1326 exceeds this limit then the received pack will be stored as1327 a pack, after adding any missing delta bases. Storing the1328 pack from a push can make the push operation complete faster,1329 especially on slow filesystems. If not set, the value of1330 `transfer.unpackLimit` is used instead.13311332fetch.prune::1333 If true, fetch will automatically behave as if the `--prune`1334 option was given on the command line. See also `remote.<name>.prune`.13351336fetch.output::1337 Control how ref update status is printed. Valid values are1338 `full` and `compact`. Default value is `full`. See section1339 OUTPUT in linkgit:git-fetch[1] for detail.13401341format.attach::1342 Enable multipart/mixed attachments as the default for1343 'format-patch'. The value can also be a double quoted string1344 which will enable attachments as the default and set the1345 value as the boundary. See the --attach option in1346 linkgit:git-format-patch[1].13471348format.from::1349 Provides the default value for the `--from` option to format-patch.1350 Accepts a boolean value, or a name and email address. If false,1351 format-patch defaults to `--no-from`, using commit authors directly in1352 the "From:" field of patch mails. If true, format-patch defaults to1353 `--from`, using your committer identity in the "From:" field of patch1354 mails and including a "From:" field in the body of the patch mail if1355 different. If set to a non-boolean value, format-patch uses that1356 value instead of your committer identity. Defaults to false.13571358format.numbered::1359 A boolean which can enable or disable sequence numbers in patch1360 subjects. It defaults to "auto" which enables it only if there1361 is more than one patch. It can be enabled or disabled for all1362 messages by setting it to "true" or "false". See --numbered1363 option in linkgit:git-format-patch[1].13641365format.headers::1366 Additional email headers to include in a patch to be submitted1367 by mail. See linkgit:git-format-patch[1].13681369format.to::1370format.cc::1371 Additional recipients to include in a patch to be submitted1372 by mail. See the --to and --cc options in1373 linkgit:git-format-patch[1].13741375format.subjectPrefix::1376 The default for format-patch is to output files with the '[PATCH]'1377 subject prefix. Use this variable to change that prefix.13781379format.signature::1380 The default for format-patch is to output a signature containing1381 the Git version number. Use this variable to change that default.1382 Set this variable to the empty string ("") to suppress1383 signature generation.13841385format.signatureFile::1386 Works just like format.signature except the contents of the1387 file specified by this variable will be used as the signature.13881389format.suffix::1390 The default for format-patch is to output files with the suffix1391 `.patch`. Use this variable to change that suffix (make sure to1392 include the dot if you want it).13931394format.pretty::1395 The default pretty format for log/show/whatchanged command,1396 See linkgit:git-log[1], linkgit:git-show[1],1397 linkgit:git-whatchanged[1].13981399format.thread::1400 The default threading style for 'git format-patch'. Can be1401 a boolean value, or `shallow` or `deep`. `shallow` threading1402 makes every mail a reply to the head of the series,1403 where the head is chosen from the cover letter, the1404 `--in-reply-to`, and the first patch mail, in this order.1405 `deep` threading makes every mail a reply to the previous one.1406 A true boolean value is the same as `shallow`, and a false1407 value disables threading.14081409format.signOff::1410 A boolean value which lets you enable the `-s/--signoff` option of1411 format-patch by default. *Note:* Adding the Signed-off-by: line to a1412 patch should be a conscious act and means that you certify you have1413 the rights to submit this work under the same open source license.1414 Please see the 'SubmittingPatches' document for further discussion.14151416format.coverLetter::1417 A boolean that controls whether to generate a cover-letter when1418 format-patch is invoked, but in addition can be set to "auto", to1419 generate a cover-letter only when there's more than one patch.14201421format.outputDirectory::1422 Set a custom directory to store the resulting files instead of the1423 current working directory.14241425format.useAutoBase::1426 A boolean value which lets you enable the `--base=auto` option of1427 format-patch by default.14281429filter.<driver>.clean::1430 The command which is used to convert the content of a worktree1431 file to a blob upon checkin. See linkgit:gitattributes[5] for1432 details.14331434filter.<driver>.smudge::1435 The command which is used to convert the content of a blob1436 object to a worktree file upon checkout. See1437 linkgit:gitattributes[5] for details.14381439fsck.<msg-id>::1440 Allows overriding the message type (error, warn or ignore) of a1441 specific message ID such as `missingEmail`.1442+1443For convenience, fsck prefixes the error/warning with the message ID,1444e.g. "missingEmail: invalid author/committer line - missing email" means1445that setting `fsck.missingEmail = ignore` will hide that issue.1446+1447This feature is intended to support working with legacy repositories1448which cannot be repaired without disruptive changes.14491450fsck.skipList::1451 The path to a sorted list of object names (i.e. one SHA-1 per1452 line) that are known to be broken in a non-fatal way and should1453 be ignored. This feature is useful when an established project1454 should be accepted despite early commits containing errors that1455 can be safely ignored such as invalid committer email addresses.1456 Note: corrupt objects cannot be skipped with this setting.14571458gc.aggressiveDepth::1459 The depth parameter used in the delta compression1460 algorithm used by 'git gc --aggressive'. This defaults1461 to 50.14621463gc.aggressiveWindow::1464 The window size parameter used in the delta compression1465 algorithm used by 'git gc --aggressive'. This defaults1466 to 250.14671468gc.auto::1469 When there are approximately more than this many loose1470 objects in the repository, `git gc --auto` will pack them.1471 Some Porcelain commands use this command to perform a1472 light-weight garbage collection from time to time. The1473 default value is 6700. Setting this to 0 disables it.14741475gc.autoPackLimit::1476 When there are more than this many packs that are not1477 marked with `*.keep` file in the repository, `git gc1478 --auto` consolidates them into one larger pack. The1479 default value is 50. Setting this to 0 disables it.14801481gc.autoDetach::1482 Make `git gc --auto` return immediately and run in background1483 if the system supports it. Default is true.14841485gc.logExpiry::1486 If the file gc.log exists, then `git gc --auto` won't run1487 unless that file is more than 'gc.logExpiry' old. Default is1488 "1.day". See `gc.pruneExpire` for more ways to specify its1489 value.14901491gc.packRefs::1492 Running `git pack-refs` in a repository renders it1493 unclonable by Git versions prior to 1.5.1.2 over dumb1494 transports such as HTTP. This variable determines whether1495 'git gc' runs `git pack-refs`. This can be set to `notbare`1496 to enable it within all non-bare repos or it can be set to a1497 boolean value. The default is `true`.14981499gc.pruneExpire::1500 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1501 Override the grace period with this config variable. The value1502 "now" may be used to disable this grace period and always prune1503 unreachable objects immediately, or "never" may be used to1504 suppress pruning. This feature helps prevent corruption when1505 'git gc' runs concurrently with another process writing to the1506 repository; see the "NOTES" section of linkgit:git-gc[1].15071508gc.worktreePruneExpire::1509 When 'git gc' is run, it calls1510 'git worktree prune --expire 3.months.ago'.1511 This config variable can be used to set a different grace1512 period. The value "now" may be used to disable the grace1513 period and prune `$GIT_DIR/worktrees` immediately, or "never"1514 may be used to suppress pruning.15151516gc.reflogExpire::1517gc.<pattern>.reflogExpire::1518 'git reflog expire' removes reflog entries older than1519 this time; defaults to 90 days. The value "now" expires all1520 entries immediately, and "never" suppresses expiration1521 altogether. With "<pattern>" (e.g.1522 "refs/stash") in the middle the setting applies only to1523 the refs that match the <pattern>.15241525gc.reflogExpireUnreachable::1526gc.<pattern>.reflogExpireUnreachable::1527 'git reflog expire' removes reflog entries older than1528 this time and are not reachable from the current tip;1529 defaults to 30 days. The value "now" expires all entries1530 immediately, and "never" suppresses expiration altogether.1531 With "<pattern>" (e.g. "refs/stash")1532 in the middle, the setting applies only to the refs that1533 match the <pattern>.15341535gc.rerereResolved::1536 Records of conflicted merge you resolved earlier are1537 kept for this many days when 'git rerere gc' is run.1538 The default is 60 days. See linkgit:git-rerere[1].15391540gc.rerereUnresolved::1541 Records of conflicted merge you have not resolved are1542 kept for this many days when 'git rerere gc' is run.1543 The default is 15 days. See linkgit:git-rerere[1].15441545gitcvs.commitMsgAnnotation::1546 Append this string to each commit message. Set to empty string1547 to disable this feature. Defaults to "via git-CVS emulator".15481549gitcvs.enabled::1550 Whether the CVS server interface is enabled for this repository.1551 See linkgit:git-cvsserver[1].15521553gitcvs.logFile::1554 Path to a log file where the CVS server interface well... logs1555 various stuff. See linkgit:git-cvsserver[1].15561557gitcvs.usecrlfattr::1558 If true, the server will look up the end-of-line conversion1559 attributes for files to determine the `-k` modes to use. If1560 the attributes force Git to treat a file as text,1561 the `-k` mode will be left blank so CVS clients will1562 treat it as text. If they suppress text conversion, the file1563 will be set with '-kb' mode, which suppresses any newline munging1564 the client might otherwise do. If the attributes do not allow1565 the file type to be determined, then `gitcvs.allBinary` is1566 used. See linkgit:gitattributes[5].15671568gitcvs.allBinary::1569 This is used if `gitcvs.usecrlfattr` does not resolve1570 the correct '-kb' mode to use. If true, all1571 unresolved files are sent to the client in1572 mode '-kb'. This causes the client to treat them1573 as binary files, which suppresses any newline munging it1574 otherwise might do. Alternatively, if it is set to "guess",1575 then the contents of the file are examined to decide if1576 it is binary, similar to `core.autocrlf`.15771578gitcvs.dbName::1579 Database used by git-cvsserver to cache revision information1580 derived from the Git repository. The exact meaning depends on the1581 used database driver, for SQLite (which is the default driver) this1582 is a filename. Supports variable substitution (see1583 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1584 Default: '%Ggitcvs.%m.sqlite'15851586gitcvs.dbDriver::1587 Used Perl DBI driver. You can specify any available driver1588 for this here, but it might not work. git-cvsserver is tested1589 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1590 reported *not* to work with 'DBD::mysql'. Experimental feature.1591 May not contain double colons (`:`). Default: 'SQLite'.1592 See linkgit:git-cvsserver[1].15931594gitcvs.dbUser, gitcvs.dbPass::1595 Database user and password. Only useful if setting `gitcvs.dbDriver`,1596 since SQLite has no concept of database users and/or passwords.1597 'gitcvs.dbUser' supports variable substitution (see1598 linkgit:git-cvsserver[1] for details).15991600gitcvs.dbTableNamePrefix::1601 Database table name prefix. Prepended to the names of any1602 database tables used, allowing a single database to be used1603 for several repositories. Supports variable substitution (see1604 linkgit:git-cvsserver[1] for details). Any non-alphabetic1605 characters will be replaced with underscores.16061607All gitcvs variables except for `gitcvs.usecrlfattr` and1608`gitcvs.allBinary` can also be specified as1609'gitcvs.<access_method>.<varname>' (where 'access_method'1610is one of "ext" and "pserver") to make them apply only for the given1611access method.16121613gitweb.category::1614gitweb.description::1615gitweb.owner::1616gitweb.url::1617 See linkgit:gitweb[1] for description.16181619gitweb.avatar::1620gitweb.blame::1621gitweb.grep::1622gitweb.highlight::1623gitweb.patches::1624gitweb.pickaxe::1625gitweb.remote_heads::1626gitweb.showSizes::1627gitweb.snapshot::1628 See linkgit:gitweb.conf[5] for description.16291630grep.lineNumber::1631 If set to true, enable `-n` option by default.16321633grep.patternType::1634 Set the default matching behavior. Using a value of 'basic', 'extended',1635 'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`,1636 `--fixed-strings`, or `--perl-regexp` option accordingly, while the1637 value 'default' will return to the default matching behavior.16381639grep.extendedRegexp::1640 If set to true, enable `--extended-regexp` option by default. This1641 option is ignored when the `grep.patternType` option is set to a value1642 other than 'default'.16431644grep.threads::1645 Number of grep worker threads to use.1646 See `grep.threads` in linkgit:git-grep[1] for more information.16471648grep.fallbackToNoIndex::1649 If set to true, fall back to git grep --no-index if git grep1650 is executed outside of a git repository. Defaults to false.16511652gpg.program::1653 Use this custom program instead of "`gpg`" found on `$PATH` when1654 making or verifying a PGP signature. The program must support the1655 same command-line interface as GPG, namely, to verify a detached1656 signature, "`gpg --verify $file - <$signature`" is run, and the1657 program is expected to signal a good signature by exiting with1658 code 0, and to generate an ASCII-armored detached signature, the1659 standard input of "`gpg -bsau $key`" is fed with the contents to be1660 signed, and the program is expected to send the result to its1661 standard output.16621663gui.commitMsgWidth::1664 Defines how wide the commit message window is in the1665 linkgit:git-gui[1]. "75" is the default.16661667gui.diffContext::1668 Specifies how many context lines should be used in calls to diff1669 made by the linkgit:git-gui[1]. The default is "5".16701671gui.displayUntracked::1672 Determines if linkgit:git-gui[1] shows untracked files1673 in the file list. The default is "true".16741675gui.encoding::1676 Specifies the default encoding to use for displaying of1677 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1678 It can be overridden by setting the 'encoding' attribute1679 for relevant files (see linkgit:gitattributes[5]).1680 If this option is not set, the tools default to the1681 locale encoding.16821683gui.matchTrackingBranch::1684 Determines if new branches created with linkgit:git-gui[1] should1685 default to tracking remote branches with matching names or1686 not. Default: "false".16871688gui.newBranchTemplate::1689 Is used as suggested name when creating new branches using the1690 linkgit:git-gui[1].16911692gui.pruneDuringFetch::1693 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1694 performing a fetch. The default value is "false".16951696gui.trustmtime::1697 Determines if linkgit:git-gui[1] should trust the file modification1698 timestamp or not. By default the timestamps are not trusted.16991700gui.spellingDictionary::1701 Specifies the dictionary used for spell checking commit messages in1702 the linkgit:git-gui[1]. When set to "none" spell checking is turned1703 off.17041705gui.fastCopyBlame::1706 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1707 location detection. It makes blame significantly faster on huge1708 repositories at the expense of less thorough copy detection.17091710gui.copyBlameThreshold::1711 Specifies the threshold to use in 'git gui blame' original location1712 detection, measured in alphanumeric characters. See the1713 linkgit:git-blame[1] manual for more information on copy detection.17141715gui.blamehistoryctx::1716 Specifies the radius of history context in days to show in1717 linkgit:gitk[1] for the selected commit, when the `Show History1718 Context` menu item is invoked from 'git gui blame'. If this1719 variable is set to zero, the whole history is shown.17201721guitool.<name>.cmd::1722 Specifies the shell command line to execute when the corresponding item1723 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1724 mandatory for every tool. The command is executed from the root of1725 the working directory, and in the environment it receives the name of1726 the tool as `GIT_GUITOOL`, the name of the currently selected file as1727 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1728 the head is detached, 'CUR_BRANCH' is empty).17291730guitool.<name>.needsFile::1731 Run the tool only if a diff is selected in the GUI. It guarantees1732 that 'FILENAME' is not empty.17331734guitool.<name>.noConsole::1735 Run the command silently, without creating a window to display its1736 output.17371738guitool.<name>.noRescan::1739 Don't rescan the working directory for changes after the tool1740 finishes execution.17411742guitool.<name>.confirm::1743 Show a confirmation dialog before actually running the tool.17441745guitool.<name>.argPrompt::1746 Request a string argument from the user, and pass it to the tool1747 through the `ARGS` environment variable. Since requesting an1748 argument implies confirmation, the 'confirm' option has no effect1749 if this is enabled. If the option is set to 'true', 'yes', or '1',1750 the dialog uses a built-in generic prompt; otherwise the exact1751 value of the variable is used.17521753guitool.<name>.revPrompt::1754 Request a single valid revision from the user, and set the1755 `REVISION` environment variable. In other aspects this option1756 is similar to 'argPrompt', and can be used together with it.17571758guitool.<name>.revUnmerged::1759 Show only unmerged branches in the 'revPrompt' subdialog.1760 This is useful for tools similar to merge or rebase, but not1761 for things like checkout or reset.17621763guitool.<name>.title::1764 Specifies the title to use for the prompt dialog. The default1765 is the tool name.17661767guitool.<name>.prompt::1768 Specifies the general prompt string to display at the top of1769 the dialog, before subsections for 'argPrompt' and 'revPrompt'.1770 The default value includes the actual command.17711772help.browser::1773 Specify the browser that will be used to display help in the1774 'web' format. See linkgit:git-help[1].17751776help.format::1777 Override the default help format used by linkgit:git-help[1].1778 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1779 the default. 'web' and 'html' are the same.17801781help.autoCorrect::1782 Automatically correct and execute mistyped commands after1783 waiting for the given number of deciseconds (0.1 sec). If more1784 than one command can be deduced from the entered text, nothing1785 will be executed. If the value of this option is negative,1786 the corrected command will be executed immediately. If the1787 value is 0 - the command will be just shown but not executed.1788 This is the default.17891790help.htmlPath::1791 Specify the path where the HTML documentation resides. File system paths1792 and URLs are supported. HTML pages will be prefixed with this path when1793 help is displayed in the 'web' format. This defaults to the documentation1794 path of your Git installation.17951796http.proxy::1797 Override the HTTP proxy, normally configured using the 'http_proxy',1798 'https_proxy', and 'all_proxy' environment variables (see `curl(1)`). In1799 addition to the syntax understood by curl, it is possible to specify a1800 proxy string with a user name but no password, in which case git will1801 attempt to acquire one in the same way it does for other credentials. See1802 linkgit:gitcredentials[7] for more information. The syntax thus is1803 '[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden1804 on a per-remote basis; see remote.<name>.proxy18051806http.proxyAuthMethod::1807 Set the method with which to authenticate against the HTTP proxy. This1808 only takes effect if the configured proxy string contains a user name part1809 (i.e. is of the form 'user@host' or 'user@host:port'). This can be1810 overridden on a per-remote basis; see `remote.<name>.proxyAuthMethod`.1811 Both can be overridden by the `GIT_HTTP_PROXY_AUTHMETHOD` environment1812 variable. Possible values are:1813+1814--1815* `anyauth` - Automatically pick a suitable authentication method. It is1816 assumed that the proxy answers an unauthenticated request with a 4071817 status code and one or more Proxy-authenticate headers with supported1818 authentication methods. This is the default.1819* `basic` - HTTP Basic authentication1820* `digest` - HTTP Digest authentication; this prevents the password from being1821 transmitted to the proxy in clear text1822* `negotiate` - GSS-Negotiate authentication (compare the --negotiate option1823 of `curl(1)`)1824* `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`)1825--18261827http.emptyAuth::1828 Attempt authentication without seeking a username or password. This1829 can be used to attempt GSS-Negotiate authentication without specifying1830 a username in the URL, as libcurl normally requires a username for1831 authentication.18321833http.delegation::1834 Control GSSAPI credential delegation. The delegation is disabled1835 by default in libcurl since version 7.21.7. Set parameter to tell1836 the server what it is allowed to delegate when it comes to user1837 credentials. Used with GSS/kerberos. Possible values are:1838+1839--1840* `none` - Don't allow any delegation.1841* `policy` - Delegates if and only if the OK-AS-DELEGATE flag is set in the1842 Kerberos service ticket, which is a matter of realm policy.1843* `always` - Unconditionally allow the server to delegate.1844--184518461847http.extraHeader::1848 Pass an additional HTTP header when communicating with a server. If1849 more than one such entry exists, all of them are added as extra1850 headers. To allow overriding the settings inherited from the system1851 config, an empty value will reset the extra headers to the empty list.18521853http.cookieFile::1854 The pathname of a file containing previously stored cookie lines,1855 which should be used1856 in the Git http session, if they match the server. The file format1857 of the file to read cookies from should be plain HTTP headers or1858 the Netscape/Mozilla cookie file format (see `curl(1)`).1859 NOTE that the file specified with http.cookieFile is used only as1860 input unless http.saveCookies is set.18611862http.saveCookies::1863 If set, store cookies received during requests to the file specified by1864 http.cookieFile. Has no effect if http.cookieFile is unset.18651866http.sslVersion::1867 The SSL version to use when negotiating an SSL connection, if you1868 want to force the default. The available and default version1869 depend on whether libcurl was built against NSS or OpenSSL and the1870 particular configuration of the crypto library in use. Internally1871 this sets the 'CURLOPT_SSL_VERSION' option; see the libcurl1872 documentation for more details on the format of this option and1873 for the ssl version supported. Actually the possible values of1874 this option are:18751876 - sslv21877 - sslv31878 - tlsv11879 - tlsv1.01880 - tlsv1.11881 - tlsv1.218821883+1884Can be overridden by the `GIT_SSL_VERSION` environment variable.1885To force git to use libcurl's default ssl version and ignore any1886explicit http.sslversion option, set `GIT_SSL_VERSION` to the1887empty string.18881889http.sslCipherList::1890 A list of SSL ciphers to use when negotiating an SSL connection.1891 The available ciphers depend on whether libcurl was built against1892 NSS or OpenSSL and the particular configuration of the crypto1893 library in use. Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'1894 option; see the libcurl documentation for more details on the format1895 of this list.1896+1897Can be overridden by the `GIT_SSL_CIPHER_LIST` environment variable.1898To force git to use libcurl's default cipher list and ignore any1899explicit http.sslCipherList option, set `GIT_SSL_CIPHER_LIST` to the1900empty string.19011902http.sslVerify::1903 Whether to verify the SSL certificate when fetching or pushing1904 over HTTPS. Can be overridden by the `GIT_SSL_NO_VERIFY` environment1905 variable.19061907http.sslCert::1908 File containing the SSL certificate when fetching or pushing1909 over HTTPS. Can be overridden by the `GIT_SSL_CERT` environment1910 variable.19111912http.sslKey::1913 File containing the SSL private key when fetching or pushing1914 over HTTPS. Can be overridden by the `GIT_SSL_KEY` environment1915 variable.19161917http.sslCertPasswordProtected::1918 Enable Git's password prompt for the SSL certificate. Otherwise1919 OpenSSL will prompt the user, possibly many times, if the1920 certificate or private key is encrypted. Can be overridden by the1921 `GIT_SSL_CERT_PASSWORD_PROTECTED` environment variable.19221923http.sslCAInfo::1924 File containing the certificates to verify the peer with when1925 fetching or pushing over HTTPS. Can be overridden by the1926 `GIT_SSL_CAINFO` environment variable.19271928http.sslCAPath::1929 Path containing files with the CA certificates to verify the peer1930 with when fetching or pushing over HTTPS. Can be overridden1931 by the `GIT_SSL_CAPATH` environment variable.19321933http.pinnedpubkey::1934 Public key of the https service. It may either be the filename of1935 a PEM or DER encoded public key file or a string starting with1936 'sha256//' followed by the base64 encoded sha256 hash of the1937 public key. See also libcurl 'CURLOPT_PINNEDPUBLICKEY'. git will1938 exit with an error if this option is set but not supported by1939 cURL.19401941http.sslTry::1942 Attempt to use AUTH SSL/TLS and encrypted data transfers1943 when connecting via regular FTP protocol. This might be needed1944 if the FTP server requires it for security reasons or you wish1945 to connect securely whenever remote FTP server supports it.1946 Default is false since it might trigger certificate verification1947 errors on misconfigured servers.19481949http.maxRequests::1950 How many HTTP requests to launch in parallel. Can be overridden1951 by the `GIT_HTTP_MAX_REQUESTS` environment variable. Default is 5.19521953http.minSessions::1954 The number of curl sessions (counted across slots) to be kept across1955 requests. They will not be ended with curl_easy_cleanup() until1956 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1957 value will be capped at 1. Defaults to 1.19581959http.postBuffer::1960 Maximum size in bytes of the buffer used by smart HTTP1961 transports when POSTing data to the remote system.1962 For requests larger than this buffer size, HTTP/1.1 and1963 Transfer-Encoding: chunked is used to avoid creating a1964 massive pack file locally. Default is 1 MiB, which is1965 sufficient for most requests.19661967http.lowSpeedLimit, http.lowSpeedTime::1968 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1969 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1970 Can be overridden by the `GIT_HTTP_LOW_SPEED_LIMIT` and1971 `GIT_HTTP_LOW_SPEED_TIME` environment variables.19721973http.noEPSV::1974 A boolean which disables using of EPSV ftp command by curl.1975 This can helpful with some "poor" ftp servers which don't1976 support EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV`1977 environment variable. Default is false (curl will use EPSV).19781979http.userAgent::1980 The HTTP USER_AGENT string presented to an HTTP server. The default1981 value represents the version of the client Git such as git/1.7.1.1982 This option allows you to override this value to a more common value1983 such as Mozilla/4.0. This may be necessary, for instance, if1984 connecting through a firewall that restricts HTTP connections to a set1985 of common USER_AGENT strings (but not including those like git/1.7.1).1986 Can be overridden by the `GIT_HTTP_USER_AGENT` environment variable.19871988http.followRedirects::1989 Whether git should follow HTTP redirects. If set to `true`, git1990 will transparently follow any redirect issued by a server it1991 encounters. If set to `false`, git will treat all redirects as1992 errors. If set to `initial`, git will follow redirects only for1993 the initial request to a remote, but not for subsequent1994 follow-up HTTP requests. Since git uses the redirected URL as1995 the base for the follow-up requests, this is generally1996 sufficient. The default is `initial`.19971998http.<url>.*::1999 Any of the http.* options above can be applied selectively to some URLs.2000 For a config key to match a URL, each element of the config key is2001 compared to that of the URL, in the following order:2002+2003--2004. Scheme (e.g., `https` in `https://example.com/`). This field2005 must match exactly between the config key and the URL.20062007. Host/domain name (e.g., `example.com` in `https://example.com/`).2008 This field must match between the config key and the URL. It is2009 possible to specify a `*` as part of the host name to match all subdomains2010 at this level. `https://*.example.com/` for example would match2011 `https://foo.example.com/`, but not `https://foo.bar.example.com/`.20122013. Port number (e.g., `8080` in `http://example.com:8080/`).2014 This field must match exactly between the config key and the URL.2015 Omitted port numbers are automatically converted to the correct2016 default for the scheme before matching.20172018. Path (e.g., `repo.git` in `https://example.com/repo.git`). The2019 path field of the config key must match the path field of the URL2020 either exactly or as a prefix of slash-delimited path elements. This means2021 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only2022 match on a slash (`/`) boundary. Longer matches take precedence (so a config2023 key with path `foo/bar` is a better match to URL path `foo/bar` than a config2024 key with just path `foo/`).20252026. User name (e.g., `user` in `https://user@example.com/repo.git`). If2027 the config key has a user name it must match the user name in the2028 URL exactly. If the config key does not have a user name, that2029 config key will match a URL with any user name (including none),2030 but at a lower precedence than a config key with a user name.2031--2032+2033The list above is ordered by decreasing precedence; a URL that matches2034a config key's path is preferred to one that matches its user name. For example,2035if the URL is `https://user@example.com/foo/bar` a config key match of2036`https://example.com/foo` will be preferred over a config key match of2037`https://user@example.com`.2038+2039All URLs are normalized before attempting any matching (the password part,2040if embedded in the URL, is always ignored for matching purposes) so that2041equivalent URLs that are simply spelled differently will match properly.2042Environment variable settings always override any matches. The URLs that are2043matched against are those given directly to Git commands. This means any URLs2044visited as a result of a redirection do not participate in matching.20452046ssh.variant::2047 Depending on the value of the environment variables `GIT_SSH` or2048 `GIT_SSH_COMMAND`, or the config setting `core.sshCommand`, Git2049 auto-detects whether to adjust its command-line parameters for use2050 with plink or tortoiseplink, as opposed to the default (OpenSSH).2051+2052The config variable `ssh.variant` can be set to override this auto-detection;2053valid values are `ssh`, `plink`, `putty` or `tortoiseplink`. Any other value2054will be treated as normal ssh. This setting can be overridden via the2055environment variable `GIT_SSH_VARIANT`.20562057i18n.commitEncoding::2058 Character encoding the commit messages are stored in; Git itself2059 does not care per se, but this information is necessary e.g. when2060 importing commits from emails or in the gitk graphical history2061 browser (and possibly at other places in the future or in other2062 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.20632064i18n.logOutputEncoding::2065 Character encoding the commit messages are converted to when2066 running 'git log' and friends.20672068imap::2069 The configuration variables in the 'imap' section are described2070 in linkgit:git-imap-send[1].20712072index.version::2073 Specify the version with which new index files should be2074 initialized. This does not affect existing repositories.20752076init.templateDir::2077 Specify the directory from which templates will be copied.2078 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)20792080instaweb.browser::2081 Specify the program that will be used to browse your working2082 repository in gitweb. See linkgit:git-instaweb[1].20832084instaweb.httpd::2085 The HTTP daemon command-line to start gitweb on your working2086 repository. See linkgit:git-instaweb[1].20872088instaweb.local::2089 If true the web server started by linkgit:git-instaweb[1] will2090 be bound to the local IP (127.0.0.1).20912092instaweb.modulePath::2093 The default module path for linkgit:git-instaweb[1] to use2094 instead of /usr/lib/apache2/modules. Only used if httpd2095 is Apache.20962097instaweb.port::2098 The port number to bind the gitweb httpd to. See2099 linkgit:git-instaweb[1].21002101interactive.singleKey::2102 In interactive commands, allow the user to provide one-letter2103 input with a single key (i.e., without hitting enter).2104 Currently this is used by the `--patch` mode of2105 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],2106 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this2107 setting is silently ignored if portable keystroke input2108 is not available; requires the Perl module Term::ReadKey.21092110interactive.diffFilter::2111 When an interactive command (such as `git add --patch`) shows2112 a colorized diff, git will pipe the diff through the shell2113 command defined by this configuration variable. The command may2114 mark up the diff further for human consumption, provided that it2115 retains a one-to-one correspondence with the lines in the2116 original diff. Defaults to disabled (no filtering).21172118log.abbrevCommit::2119 If true, makes linkgit:git-log[1], linkgit:git-show[1], and2120 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may2121 override this option with `--no-abbrev-commit`.21222123log.date::2124 Set the default date-time mode for the 'log' command.2125 Setting a value for log.date is similar to using 'git log''s2126 `--date` option. See linkgit:git-log[1] for details.21272128log.decorate::2129 Print out the ref names of any commits that are shown by the log2130 command. If 'short' is specified, the ref name prefixes 'refs/heads/',2131 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is2132 specified, the full ref name (including prefix) will be printed.2133 If 'auto' is specified, then if the output is going to a terminal,2134 the ref names are shown as if 'short' were given, otherwise no ref2135 names are shown. This is the same as the `--decorate` option2136 of the `git log`.21372138log.follow::2139 If `true`, `git log` will act as if the `--follow` option was used when2140 a single <path> is given. This has the same limitations as `--follow`,2141 i.e. it cannot be used to follow multiple files and does not work well2142 on non-linear history.21432144log.graphColors::2145 A list of colors, separated by commas, that can be used to draw2146 history lines in `git log --graph`.21472148log.showRoot::2149 If true, the initial commit will be shown as a big creation event.2150 This is equivalent to a diff against an empty tree.2151 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which2152 normally hide the root commit will now show it. True by default.21532154log.mailmap::2155 If true, makes linkgit:git-log[1], linkgit:git-show[1], and2156 linkgit:git-whatchanged[1] assume `--use-mailmap`.21572158mailinfo.scissors::2159 If true, makes linkgit:git-mailinfo[1] (and therefore2160 linkgit:git-am[1]) act by default as if the --scissors option2161 was provided on the command-line. When active, this features2162 removes everything from the message body before a scissors2163 line (i.e. consisting mainly of ">8", "8<" and "-").21642165mailmap.file::2166 The location of an augmenting mailmap file. The default2167 mailmap, located in the root of the repository, is loaded2168 first, then the mailmap file pointed to by this variable.2169 The location of the mailmap file may be in a repository2170 subdirectory, or somewhere outside of the repository itself.2171 See linkgit:git-shortlog[1] and linkgit:git-blame[1].21722173mailmap.blob::2174 Like `mailmap.file`, but consider the value as a reference to a2175 blob in the repository. If both `mailmap.file` and2176 `mailmap.blob` are given, both are parsed, with entries from2177 `mailmap.file` taking precedence. In a bare repository, this2178 defaults to `HEAD:.mailmap`. In a non-bare repository, it2179 defaults to empty.21802181man.viewer::2182 Specify the programs that may be used to display help in the2183 'man' format. See linkgit:git-help[1].21842185man.<tool>.cmd::2186 Specify the command to invoke the specified man viewer. The2187 specified command is evaluated in shell with the man page2188 passed as argument. (See linkgit:git-help[1].)21892190man.<tool>.path::2191 Override the path for the given tool that may be used to2192 display help in the 'man' format. See linkgit:git-help[1].21932194include::merge-config.txt[]21952196mergetool.<tool>.path::2197 Override the path for the given tool. This is useful in case2198 your tool is not in the PATH.21992200mergetool.<tool>.cmd::2201 Specify the command to invoke the specified merge tool. The2202 specified command is evaluated in shell with the following2203 variables available: 'BASE' is the name of a temporary file2204 containing the common base of the files to be merged, if available;2205 'LOCAL' is the name of a temporary file containing the contents of2206 the file on the current branch; 'REMOTE' is the name of a temporary2207 file containing the contents of the file from the branch being2208 merged; 'MERGED' contains the name of the file to which the merge2209 tool should write the results of a successful merge.22102211mergetool.<tool>.trustExitCode::2212 For a custom merge command, specify whether the exit code of2213 the merge command can be used to determine whether the merge was2214 successful. If this is not set to true then the merge target file2215 timestamp is checked and the merge assumed to have been successful2216 if the file has been updated, otherwise the user is prompted to2217 indicate the success of the merge.22182219mergetool.meld.hasOutput::2220 Older versions of `meld` do not support the `--output` option.2221 Git will attempt to detect whether `meld` supports `--output`2222 by inspecting the output of `meld --help`. Configuring2223 `mergetool.meld.hasOutput` will make Git skip these checks and2224 use the configured value instead. Setting `mergetool.meld.hasOutput`2225 to `true` tells Git to unconditionally use the `--output` option,2226 and `false` avoids using `--output`.22272228mergetool.keepBackup::2229 After performing a merge, the original file with conflict markers2230 can be saved as a file with a `.orig` extension. If this variable2231 is set to `false` then this file is not preserved. Defaults to2232 `true` (i.e. keep the backup files).22332234mergetool.keepTemporaries::2235 When invoking a custom merge tool, Git uses a set of temporary2236 files to pass to the tool. If the tool returns an error and this2237 variable is set to `true`, then these temporary files will be2238 preserved, otherwise they will be removed after the tool has2239 exited. Defaults to `false`.22402241mergetool.writeToTemp::2242 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of2243 conflicting files in the worktree by default. Git will attempt2244 to use a temporary directory for these files when set `true`.2245 Defaults to `false`.22462247mergetool.prompt::2248 Prompt before each invocation of the merge resolution program.22492250notes.mergeStrategy::2251 Which merge strategy to choose by default when resolving notes2252 conflicts. Must be one of `manual`, `ours`, `theirs`, `union`, or2253 `cat_sort_uniq`. Defaults to `manual`. See "NOTES MERGE STRATEGIES"2254 section of linkgit:git-notes[1] for more information on each strategy.22552256notes.<name>.mergeStrategy::2257 Which merge strategy to choose when doing a notes merge into2258 refs/notes/<name>. This overrides the more general2259 "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES" section in2260 linkgit:git-notes[1] for more information on the available strategies.22612262notes.displayRef::2263 The (fully qualified) refname from which to show notes when2264 showing commit messages. The value of this variable can be set2265 to a glob, in which case notes from all matching refs will be2266 shown. You may also specify this configuration variable2267 several times. A warning will be issued for refs that do not2268 exist, but a glob that does not match any refs is silently2269 ignored.2270+2271This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`2272environment variable, which must be a colon separated list of refs or2273globs.2274+2275The effective value of "core.notesRef" (possibly overridden by2276GIT_NOTES_REF) is also implicitly added to the list of refs to be2277displayed.22782279notes.rewrite.<command>::2280 When rewriting commits with <command> (currently `amend` or2281 `rebase`) and this variable is set to `true`, Git2282 automatically copies your notes from the original to the2283 rewritten commit. Defaults to `true`, but see2284 "notes.rewriteRef" below.22852286notes.rewriteMode::2287 When copying notes during a rewrite (see the2288 "notes.rewrite.<command>" option), determines what to do if2289 the target commit already has a note. Must be one of2290 `overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`.2291 Defaults to `concatenate`.2292+2293This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`2294environment variable.22952296notes.rewriteRef::2297 When copying notes during a rewrite, specifies the (fully2298 qualified) ref whose notes should be copied. The ref may be a2299 glob, in which case notes in all matching refs will be copied.2300 You may also specify this configuration several times.2301+2302Does not have a default value; you must configure this variable to2303enable note rewriting. Set it to `refs/notes/commits` to enable2304rewriting for the default commit notes.2305+2306This setting can be overridden with the `GIT_NOTES_REWRITE_REF`2307environment variable, which must be a colon separated list of refs or2308globs.23092310pack.window::2311 The size of the window used by linkgit:git-pack-objects[1] when no2312 window size is given on the command line. Defaults to 10.23132314pack.depth::2315 The maximum delta depth used by linkgit:git-pack-objects[1] when no2316 maximum depth is given on the command line. Defaults to 50.23172318pack.windowMemory::2319 The maximum size of memory that is consumed by each thread2320 in linkgit:git-pack-objects[1] for pack window memory when2321 no limit is given on the command line. The value can be2322 suffixed with "k", "m", or "g". When left unconfigured (or2323 set explicitly to 0), there will be no limit.23242325pack.compression::2326 An integer -1..9, indicating the compression level for objects2327 in a pack file. -1 is the zlib default. 0 means no2328 compression, and 1..9 are various speed/size tradeoffs, 9 being2329 slowest. If not set, defaults to core.compression. If that is2330 not set, defaults to -1, the zlib default, which is "a default2331 compromise between speed and compression (currently equivalent2332 to level 6)."2333+2334Note that changing the compression level will not automatically recompress2335all existing objects. You can force recompression by passing the -F option2336to linkgit:git-repack[1].23372338pack.deltaCacheSize::2339 The maximum memory in bytes used for caching deltas in2340 linkgit:git-pack-objects[1] before writing them out to a pack.2341 This cache is used to speed up the writing object phase by not2342 having to recompute the final delta result once the best match2343 for all objects is found. Repacking large repositories on machines2344 which are tight with memory might be badly impacted by this though,2345 especially if this cache pushes the system into swapping.2346 A value of 0 means no limit. The smallest size of 1 byte may be2347 used to virtually disable this cache. Defaults to 256 MiB.23482349pack.deltaCacheLimit::2350 The maximum size of a delta, that is cached in2351 linkgit:git-pack-objects[1]. This cache is used to speed up the2352 writing object phase by not having to recompute the final delta2353 result once the best match for all objects is found. Defaults to 1000.23542355pack.threads::2356 Specifies the number of threads to spawn when searching for best2357 delta matches. This requires that linkgit:git-pack-objects[1]2358 be compiled with pthreads otherwise this option is ignored with a2359 warning. This is meant to reduce packing time on multiprocessor2360 machines. The required amount of memory for the delta search window2361 is however multiplied by the number of threads.2362 Specifying 0 will cause Git to auto-detect the number of CPU's2363 and set the number of threads accordingly.23642365pack.indexVersion::2366 Specify the default pack index version. Valid values are 1 for2367 legacy pack index used by Git versions prior to 1.5.2, and 2 for2368 the new pack index with capabilities for packs larger than 4 GB2369 as well as proper protection against the repacking of corrupted2370 packs. Version 2 is the default. Note that version 2 is enforced2371 and this config option ignored whenever the corresponding pack is2372 larger than 2 GB.2373+2374If you have an old Git that does not understand the version 2 `*.idx` file,2375cloning or fetching over a non native protocol (e.g. "http")2376that will copy both `*.pack` file and corresponding `*.idx` file from the2377other side may give you a repository that cannot be accessed with your2378older version of Git. If the `*.pack` file is smaller than 2 GB, however,2379you can use linkgit:git-index-pack[1] on the *.pack file to regenerate2380the `*.idx` file.23812382pack.packSizeLimit::2383 The maximum size of a pack. This setting only affects2384 packing to a file when repacking, i.e. the git:// protocol2385 is unaffected. It can be overridden by the `--max-pack-size`2386 option of linkgit:git-repack[1]. Reaching this limit results2387 in the creation of multiple packfiles; which in turn prevents2388 bitmaps from being created.2389 The minimum size allowed is limited to 1 MiB.2390 The default is unlimited.2391 Common unit suffixes of 'k', 'm', or 'g' are2392 supported.23932394pack.useBitmaps::2395 When true, git will use pack bitmaps (if available) when packing2396 to stdout (e.g., during the server side of a fetch). Defaults to2397 true. You should not generally need to turn this off unless2398 you are debugging pack bitmaps.23992400pack.writeBitmaps (deprecated)::2401 This is a deprecated synonym for `repack.writeBitmaps`.24022403pack.writeBitmapHashCache::2404 When true, git will include a "hash cache" section in the bitmap2405 index (if one is written). This cache can be used to feed git's2406 delta heuristics, potentially leading to better deltas between2407 bitmapped and non-bitmapped objects (e.g., when serving a fetch2408 between an older, bitmapped pack and objects that have been2409 pushed since the last gc). The downside is that it consumes 42410 bytes per object of disk space, and that JGit's bitmap2411 implementation does not understand it, causing it to complain if2412 Git and JGit are used on the same repository. Defaults to false.24132414pager.<cmd>::2415 If the value is boolean, turns on or off pagination of the2416 output of a particular Git subcommand when writing to a tty.2417 Otherwise, turns on pagination for the subcommand using the2418 pager specified by the value of `pager.<cmd>`. If `--paginate`2419 or `--no-pager` is specified on the command line, it takes2420 precedence over this option. To disable pagination for all2421 commands, set `core.pager` or `GIT_PAGER` to `cat`.24222423pretty.<name>::2424 Alias for a --pretty= format string, as specified in2425 linkgit:git-log[1]. Any aliases defined here can be used just2426 as the built-in pretty formats could. For example,2427 running `git config pretty.changelog "format:* %H %s"`2428 would cause the invocation `git log --pretty=changelog`2429 to be equivalent to running `git log "--pretty=format:* %H %s"`.2430 Note that an alias with the same name as a built-in format2431 will be silently ignored.24322433protocol.allow::2434 If set, provide a user defined default policy for all protocols which2435 don't explicitly have a policy (`protocol.<name>.allow`). By default,2436 if unset, known-safe protocols (http, https, git, ssh, file) have a2437 default policy of `always`, known-dangerous protocols (ext) have a2438 default policy of `never`, and all other protocols have a default2439 policy of `user`. Supported policies:2440+2441--24422443* `always` - protocol is always able to be used.24442445* `never` - protocol is never able to be used.24462447* `user` - protocol is only able to be used when `GIT_PROTOCOL_FROM_USER` is2448 either unset or has a value of 1. This policy should be used when you want a2449 protocol to be directly usable by the user but don't want it used by commands which2450 execute clone/fetch/push commands without user input, e.g. recursive2451 submodule initialization.24522453--24542455protocol.<name>.allow::2456 Set a policy to be used by protocol `<name>` with clone/fetch/push2457 commands. See `protocol.allow` above for the available policies.2458+2459The protocol names currently used by git are:2460+2461--2462 - `file`: any local file-based path (including `file://` URLs,2463 or local paths)24642465 - `git`: the anonymous git protocol over a direct TCP2466 connection (or proxy, if configured)24672468 - `ssh`: git over ssh (including `host:path` syntax,2469 `ssh://`, etc).24702471 - `http`: git over http, both "smart http" and "dumb http".2472 Note that this does _not_ include `https`; if you want to configure2473 both, you must do so individually.24742475 - any external helpers are named by their protocol (e.g., use2476 `hg` to allow the `git-remote-hg` helper)2477--24782479pull.ff::2480 By default, Git does not create an extra merge commit when merging2481 a commit that is a descendant of the current commit. Instead, the2482 tip of the current branch is fast-forwarded. When set to `false`,2483 this variable tells Git to create an extra merge commit in such2484 a case (equivalent to giving the `--no-ff` option from the command2485 line). When set to `only`, only such fast-forward merges are2486 allowed (equivalent to giving the `--ff-only` option from the2487 command line). This setting overrides `merge.ff` when pulling.24882489pull.rebase::2490 When true, rebase branches on top of the fetched branch, instead2491 of merging the default branch from the default remote when "git2492 pull" is run. See "branch.<name>.rebase" for setting this on a2493 per-branch basis.2494+2495When preserve, also pass `--preserve-merges` along to 'git rebase'2496so that locally committed merge commits will not be flattened2497by running 'git pull'.2498+2499When the value is `interactive`, the rebase is run in interactive mode.2500+2501*NOTE*: this is a possibly dangerous operation; do *not* use2502it unless you understand the implications (see linkgit:git-rebase[1]2503for details).25042505pull.octopus::2506 The default merge strategy to use when pulling multiple branches2507 at once.25082509pull.twohead::2510 The default merge strategy to use when pulling a single branch.25112512push.default::2513 Defines the action `git push` should take if no refspec is2514 explicitly given. Different values are well-suited for2515 specific workflows; for instance, in a purely central workflow2516 (i.e. the fetch source is equal to the push destination),2517 `upstream` is probably what you want. Possible values are:2518+2519--25202521* `nothing` - do not push anything (error out) unless a refspec is2522 explicitly given. This is primarily meant for people who want to2523 avoid mistakes by always being explicit.25242525* `current` - push the current branch to update a branch with the same2526 name on the receiving end. Works in both central and non-central2527 workflows.25282529* `upstream` - push the current branch back to the branch whose2530 changes are usually integrated into the current branch (which is2531 called `@{upstream}`). This mode only makes sense if you are2532 pushing to the same repository you would normally pull from2533 (i.e. central workflow).25342535* `tracking` - This is a deprecated synonym for `upstream`.25362537* `simple` - in centralized workflow, work like `upstream` with an2538 added safety to refuse to push if the upstream branch's name is2539 different from the local one.2540+2541When pushing to a remote that is different from the remote you normally2542pull from, work as `current`. This is the safest option and is suited2543for beginners.2544+2545This mode has become the default in Git 2.0.25462547* `matching` - push all branches having the same name on both ends.2548 This makes the repository you are pushing to remember the set of2549 branches that will be pushed out (e.g. if you always push 'maint'2550 and 'master' there and no other branches, the repository you push2551 to will have these two branches, and your local 'maint' and2552 'master' will be pushed there).2553+2554To use this mode effectively, you have to make sure _all_ the2555branches you would push out are ready to be pushed out before2556running 'git push', as the whole point of this mode is to allow you2557to push all of the branches in one go. If you usually finish work2558on only one branch and push out the result, while other branches are2559unfinished, this mode is not for you. Also this mode is not2560suitable for pushing into a shared central repository, as other2561people may add new branches there, or update the tip of existing2562branches outside your control.2563+2564This used to be the default, but not since Git 2.0 (`simple` is the2565new default).25662567--25682569push.followTags::2570 If set to true enable `--follow-tags` option by default. You2571 may override this configuration at time of push by specifying2572 `--no-follow-tags`.25732574push.gpgSign::2575 May be set to a boolean value, or the string 'if-asked'. A true2576 value causes all pushes to be GPG signed, as if `--signed` is2577 passed to linkgit:git-push[1]. The string 'if-asked' causes2578 pushes to be signed if the server supports it, as if2579 `--signed=if-asked` is passed to 'git push'. A false value may2580 override a value from a lower-priority config file. An explicit2581 command-line flag always overrides this config option.25822583push.recurseSubmodules::2584 Make sure all submodule commits used by the revisions to be pushed2585 are available on a remote-tracking branch. If the value is 'check'2586 then Git will verify that all submodule commits that changed in the2587 revisions to be pushed are available on at least one remote of the2588 submodule. If any commits are missing, the push will be aborted and2589 exit with non-zero status. If the value is 'on-demand' then all2590 submodules that changed in the revisions to be pushed will be2591 pushed. If on-demand was not able to push all necessary revisions2592 it will also be aborted and exit with non-zero status. If the value2593 is 'no' then default behavior of ignoring submodules when pushing2594 is retained. You may override this configuration at time of push by2595 specifying '--recurse-submodules=check|on-demand|no'.25962597rebase.stat::2598 Whether to show a diffstat of what changed upstream since the last2599 rebase. False by default.26002601rebase.autoSquash::2602 If set to true enable `--autosquash` option by default.26032604rebase.autoStash::2605 When set to true, automatically create a temporary stash2606 before the operation begins, and apply it after the operation2607 ends. This means that you can run rebase on a dirty worktree.2608 However, use with care: the final stash application after a2609 successful rebase might result in non-trivial conflicts.2610 Defaults to false.26112612rebase.missingCommitsCheck::2613 If set to "warn", git rebase -i will print a warning if some2614 commits are removed (e.g. a line was deleted), however the2615 rebase will still proceed. If set to "error", it will print2616 the previous warning and stop the rebase, 'git rebase2617 --edit-todo' can then be used to correct the error. If set to2618 "ignore", no checking is done.2619 To drop a commit without warning or error, use the `drop`2620 command in the todo-list.2621 Defaults to "ignore".26222623rebase.instructionFormat::2624 A format string, as specified in linkgit:git-log[1], to be used for2625 the instruction list during an interactive rebase. The format will automatically2626 have the long commit hash prepended to the format.26272628receive.advertiseAtomic::2629 By default, git-receive-pack will advertise the atomic push2630 capability to its clients. If you don't want to advertise this2631 capability, set this variable to false.26322633receive.advertisePushOptions::2634 By default, git-receive-pack will advertise the push options2635 capability to its clients. If you don't want to advertise this2636 capability, set this variable to false.26372638receive.autogc::2639 By default, git-receive-pack will run "git-gc --auto" after2640 receiving data from git-push and updating refs. You can stop2641 it by setting this variable to false.26422643receive.certNonceSeed::2644 By setting this variable to a string, `git receive-pack`2645 will accept a `git push --signed` and verifies it by using2646 a "nonce" protected by HMAC using this string as a secret2647 key.26482649receive.certNonceSlop::2650 When a `git push --signed` sent a push certificate with a2651 "nonce" that was issued by a receive-pack serving the same2652 repository within this many seconds, export the "nonce"2653 found in the certificate to `GIT_PUSH_CERT_NONCE` to the2654 hooks (instead of what the receive-pack asked the sending2655 side to include). This may allow writing checks in2656 `pre-receive` and `post-receive` a bit easier. Instead of2657 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable2658 that records by how many seconds the nonce is stale to2659 decide if they want to accept the certificate, they only2660 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.26612662receive.fsckObjects::2663 If it is set to true, git-receive-pack will check all received2664 objects. It will abort in the case of a malformed object or a2665 broken link. The result of an abort are only dangling objects.2666 Defaults to false. If not set, the value of `transfer.fsckObjects`2667 is used instead.26682669receive.fsck.<msg-id>::2670 When `receive.fsckObjects` is set to true, errors can be switched2671 to warnings and vice versa by configuring the `receive.fsck.<msg-id>`2672 setting where the `<msg-id>` is the fsck message ID and the value2673 is one of `error`, `warn` or `ignore`. For convenience, fsck prefixes2674 the error/warning with the message ID, e.g. "missingEmail: invalid2675 author/committer line - missing email" means that setting2676 `receive.fsck.missingEmail = ignore` will hide that issue.2677+2678This feature is intended to support working with legacy repositories2679which would not pass pushing when `receive.fsckObjects = true`, allowing2680the host to accept repositories with certain known issues but still catch2681other issues.26822683receive.fsck.skipList::2684 The path to a sorted list of object names (i.e. one SHA-1 per2685 line) that are known to be broken in a non-fatal way and should2686 be ignored. This feature is useful when an established project2687 should be accepted despite early commits containing errors that2688 can be safely ignored such as invalid committer email addresses.2689 Note: corrupt objects cannot be skipped with this setting.26902691receive.keepAlive::2692 After receiving the pack from the client, `receive-pack` may2693 produce no output (if `--quiet` was specified) while processing2694 the pack, causing some networks to drop the TCP connection.2695 With this option set, if `receive-pack` does not transmit2696 any data in this phase for `receive.keepAlive` seconds, it will2697 send a short keepalive packet. The default is 5 seconds; set2698 to 0 to disable keepalives entirely.26992700receive.unpackLimit::2701 If the number of objects received in a push is below this2702 limit then the objects will be unpacked into loose object2703 files. However if the number of received objects equals or2704 exceeds this limit then the received pack will be stored as2705 a pack, after adding any missing delta bases. Storing the2706 pack from a push can make the push operation complete faster,2707 especially on slow filesystems. If not set, the value of2708 `transfer.unpackLimit` is used instead.27092710receive.maxInputSize::2711 If the size of the incoming pack stream is larger than this2712 limit, then git-receive-pack will error out, instead of2713 accepting the pack file. If not set or set to 0, then the size2714 is unlimited.27152716receive.denyDeletes::2717 If set to true, git-receive-pack will deny a ref update that deletes2718 the ref. Use this to prevent such a ref deletion via a push.27192720receive.denyDeleteCurrent::2721 If set to true, git-receive-pack will deny a ref update that2722 deletes the currently checked out branch of a non-bare repository.27232724receive.denyCurrentBranch::2725 If set to true or "refuse", git-receive-pack will deny a ref update2726 to the currently checked out branch of a non-bare repository.2727 Such a push is potentially dangerous because it brings the HEAD2728 out of sync with the index and working tree. If set to "warn",2729 print a warning of such a push to stderr, but allow the push to2730 proceed. If set to false or "ignore", allow such pushes with no2731 message. Defaults to "refuse".2732+2733Another option is "updateInstead" which will update the working2734tree if pushing into the current branch. This option is2735intended for synchronizing working directories when one side is not easily2736accessible via interactive ssh (e.g. a live web site, hence the requirement2737that the working directory be clean). This mode also comes in handy when2738developing inside a VM to test and fix code on different Operating Systems.2739+2740By default, "updateInstead" will refuse the push if the working tree or2741the index have any difference from the HEAD, but the `push-to-checkout`2742hook can be used to customize this. See linkgit:githooks[5].27432744receive.denyNonFastForwards::2745 If set to true, git-receive-pack will deny a ref update which is2746 not a fast-forward. Use this to prevent such an update via a push,2747 even if that push is forced. This configuration variable is2748 set when initializing a shared repository.27492750receive.hideRefs::2751 This variable is the same as `transfer.hideRefs`, but applies2752 only to `receive-pack` (and so affects pushes, but not fetches).2753 An attempt to update or delete a hidden ref by `git push` is2754 rejected.27552756receive.updateServerInfo::2757 If set to true, git-receive-pack will run git-update-server-info2758 after receiving data from git-push and updating refs.27592760receive.shallowUpdate::2761 If set to true, .git/shallow can be updated when new refs2762 require new shallow roots. Otherwise those refs are rejected.27632764remote.pushDefault::2765 The remote to push to by default. Overrides2766 `branch.<name>.remote` for all branches, and is overridden by2767 `branch.<name>.pushRemote` for specific branches.27682769remote.<name>.url::2770 The URL of a remote repository. See linkgit:git-fetch[1] or2771 linkgit:git-push[1].27722773remote.<name>.pushurl::2774 The push URL of a remote repository. See linkgit:git-push[1].27752776remote.<name>.proxy::2777 For remotes that require curl (http, https and ftp), the URL to2778 the proxy to use for that remote. Set to the empty string to2779 disable proxying for that remote.27802781remote.<name>.proxyAuthMethod::2782 For remotes that require curl (http, https and ftp), the method to use for2783 authenticating against the proxy in use (probably set in2784 `remote.<name>.proxy`). See `http.proxyAuthMethod`.27852786remote.<name>.fetch::2787 The default set of "refspec" for linkgit:git-fetch[1]. See2788 linkgit:git-fetch[1].27892790remote.<name>.push::2791 The default set of "refspec" for linkgit:git-push[1]. See2792 linkgit:git-push[1].27932794remote.<name>.mirror::2795 If true, pushing to this remote will automatically behave2796 as if the `--mirror` option was given on the command line.27972798remote.<name>.skipDefaultUpdate::2799 If true, this remote will be skipped by default when updating2800 using linkgit:git-fetch[1] or the `update` subcommand of2801 linkgit:git-remote[1].28022803remote.<name>.skipFetchAll::2804 If true, this remote will be skipped by default when updating2805 using linkgit:git-fetch[1] or the `update` subcommand of2806 linkgit:git-remote[1].28072808remote.<name>.receivepack::2809 The default program to execute on the remote side when pushing. See2810 option --receive-pack of linkgit:git-push[1].28112812remote.<name>.uploadpack::2813 The default program to execute on the remote side when fetching. See2814 option --upload-pack of linkgit:git-fetch-pack[1].28152816remote.<name>.tagOpt::2817 Setting this value to --no-tags disables automatic tag following when2818 fetching from remote <name>. Setting it to --tags will fetch every2819 tag from remote <name>, even if they are not reachable from remote2820 branch heads. Passing these flags directly to linkgit:git-fetch[1] can2821 override this setting. See options --tags and --no-tags of2822 linkgit:git-fetch[1].28232824remote.<name>.vcs::2825 Setting this to a value <vcs> will cause Git to interact with2826 the remote with the git-remote-<vcs> helper.28272828remote.<name>.prune::2829 When set to true, fetching from this remote by default will also2830 remove any remote-tracking references that no longer exist on the2831 remote (as if the `--prune` option was given on the command line).2832 Overrides `fetch.prune` settings, if any.28332834remotes.<group>::2835 The list of remotes which are fetched by "git remote update2836 <group>". See linkgit:git-remote[1].28372838repack.useDeltaBaseOffset::2839 By default, linkgit:git-repack[1] creates packs that use2840 delta-base offset. If you need to share your repository with2841 Git older than version 1.4.4, either directly or via a dumb2842 protocol such as http, then you need to set this option to2843 "false" and repack. Access from old Git versions over the2844 native protocol are unaffected by this option.28452846repack.packKeptObjects::2847 If set to true, makes `git repack` act as if2848 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for2849 details. Defaults to `false` normally, but `true` if a bitmap2850 index is being written (either via `--write-bitmap-index` or2851 `repack.writeBitmaps`).28522853repack.writeBitmaps::2854 When true, git will write a bitmap index when packing all2855 objects to disk (e.g., when `git repack -a` is run). This2856 index can speed up the "counting objects" phase of subsequent2857 packs created for clones and fetches, at the cost of some disk2858 space and extra time spent on the initial repack. This has2859 no effect if multiple packfiles are created.2860 Defaults to false.28612862rerere.autoUpdate::2863 When set to true, `git-rerere` updates the index with the2864 resulting contents after it cleanly resolves conflicts using2865 previously recorded resolution. Defaults to false.28662867rerere.enabled::2868 Activate recording of resolved conflicts, so that identical2869 conflict hunks can be resolved automatically, should they be2870 encountered again. By default, linkgit:git-rerere[1] is2871 enabled if there is an `rr-cache` directory under the2872 `$GIT_DIR`, e.g. if "rerere" was previously used in the2873 repository.28742875sendemail.identity::2876 A configuration identity. When given, causes values in the2877 'sendemail.<identity>' subsection to take precedence over2878 values in the 'sendemail' section. The default identity is2879 the value of `sendemail.identity`.28802881sendemail.smtpEncryption::2882 See linkgit:git-send-email[1] for description. Note that this2883 setting is not subject to the 'identity' mechanism.28842885sendemail.smtpssl (deprecated)::2886 Deprecated alias for 'sendemail.smtpEncryption = ssl'.28872888sendemail.smtpsslcertpath::2889 Path to ca-certificates (either a directory or a single file).2890 Set it to an empty string to disable certificate verification.28912892sendemail.<identity>.*::2893 Identity-specific versions of the 'sendemail.*' parameters2894 found below, taking precedence over those when the this2895 identity is selected, through command-line or2896 `sendemail.identity`.28972898sendemail.aliasesFile::2899sendemail.aliasFileType::2900sendemail.annotate::2901sendemail.bcc::2902sendemail.cc::2903sendemail.ccCmd::2904sendemail.chainReplyTo::2905sendemail.confirm::2906sendemail.envelopeSender::2907sendemail.from::2908sendemail.multiEdit::2909sendemail.signedoffbycc::2910sendemail.smtpPass::2911sendemail.suppresscc::2912sendemail.suppressFrom::2913sendemail.to::2914sendemail.smtpDomain::2915sendemail.smtpServer::2916sendemail.smtpServerPort::2917sendemail.smtpServerOption::2918sendemail.smtpUser::2919sendemail.thread::2920sendemail.transferEncoding::2921sendemail.validate::2922sendemail.xmailer::2923 See linkgit:git-send-email[1] for description.29242925sendemail.signedoffcc (deprecated)::2926 Deprecated alias for `sendemail.signedoffbycc`.29272928showbranch.default::2929 The default set of branches for linkgit:git-show-branch[1].2930 See linkgit:git-show-branch[1].29312932splitIndex.maxPercentChange::2933 When the split index feature is used, this specifies the2934 percent of entries the split index can contain compared to the2935 total number of entries in both the split index and the shared2936 index before a new shared index is written.2937 The value should be between 0 and 100. If the value is 0 then2938 a new shared index is always written, if it is 100 a new2939 shared index is never written.2940 By default the value is 20, so a new shared index is written2941 if the number of entries in the split index would be greater2942 than 20 percent of the total number of entries.2943 See linkgit:git-update-index[1].29442945splitIndex.sharedIndexExpire::2946 When the split index feature is used, shared index files that2947 were not modified since the time this variable specifies will2948 be removed when a new shared index file is created. The value2949 "now" expires all entries immediately, and "never" suppresses2950 expiration altogether.2951 The default value is "2.weeks.ago".2952 Note that a shared index file is considered modified (for the2953 purpose of expiration) each time a new split-index file is2954 either created based on it or read from it.2955 See linkgit:git-update-index[1].29562957status.relativePaths::2958 By default, linkgit:git-status[1] shows paths relative to the2959 current directory. Setting this variable to `false` shows paths2960 relative to the repository root (this was the default for Git2961 prior to v1.5.4).29622963status.short::2964 Set to true to enable --short by default in linkgit:git-status[1].2965 The option --no-short takes precedence over this variable.29662967status.branch::2968 Set to true to enable --branch by default in linkgit:git-status[1].2969 The option --no-branch takes precedence over this variable.29702971status.displayCommentPrefix::2972 If set to true, linkgit:git-status[1] will insert a comment2973 prefix before each output line (starting with2974 `core.commentChar`, i.e. `#` by default). This was the2975 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.2976 Defaults to false.29772978status.showUntrackedFiles::2979 By default, linkgit:git-status[1] and linkgit:git-commit[1] show2980 files which are not currently tracked by Git. Directories which2981 contain only untracked files, are shown with the directory name2982 only. Showing untracked files means that Git needs to lstat() all2983 the files in the whole repository, which might be slow on some2984 systems. So, this variable controls how the commands displays2985 the untracked files. Possible values are:2986+2987--2988* `no` - Show no untracked files.2989* `normal` - Show untracked files and directories.2990* `all` - Show also individual files in untracked directories.2991--2992+2993If this variable is not specified, it defaults to 'normal'.2994This variable can be overridden with the -u|--untracked-files option2995of linkgit:git-status[1] and linkgit:git-commit[1].29962997status.submoduleSummary::2998 Defaults to false.2999 If this is set to a non zero number or true (identical to -1 or an3000 unlimited number), the submodule summary will be enabled and a3001 summary of commits for modified submodules will be shown (see3002 --summary-limit option of linkgit:git-submodule[1]). Please note3003 that the summary output command will be suppressed for all3004 submodules when `diff.ignoreSubmodules` is set to 'all' or only3005 for those submodules where `submodule.<name>.ignore=all`. The only3006 exception to that rule is that status and commit will show staged3007 submodule changes. To3008 also view the summary for ignored submodules you can either use3009 the --ignore-submodules=dirty command-line option or the 'git3010 submodule summary' command, which shows a similar output but does3011 not honor these settings.30123013stash.showPatch::3014 If this is set to true, the `git stash show` command without an3015 option will show the stash in patch form. Defaults to false.3016 See description of 'show' command in linkgit:git-stash[1].30173018stash.showStat::3019 If this is set to true, the `git stash show` command without an3020 option will show diffstat of the stash. Defaults to true.3021 See description of 'show' command in linkgit:git-stash[1].30223023submodule.<name>.url::3024 The URL for a submodule. This variable is copied from the .gitmodules3025 file to the git config via 'git submodule init'. The user can change3026 the configured URL before obtaining the submodule via 'git submodule3027 update'. If neither submodule.<name>.active or submodule.active are3028 set, the presence of this variable is used as a fallback to indicate3029 whether the submodule is of interest to git commands.3030 See linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.30313032submodule.<name>.update::3033 The default update procedure for a submodule. This variable3034 is populated by `git submodule init` from the3035 linkgit:gitmodules[5] file. See description of 'update'3036 command in linkgit:git-submodule[1].30373038submodule.<name>.branch::3039 The remote branch name for a submodule, used by `git submodule3040 update --remote`. Set this option to override the value found in3041 the `.gitmodules` file. See linkgit:git-submodule[1] and3042 linkgit:gitmodules[5] for details.30433044submodule.<name>.fetchRecurseSubmodules::3045 This option can be used to control recursive fetching of this3046 submodule. It can be overridden by using the --[no-]recurse-submodules3047 command-line option to "git fetch" and "git pull".3048 This setting will override that from in the linkgit:gitmodules[5]3049 file.30503051submodule.<name>.ignore::3052 Defines under what circumstances "git status" and the diff family show3053 a submodule as modified. When set to "all", it will never be considered3054 modified (but it will nonetheless show up in the output of status and3055 commit when it has been staged), "dirty" will ignore all changes3056 to the submodules work tree and3057 takes only differences between the HEAD of the submodule and the commit3058 recorded in the superproject into account. "untracked" will additionally3059 let submodules with modified tracked files in their work tree show up.3060 Using "none" (the default when this option is not set) also shows3061 submodules that have untracked files in their work tree as changed.3062 This setting overrides any setting made in .gitmodules for this submodule,3063 both settings can be overridden on the command line by using the3064 "--ignore-submodules" option. The 'git submodule' commands are not3065 affected by this setting.30663067submodule.<name>.active::3068 Boolean value indicating if the submodule is of interest to git3069 commands. This config option takes precedence over the3070 submodule.active config option.30713072submodule.active::3073 A repeated field which contains a pathspec used to match against a3074 submodule's path to determine if the submodule is of interest to git3075 commands.30763077submodule.fetchJobs::3078 Specifies how many submodules are fetched/cloned at the same time.3079 A positive integer allows up to that number of submodules fetched3080 in parallel. A value of 0 will give some reasonable default.3081 If unset, it defaults to 1.30823083submodule.alternateLocation::3084 Specifies how the submodules obtain alternates when submodules are3085 cloned. Possible values are `no`, `superproject`.3086 By default `no` is assumed, which doesn't add references. When the3087 value is set to `superproject` the submodule to be cloned computes3088 its alternates location relative to the superprojects alternate.30893090submodule.alternateErrorStrategy::3091 Specifies how to treat errors with the alternates for a submodule3092 as computed via `submodule.alternateLocation`. Possible values are3093 `ignore`, `info`, `die`. Default is `die`.30943095tag.forceSignAnnotated::3096 A boolean to specify whether annotated tags created should be GPG signed.3097 If `--annotate` is specified on the command line, it takes3098 precedence over this option.30993100tag.sort::3101 This variable controls the sort ordering of tags when displayed by3102 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the3103 value of this variable will be used as the default.31043105tar.umask::3106 This variable can be used to restrict the permission bits of3107 tar archive entries. The default is 0002, which turns off the3108 world write bit. The special value "user" indicates that the3109 archiving user's umask will be used instead. See umask(2) and3110 linkgit:git-archive[1].31113112transfer.fsckObjects::3113 When `fetch.fsckObjects` or `receive.fsckObjects` are3114 not set, the value of this variable is used instead.3115 Defaults to false.31163117transfer.hideRefs::3118 String(s) `receive-pack` and `upload-pack` use to decide which3119 refs to omit from their initial advertisements. Use more than3120 one definition to specify multiple prefix strings. A ref that is3121 under the hierarchies listed in the value of this variable is3122 excluded, and is hidden when responding to `git push` or `git3123 fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for3124 program-specific versions of this config.3125+3126You may also include a `!` in front of the ref name to negate the entry,3127explicitly exposing it, even if an earlier entry marked it as hidden.3128If you have multiple hideRefs values, later entries override earlier ones3129(and entries in more-specific config files override less-specific ones).3130+3131If a namespace is in use, the namespace prefix is stripped from each3132reference before it is matched against `transfer.hiderefs` patterns.3133For example, if `refs/heads/master` is specified in `transfer.hideRefs` and3134the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`3135is omitted from the advertisements but `refs/heads/master` and3136`refs/namespaces/bar/refs/heads/master` are still advertised as so-called3137"have" lines. In order to match refs before stripping, add a `^` in front of3138the ref name. If you combine `!` and `^`, `!` must be specified first.3139+3140Even if you hide refs, a client may still be able to steal the target3141objects via the techniques described in the "SECURITY" section of the3142linkgit:gitnamespaces[7] man page; it's best to keep private data in a3143separate repository.31443145transfer.unpackLimit::3146 When `fetch.unpackLimit` or `receive.unpackLimit` are3147 not set, the value of this variable is used instead.3148 The default value is 100.31493150uploadarchive.allowUnreachable::3151 If true, allow clients to use `git archive --remote` to request3152 any tree, whether reachable from the ref tips or not. See the3153 discussion in the "SECURITY" section of3154 linkgit:git-upload-archive[1] for more details. Defaults to3155 `false`.31563157uploadpack.hideRefs::3158 This variable is the same as `transfer.hideRefs`, but applies3159 only to `upload-pack` (and so affects only fetches, not pushes).3160 An attempt to fetch a hidden ref by `git fetch` will fail. See3161 also `uploadpack.allowTipSHA1InWant`.31623163uploadpack.allowTipSHA1InWant::3164 When `uploadpack.hideRefs` is in effect, allow `upload-pack`3165 to accept a fetch request that asks for an object at the tip3166 of a hidden ref (by default, such a request is rejected).3167 See also `uploadpack.hideRefs`. Even if this is false, a client3168 may be able to steal objects via the techniques described in the3169 "SECURITY" section of the linkgit:gitnamespaces[7] man page; it's3170 best to keep private data in a separate repository.31713172uploadpack.allowReachableSHA1InWant::3173 Allow `upload-pack` to accept a fetch request that asks for an3174 object that is reachable from any ref tip. However, note that3175 calculating object reachability is computationally expensive.3176 Defaults to `false`. Even if this is false, a client may be able3177 to steal objects via the techniques described in the "SECURITY"3178 section of the linkgit:gitnamespaces[7] man page; it's best to3179 keep private data in a separate repository.31803181uploadpack.allowAnySHA1InWant::3182 Allow `upload-pack` to accept a fetch request that asks for any3183 object at all.3184 Defaults to `false`.31853186uploadpack.keepAlive::3187 When `upload-pack` has started `pack-objects`, there may be a3188 quiet period while `pack-objects` prepares the pack. Normally3189 it would output progress information, but if `--quiet` was used3190 for the fetch, `pack-objects` will output nothing at all until3191 the pack data begins. Some clients and networks may consider3192 the server to be hung and give up. Setting this option instructs3193 `upload-pack` to send an empty keepalive packet every3194 `uploadpack.keepAlive` seconds. Setting this option to 03195 disables keepalive packets entirely. The default is 5 seconds.31963197uploadpack.packObjectsHook::3198 If this option is set, when `upload-pack` would run3199 `git pack-objects` to create a packfile for a client, it will3200 run this shell command instead. The `pack-objects` command and3201 arguments it _would_ have run (including the `git pack-objects`3202 at the beginning) are appended to the shell command. The stdin3203 and stdout of the hook are treated as if `pack-objects` itself3204 was run. I.e., `upload-pack` will feed input intended for3205 `pack-objects` to the hook, and expects a completed packfile on3206 stdout.3207+3208Note that this configuration variable is ignored if it is seen in the3209repository-level config (this is a safety measure against fetching from3210untrusted repositories).32113212url.<base>.insteadOf::3213 Any URL that starts with this value will be rewritten to3214 start, instead, with <base>. In cases where some site serves a3215 large number of repositories, and serves them with multiple3216 access methods, and some users need to use different access3217 methods, this feature allows people to specify any of the3218 equivalent URLs and have Git automatically rewrite the URL to3219 the best alternative for the particular user, even for a3220 never-before-seen repository on the site. When more than one3221 insteadOf strings match a given URL, the longest match is used.32223223url.<base>.pushInsteadOf::3224 Any URL that starts with this value will not be pushed to;3225 instead, it will be rewritten to start with <base>, and the3226 resulting URL will be pushed to. In cases where some site serves3227 a large number of repositories, and serves them with multiple3228 access methods, some of which do not allow push, this feature3229 allows people to specify a pull-only URL and have Git3230 automatically use an appropriate URL to push, even for a3231 never-before-seen repository on the site. When more than one3232 pushInsteadOf strings match a given URL, the longest match is3233 used. If a remote has an explicit pushurl, Git will ignore this3234 setting for that remote.32353236user.email::3237 Your email address to be recorded in any newly created commits.3238 Can be overridden by the `GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_EMAIL`, and3239 `EMAIL` environment variables. See linkgit:git-commit-tree[1].32403241user.name::3242 Your full name to be recorded in any newly created commits.3243 Can be overridden by the `GIT_AUTHOR_NAME` and `GIT_COMMITTER_NAME`3244 environment variables. See linkgit:git-commit-tree[1].32453246user.useConfigOnly::3247 Instruct Git to avoid trying to guess defaults for `user.email`3248 and `user.name`, and instead retrieve the values only from the3249 configuration. For example, if you have multiple email addresses3250 and would like to use a different one for each repository, then3251 with this configuration option set to `true` in the global config3252 along with a name, Git will prompt you to set up an email before3253 making new commits in a newly cloned repository.3254 Defaults to `false`.32553256user.signingKey::3257 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the3258 key you want it to automatically when creating a signed tag or3259 commit, you can override the default selection with this variable.3260 This option is passed unchanged to gpg's --local-user parameter,3261 so you may specify a key using any method that gpg supports.32623263versionsort.prereleaseSuffix (deprecated)::3264 Deprecated alias for `versionsort.suffix`. Ignored if3265 `versionsort.suffix` is set.32663267versionsort.suffix::3268 Even when version sort is used in linkgit:git-tag[1], tagnames3269 with the same base version but different suffixes are still sorted3270 lexicographically, resulting e.g. in prerelease tags appearing3271 after the main release (e.g. "1.0-rc1" after "1.0"). This3272 variable can be specified to determine the sorting order of tags3273 with different suffixes.3274+3275By specifying a single suffix in this variable, any tagname containing3276that suffix will appear before the corresponding main release. E.g. if3277the variable is set to "-rc", then all "1.0-rcX" tags will appear before3278"1.0". If specified multiple times, once per suffix, then the order of3279suffixes in the configuration will determine the sorting order of tagnames3280with those suffixes. E.g. if "-pre" appears before "-rc" in the3281configuration, then all "1.0-preX" tags will be listed before any3282"1.0-rcX" tags. The placement of the main release tag relative to tags3283with various suffixes can be determined by specifying the empty suffix3284among those other suffixes. E.g. if the suffixes "-rc", "", "-ck" and3285"-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags3286are listed first, followed by "v4.8", then "v4.8-ckX" and finally3287"v4.8-bfsX".3288+3289If more than one suffixes match the same tagname, then that tagname will3290be sorted according to the suffix which starts at the earliest position in3291the tagname. If more than one different matching suffixes start at3292that earliest position, then that tagname will be sorted according to the3293longest of those suffixes.3294The sorting order between different suffixes is undefined if they are3295in multiple config files.32963297web.browser::3298 Specify a web browser that may be used by some commands.3299 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]3300 may use it.