4 The git configuration file contains a number of variables that affect
5 the git command's behavior. The `.git/config` file in each repository
6 is used to store the configuration for that repository, and
7 `$HOME/.gitconfig` is used to store a per-user configuration as
8 fallback values for the `.git/config` file. The file `/etc/gitconfig`
9 can be used to store a system-wide default configuration.
11 The configuration variables are used by both the git plumbing
12 and the porcelains. The variables are divided into sections, wherein
13 the fully qualified variable name of the variable itself is the last
14 dot-separated segment and the section name is everything before the last
15 dot. The variable names are case-insensitive, allow only alphanumeric
16 characters and `-`, and must start with an alphabetic character. Some
17 variables may appear multiple times.
22 The syntax is fairly flexible and permissive; whitespaces are mostly
23 ignored. The '#' and ';' characters begin comments to the end of line,
24 blank lines are ignored.
26 The file consists of sections and variables. A section begins with
27 the name of the section in square brackets and continues until the next
28 section begins. Section names are not case sensitive. Only alphanumeric
29 characters, `-` and `.` are allowed in section names. Each variable
30 must belong to some section, which means that there must be a section
31 header before the first setting of a variable.
33 Sections can be further divided into subsections. To begin a subsection
34 put its name in double quotes, separated by space from the section name,
35 in the section header, like in the example below:
38 [section "subsection"]
42 Subsection names are case sensitive and can contain any characters except
43 newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
44 respectively). Section headers cannot span multiple
45 lines. Variables may belong directly to a section or to a given subsection.
46 You can have `[section]` if you have `[section "subsection"]`, but you
49 There is also a deprecated `[section.subsection]` syntax. With this
50 syntax, the subsection name is converted to lower-case and is also
51 compared case sensitively. These subsection names follow the same
52 restrictions as section names.
54 All the other lines (and the remainder of the line after the section
55 header) are recognized as setting variables, in the form
56 'name = value'. If there is no equal sign on the line, the entire line
57 is taken as 'name' and the variable is recognized as boolean "true".
58 The variable names are case-insensitive, allow only alphanumeric characters
59 and `-`, and must start with an alphabetic character. There can be more
60 than one value for a given variable; we say then that the variable is
63 Leading and trailing whitespace in a variable value is discarded.
64 Internal whitespace within a variable value is retained verbatim.
66 The values following the equals sign in variable assign are all either
67 a string, an integer, or a boolean. Boolean values may be given as yes/no,
68 1/0, true/false or on/off. Case is not significant in boolean values, when
69 converting value to the canonical form using '--bool' type specifier;
70 'git config' will ensure that the output is "true" or "false".
72 String values may be entirely or partially enclosed in double quotes.
73 You need to enclose variable values in double quotes if you want to
74 preserve leading or trailing whitespace, or if the variable value contains
75 comment characters (i.e. it contains '#' or ';').
76 Double quote `"` and backslash `\` characters in variable values must
77 be escaped: use `\"` for `"` and `\\` for `\`.
79 The following escape sequences (beside `\"` and `\\`) are recognized:
80 `\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
81 and `\b` for backspace (BS). No other char escape sequence, nor octal
82 char sequences are valid.
84 Variable values ending in a `\` are continued on the next line in the
85 customary UNIX fashion.
87 Some variables may require a special value format.
92 You can include one config file from another by setting the special
93 `include.path` variable to the name of the file to be included. The
94 included file is expanded immediately, as if its contents had been
95 found at the location of the include directive. If the value of the
96 `include.path` variable is a relative path, the path is considered to be
97 relative to the configuration file in which the include directive was
98 found. See below for examples.
105 ; Don't trust file modes
110 external = /usr/local/bin/diff-wrapper
115 merge = refs/heads/devel
119 gitProxy="ssh" for "kernel.org"
120 gitProxy=default-proxy ; for the rest
123 path = /path/to/foo.inc ; include by absolute path
124 path = foo ; expand "foo" relative to the current file
129 Note that this list is non-comprehensive and not necessarily complete.
130 For command-specific variables, you will find a more detailed description
131 in the appropriate manual page. You will find a description of non-core
132 porcelain configuration variables in the respective porcelain documentation.
135 These variables control various optional help messages designed to
136 aid new users. All 'advice.*' variables default to 'true', and you
137 can tell Git that you do not need help by setting these to 'false':
141 Advice shown when linkgit:git-push[1] refuses
142 non-fast-forward refs.
144 Directions on how to stage/unstage/add shown in the
145 output of linkgit:git-status[1] and the template shown
146 when writing commit messages.
148 Advice shown when linkgit:git-merge[1] refuses to
149 merge to avoid overwriting local changes.
151 Advices shown by various commands when conflicts
152 prevent the operation from being performed.
154 Advice on how to set your identity configuration when
155 your information is guessed from the system username and
158 Advice shown when you used linkgit:git-checkout[1] to
159 move to the detach HEAD state, to instruct how to create
160 a local branch after the fact.
164 If false, the executable bit differences between the index and
165 the working tree are ignored; useful on broken filesystems like FAT.
166 See linkgit:git-update-index[1].
168 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
169 will probe and set core.fileMode false if appropriate when the
170 repository is created.
173 (Windows-only) If true (which is the default), mark newly-created
174 directories and files whose name starts with a dot as hidden.
175 If 'dotGitOnly', only the .git/ directory is hidden, but no other
176 files starting with a dot.
178 core.ignoreCygwinFSTricks::
179 This option is only used by Cygwin implementation of Git. If false,
180 the Cygwin stat() and lstat() functions are used. This may be useful
181 if your repository consists of a few separate directories joined in
182 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
183 whenever it is possible and falls back to Cygwin functions only to
184 handle symbol links. The native mode is more than twice faster than
185 normal Cygwin l/stat() functions. True by default, unless core.filemode
186 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
187 POSIX emulation is required to support core.filemode.
190 If true, this option enables various workarounds to enable
191 git to work better on filesystems that are not case sensitive,
192 like FAT. For example, if a directory listing finds
193 "makefile" when git expects "Makefile", git will assume
194 it is really the same file, and continue to remember it as
197 The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
198 will probe and set core.ignorecase true if appropriate when the repository
202 If false, the ctime differences between the index and the
203 working tree are ignored; useful when the inode change time
204 is regularly modified by something outside Git (file system
205 crawlers and some backup systems).
206 See linkgit:git-update-index[1]. True by default.
209 The commands that output paths (e.g. 'ls-files',
210 'diff'), when not given the `-z` option, will quote
211 "unusual" characters in the pathname by enclosing the
212 pathname in a double-quote pair and with backslashes the
213 same way strings in C source code are quoted. If this
214 variable is set to false, the bytes higher than 0x80 are
215 not quoted but output as verbatim. Note that double
216 quote, backslash and control characters are always
217 quoted without `-z` regardless of the setting of this
221 Sets the line ending type to use in the working directory for
222 files that have the `text` property set. Alternatives are
223 'lf', 'crlf' and 'native', which uses the platform's native
224 line ending. The default value is `native`. See
225 linkgit:gitattributes[5] for more information on end-of-line
229 If true, makes git check if converting `CRLF` is reversible when
230 end-of-line conversion is active. Git will verify if a command
231 modifies a file in the work tree either directly or indirectly.
232 For example, committing a file followed by checking out the
233 same file should yield the original file in the work tree. If
234 this is not the case for the current setting of
235 `core.autocrlf`, git will reject the file. The variable can
236 be set to "warn", in which case git will only warn about an
237 irreversible conversion but continue the operation.
239 CRLF conversion bears a slight chance of corrupting data.
240 When it is enabled, git will convert CRLF to LF during commit and LF to
241 CRLF during checkout. A file that contains a mixture of LF and
242 CRLF before the commit cannot be recreated by git. For text
243 files this is the right thing to do: it corrects line endings
244 such that we have only LF line endings in the repository.
245 But for binary files that are accidentally classified as text the
246 conversion can corrupt data.
248 If you recognize such corruption early you can easily fix it by
249 setting the conversion type explicitly in .gitattributes. Right
250 after committing you still have the original file in your work
251 tree and this file is not yet corrupted. You can explicitly tell
252 git that this file is binary and git will handle the file
255 Unfortunately, the desired effect of cleaning up text files with
256 mixed line endings and the undesired effect of corrupting binary
257 files cannot be distinguished. In both cases CRLFs are removed
258 in an irreversible way. For text files this is the right thing
259 to do because CRLFs are line endings, while for binary files
260 converting CRLFs corrupts data.
262 Note, this safety check does not mean that a checkout will generate a
263 file identical to the original file for a different setting of
264 `core.eol` and `core.autocrlf`, but only for the current one. For
265 example, a text file with `LF` would be accepted with `core.eol=lf`
266 and could later be checked out with `core.eol=crlf`, in which case the
267 resulting file would contain `CRLF`, although the original file
268 contained `LF`. However, in both work trees the line endings would be
269 consistent, that is either all `LF` or all `CRLF`, but never mixed. A
270 file with mixed line endings would be reported by the `core.safecrlf`
274 Setting this variable to "true" is almost the same as setting
275 the `text` attribute to "auto" on all files except that text
276 files are not guaranteed to be normalized: files that contain
277 `CRLF` in the repository will not be touched. Use this
278 setting if you want to have `CRLF` line endings in your
279 working directory even though the repository does not have
280 normalized line endings. This variable can be set to 'input',
281 in which case no output conversion is performed.
284 If false, symbolic links are checked out as small plain files that
285 contain the link text. linkgit:git-update-index[1] and
286 linkgit:git-add[1] will not change the recorded type to regular
287 file. Useful on filesystems like FAT that do not support
290 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
291 will probe and set core.symlinks false if appropriate when the repository
295 A "proxy command" to execute (as 'command host port') instead
296 of establishing direct connection to the remote server when
297 using the git protocol for fetching. If the variable value is
298 in the "COMMAND for DOMAIN" format, the command is applied only
299 on hostnames ending with the specified domain string. This variable
300 may be set multiple times and is matched in the given order;
301 the first match wins.
303 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
304 (which always applies universally, without the special "for"
307 The special string `none` can be used as the proxy command to
308 specify that no proxy be used for a given domain pattern.
309 This is useful for excluding servers inside a firewall from
310 proxy use, while defaulting to a common proxy for external domains.
313 If true, commands which modify both the working tree and the index
314 will mark the updated paths with the "assume unchanged" bit in the
315 index. These marked files are then assumed to stay unchanged in the
316 working tree, until you mark them otherwise manually - Git will not
317 detect the file changes by lstat() calls. This is useful on systems
318 where those are very slow, such as Microsoft Windows.
319 See linkgit:git-update-index[1].
322 core.preferSymlinkRefs::
323 Instead of the default "symref" format for HEAD
324 and other symbolic reference files, use symbolic links.
325 This is sometimes needed to work with old scripts that
326 expect HEAD to be a symbolic link.
329 If true this repository is assumed to be 'bare' and has no
330 working directory associated with it. If this is the case a
331 number of commands that require a working directory will be
332 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
334 This setting is automatically guessed by linkgit:git-clone[1] or
335 linkgit:git-init[1] when the repository was created. By default a
336 repository that ends in "/.git" is assumed to be not bare (bare =
337 false), while all other repositories are assumed to be bare (bare
341 Set the path to the root of the working tree.
342 This can be overridden by the GIT_WORK_TREE environment
343 variable and the '--work-tree' command line option.
344 The value can be an absolute path or relative to the path to
345 the .git directory, which is either specified by --git-dir
346 or GIT_DIR, or automatically discovered.
347 If --git-dir or GIT_DIR is specified but none of
348 --work-tree, GIT_WORK_TREE and core.worktree is specified,
349 the current working directory is regarded as the top level
350 of your working tree.
352 Note that this variable is honored even when set in a configuration
353 file in a ".git" subdirectory of a directory and its value differs
354 from the latter directory (e.g. "/path/to/.git/config" has
355 core.worktree set to "/different/path"), which is most likely a
356 misconfiguration. Running git commands in the "/path/to" directory will
357 still use "/different/path" as the root of the work tree and can cause
358 confusion unless you know what you are doing (e.g. you are creating a
359 read-only snapshot of the same index to a location different from the
360 repository's usual working tree).
362 core.logAllRefUpdates::
363 Enable the reflog. Updates to a ref <ref> is logged to the file
364 "$GIT_DIR/logs/<ref>", by appending the new and old
365 SHA1, the date/time and the reason of the update, but
366 only when the file exists. If this configuration
367 variable is set to true, missing "$GIT_DIR/logs/<ref>"
368 file is automatically created for branch heads (i.e. under
369 refs/heads/), remote refs (i.e. under refs/remotes/),
370 note refs (i.e. under refs/notes/), and the symbolic ref HEAD.
372 This information can be used to determine what commit
373 was the tip of a branch "2 days ago".
375 This value is true by default in a repository that has
376 a working directory associated with it, and false by
377 default in a bare repository.
379 core.repositoryFormatVersion::
380 Internal variable identifying the repository format and layout
383 core.sharedRepository::
384 When 'group' (or 'true'), the repository is made shareable between
385 several users in a group (making sure all the files and objects are
386 group-writable). When 'all' (or 'world' or 'everybody'), the
387 repository will be readable by all users, additionally to being
388 group-shareable. When 'umask' (or 'false'), git will use permissions
389 reported by umask(2). When '0xxx', where '0xxx' is an octal number,
390 files in the repository will have this mode value. '0xxx' will override
391 user's umask value (whereas the other options will only override
392 requested parts of the user's umask value). Examples: '0660' will make
393 the repo read/write-able for the owner and group, but inaccessible to
394 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
395 repository that is group-readable but not group-writable.
396 See linkgit:git-init[1]. False by default.
398 core.warnAmbiguousRefs::
399 If true, git will warn you if the ref name you passed it is ambiguous
400 and might match multiple refs in the .git/refs/ tree. True by default.
403 An integer -1..9, indicating a default compression level.
404 -1 is the zlib default. 0 means no compression,
405 and 1..9 are various speed/size tradeoffs, 9 being slowest.
406 If set, this provides a default to other compression variables,
407 such as 'core.loosecompression' and 'pack.compression'.
409 core.loosecompression::
410 An integer -1..9, indicating the compression level for objects that
411 are not in a pack file. -1 is the zlib default. 0 means no
412 compression, and 1..9 are various speed/size tradeoffs, 9 being
413 slowest. If not set, defaults to core.compression. If that is
414 not set, defaults to 1 (best speed).
416 core.packedGitWindowSize::
417 Number of bytes of a pack file to map into memory in a
418 single mapping operation. Larger window sizes may allow
419 your system to process a smaller number of large pack files
420 more quickly. Smaller window sizes will negatively affect
421 performance due to increased calls to the operating system's
422 memory manager, but may improve performance when accessing
423 a large number of large pack files.
425 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
426 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
427 be reasonable for all users/operating systems. You probably do
428 not need to adjust this value.
430 Common unit suffixes of 'k', 'm', or 'g' are supported.
432 core.packedGitLimit::
433 Maximum number of bytes to map simultaneously into memory
434 from pack files. If Git needs to access more than this many
435 bytes at once to complete an operation it will unmap existing
436 regions to reclaim virtual address space within the process.
438 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
439 This should be reasonable for all users/operating systems, except on
440 the largest projects. You probably do not need to adjust this value.
442 Common unit suffixes of 'k', 'm', or 'g' are supported.
444 core.deltaBaseCacheLimit::
445 Maximum number of bytes to reserve for caching base objects
446 that may be referenced by multiple deltified objects. By storing the
447 entire decompressed base objects in a cache Git is able
448 to avoid unpacking and decompressing frequently used base
449 objects multiple times.
451 Default is 16 MiB on all platforms. This should be reasonable
452 for all users/operating systems, except on the largest projects.
453 You probably do not need to adjust this value.
455 Common unit suffixes of 'k', 'm', or 'g' are supported.
457 core.bigFileThreshold::
458 Files larger than this size are stored deflated, without
459 attempting delta compression. Storing large files without
460 delta compression avoids excessive memory usage, at the
461 slight expense of increased disk usage.
463 Default is 512 MiB on all platforms. This should be reasonable
464 for most projects as source code and other text files can still
465 be delta compressed, but larger binary media files won't be.
467 Common unit suffixes of 'k', 'm', or 'g' are supported.
470 In addition to '.gitignore' (per-directory) and
471 '.git/info/exclude', git looks into this file for patterns
472 of files which are not meant to be tracked. "{tilde}/" is expanded
473 to the value of `$HOME` and "{tilde}user/" to the specified user's
474 home directory. See linkgit:gitignore[5].
477 Some commands (e.g. svn and http interfaces) that interactively
478 ask for a password can be told to use an external program given
479 via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
480 environment variable. If not set, fall back to the value of the
481 'SSH_ASKPASS' environment variable or, failing that, a simple password
482 prompt. The external program shall be given a suitable prompt as
483 command line argument and write the password on its STDOUT.
485 core.attributesfile::
486 In addition to '.gitattributes' (per-directory) and
487 '.git/info/attributes', git looks into this file for attributes
488 (see linkgit:gitattributes[5]). Path expansions are made the same
489 way as for `core.excludesfile`.
492 Commands such as `commit` and `tag` that lets you edit
493 messages by launching an editor uses the value of this
494 variable when it is set, and the environment variable
495 `GIT_EDITOR` is not set. See linkgit:git-var[1].
498 Text editor used by `git rebase -i` for editing the rebase insn file.
499 The value is meant to be interpreted by the shell when it is used.
500 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
501 When not configured the default commit message editor is used instead.
504 The command that git will use to paginate output. Can
505 be overridden with the `GIT_PAGER` environment
506 variable. Note that git sets the `LESS` environment
507 variable to `FRSX` if it is unset when it runs the
508 pager. One can change these settings by setting the
509 `LESS` variable to some other value. Alternately,
510 these settings can be overridden on a project or
511 global basis by setting the `core.pager` option.
512 Setting `core.pager` has no affect on the `LESS`
513 environment variable behaviour above, so if you want
514 to override git's default settings this way, you need
515 to be explicit. For example, to disable the S option
516 in a backward compatible manner, set `core.pager`
517 to `less -+$LESS -FRX`. This will be passed to the
518 shell by git, which will translate the final command to
519 `LESS=FRSX less -+FRSX -FRX`.
522 A comma separated list of common whitespace problems to
523 notice. 'git diff' will use `color.diff.whitespace` to
524 highlight them, and 'git apply --whitespace=error' will
525 consider them as errors. You can prefix `-` to disable
526 any of them (e.g. `-trailing-space`):
528 * `blank-at-eol` treats trailing whitespaces at the end of the line
529 as an error (enabled by default).
530 * `space-before-tab` treats a space character that appears immediately
531 before a tab character in the initial indent part of the line as an
532 error (enabled by default).
533 * `indent-with-non-tab` treats a line that is indented with 8 or more
534 space characters as an error (not enabled by default).
535 * `tab-in-indent` treats a tab character in the initial indent part of
536 the line as an error (not enabled by default).
537 * `blank-at-eof` treats blank lines added at the end of file as an error
538 (enabled by default).
539 * `trailing-space` is a short-hand to cover both `blank-at-eol` and
541 * `cr-at-eol` treats a carriage-return at the end of line as
542 part of the line terminator, i.e. with it, `trailing-space`
543 does not trigger if the character before such a carriage-return
544 is not a whitespace (not enabled by default).
545 * `tabwidth=<n>` tells how many character positions a tab occupies; this
546 is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent`
547 errors. The default tab width is 8. Allowed values are 1 to 63.
549 core.fsyncobjectfiles::
550 This boolean will enable 'fsync()' when writing object files.
552 This is a total waste of time and effort on a filesystem that orders
553 data writes properly, but can be useful for filesystems that do not use
554 journalling (traditional UNIX filesystems) or that only journal metadata
555 and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
558 Enable parallel index preload for operations like 'git diff'
560 This can speed up operations like 'git diff' and 'git status' especially
561 on filesystems like NFS that have weak caching semantics and thus
562 relatively high IO latencies. With this set to 'true', git will do the
563 index comparison to the filesystem data in parallel, allowing
567 You can set this to 'link', in which case a hardlink followed by
568 a delete of the source are used to make sure that object creation
569 will not overwrite existing objects.
571 On some file system/operating system combinations, this is unreliable.
572 Set this config setting to 'rename' there; However, This will remove the
573 check that makes sure that existing object files will not get overwritten.
576 When showing commit messages, also show notes which are stored in
577 the given ref. The ref must be fully qualified. If the given
578 ref does not exist, it is not an error but means that no
579 notes should be printed.
581 This setting defaults to "refs/notes/commits", and it can be overridden by
582 the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1].
584 core.sparseCheckout::
585 Enable "sparse checkout" feature. See section "Sparse checkout" in
586 linkgit:git-read-tree[1] for more information.
589 Set the length object names are abbreviated to. If unspecified,
590 many commands abbreviate to 7 hexdigits, which may not be enough
591 for abbreviated object names to stay unique for sufficiently long
596 Tells 'git add' to continue adding files when some files cannot be
597 added due to indexing errors. Equivalent to the '--ignore-errors'
598 option of linkgit:git-add[1]. Older versions of git accept only
599 `add.ignore-errors`, which does not follow the usual naming
600 convention for configuration variables. Newer versions of git
601 honor `add.ignoreErrors` as well.
604 Command aliases for the linkgit:git[1] command wrapper - e.g.
605 after defining "alias.last = cat-file commit HEAD", the invocation
606 "git last" is equivalent to "git cat-file commit HEAD". To avoid
607 confusion and troubles with script usage, aliases that
608 hide existing git commands are ignored. Arguments are split by
609 spaces, the usual shell quoting and escaping is supported.
610 quote pair and a backslash can be used to quote them.
612 If the alias expansion is prefixed with an exclamation point,
613 it will be treated as a shell command. For example, defining
614 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
615 "git new" is equivalent to running the shell command
616 "gitk --all --not ORIG_HEAD". Note that shell commands will be
617 executed from the top-level directory of a repository, which may
618 not necessarily be the current directory.
619 'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix'
620 from the original current directory. See linkgit:git-rev-parse[1].
623 If true, git-am will call git-mailsplit for patches in mbox format
624 with parameter '--keep-cr'. In this case git-mailsplit will
625 not remove `\r` from lines ending with `\r\n`. Can be overridden
626 by giving '--no-keep-cr' from the command line.
627 See linkgit:git-am[1], linkgit:git-mailsplit[1].
629 apply.ignorewhitespace::
630 When set to 'change', tells 'git apply' to ignore changes in
631 whitespace, in the same way as the '--ignore-space-change'
633 When set to one of: no, none, never, false tells 'git apply' to
634 respect all whitespace differences.
635 See linkgit:git-apply[1].
638 Tells 'git apply' how to handle whitespaces, in the same way
639 as the '--whitespace' option. See linkgit:git-apply[1].
641 branch.autosetupmerge::
642 Tells 'git branch' and 'git checkout' to set up new branches
643 so that linkgit:git-pull[1] will appropriately merge from the
644 starting point branch. Note that even if this option is not set,
645 this behavior can be chosen per-branch using the `--track`
646 and `--no-track` options. The valid settings are: `false` -- no
647 automatic setup is done; `true` -- automatic setup is done when the
648 starting point is a remote-tracking branch; `always` --
649 automatic setup is done when the starting point is either a
650 local branch or remote-tracking
651 branch. This option defaults to true.
653 branch.autosetuprebase::
654 When a new branch is created with 'git branch' or 'git checkout'
655 that tracks another branch, this variable tells git to set
656 up pull to rebase instead of merge (see "branch.<name>.rebase").
657 When `never`, rebase is never automatically set to true.
658 When `local`, rebase is set to true for tracked branches of
659 other local branches.
660 When `remote`, rebase is set to true for tracked branches of
661 remote-tracking branches.
662 When `always`, rebase will be set to true for all tracking
664 See "branch.autosetupmerge" for details on how to set up a
665 branch to track another branch.
666 This option defaults to never.
668 branch.<name>.remote::
669 When in branch <name>, it tells 'git fetch' and 'git push' which
670 remote to fetch from/push to. It defaults to `origin` if no remote is
671 configured. `origin` is also used if you are not on any branch.
673 branch.<name>.merge::
674 Defines, together with branch.<name>.remote, the upstream branch
675 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which
676 branch to merge and can also affect 'git push' (see push.default).
677 When in branch <name>, it tells 'git fetch' the default
678 refspec to be marked for merging in FETCH_HEAD. The value is
679 handled like the remote part of a refspec, and must match a
680 ref which is fetched from the remote given by
681 "branch.<name>.remote".
682 The merge information is used by 'git pull' (which at first calls
683 'git fetch') to lookup the default branch for merging. Without
684 this option, 'git pull' defaults to merge the first refspec fetched.
685 Specify multiple values to get an octopus merge.
686 If you wish to setup 'git pull' so that it merges into <name> from
687 another branch in the local repository, you can point
688 branch.<name>.merge to the desired branch, and use the special setting
689 `.` (a period) for branch.<name>.remote.
691 branch.<name>.mergeoptions::
692 Sets default options for merging into branch <name>. The syntax and
693 supported options are the same as those of linkgit:git-merge[1], but
694 option values containing whitespace characters are currently not
697 branch.<name>.rebase::
698 When true, rebase the branch <name> on top of the fetched branch,
699 instead of merging the default branch from the default remote when
700 "git pull" is run. See "pull.rebase" for doing this in a non
701 branch-specific manner.
702 When the value is `interactive`, the rebase is run in interactive mode.
704 *NOTE*: this is a possibly dangerous operation; do *not* use
705 it unless you understand the implications (see linkgit:git-rebase[1]
709 Specify the command to invoke the specified browser. The
710 specified command is evaluated in shell with the URLs passed
711 as arguments. (See linkgit:git-web{litdd}browse[1].)
713 browser.<tool>.path::
714 Override the path for the given tool that may be used to
715 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
716 working repository in gitweb (see linkgit:git-instaweb[1]).
719 A boolean to make git-clean do nothing unless given -f
720 or -n. Defaults to true.
723 A boolean to enable/disable color in the output of
724 linkgit:git-branch[1]. May be set to `always`,
725 `false` (or `never`) or `auto` (or `true`), in which case colors are used
726 only when the output is to a terminal. Defaults to false.
728 color.branch.<slot>::
729 Use customized color for branch coloration. `<slot>` is one of
730 `current` (the current branch), `local` (a local branch),
731 `remote` (a remote-tracking branch in refs/remotes/), `plain` (other
734 The value for these configuration variables is a list of colors (at most
735 two) and attributes (at most one), separated by spaces. The colors
736 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
737 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
738 `blink` and `reverse`. The first color given is the foreground; the
739 second is the background. The position of the attribute, if any,
743 Whether to use ANSI escape sequences to add color to patches.
744 If this is set to `always`, linkgit:git-diff[1],
745 linkgit:git-log[1], and linkgit:git-show[1] will use color
746 for all patches. If it is set to `true` or `auto`, those
747 commands will only use color when output is to the terminal.
750 This does not affect linkgit:git-format-patch[1] nor the
751 'git-diff-{asterisk}' plumbing commands. Can be overridden on the
752 command line with the `--color[=<when>]` option.
755 Use customized color for diff colorization. `<slot>` specifies
756 which part of the patch to use the specified color, and is one
757 of `plain` (context text), `meta` (metainformation), `frag`
758 (hunk header), 'func' (function in hunk header), `old` (removed lines),
759 `new` (added lines), `commit` (commit headers), or `whitespace`
760 (highlighting whitespace errors). The values of these variables may be
761 specified as in color.branch.<slot>.
763 color.decorate.<slot>::
764 Use customized color for 'git log --decorate' output. `<slot>` is one
765 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
766 branches, remote-tracking branches, tags, stash and HEAD, respectively.
769 When set to `always`, always highlight matches. When `false` (or
770 `never`), never. When set to `true` or `auto`, use color only
771 when the output is written to the terminal. Defaults to `false`.
774 Use customized color for grep colorization. `<slot>` specifies which
775 part of the line to use the specified color, and is one of
779 non-matching text in context lines (when using `-A`, `-B`, or `-C`)
781 filename prefix (when not using `-h`)
783 function name lines (when using `-p`)
785 line number prefix (when using `-n`)
789 non-matching text in selected lines
791 separators between fields on a line (`:`, `-`, and `=`)
792 and between hunks (`--`)
795 The values of these variables may be specified as in color.branch.<slot>.
798 When set to `always`, always use colors for interactive prompts
799 and displays (such as those used by "git-add --interactive").
800 When false (or `never`), never. When set to `true` or `auto`, use
801 colors only when the output is to the terminal. Defaults to false.
803 color.interactive.<slot>::
804 Use customized color for 'git add --interactive'
805 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
806 four distinct types of normal output from interactive
807 commands. The values of these variables may be specified as
808 in color.branch.<slot>.
811 A boolean to enable/disable colored output when the pager is in
812 use (default is true).
815 A boolean to enable/disable color in the output of
816 linkgit:git-show-branch[1]. May be set to `always`,
817 `false` (or `never`) or `auto` (or `true`), in which case colors are used
818 only when the output is to a terminal. Defaults to false.
821 A boolean to enable/disable color in the output of
822 linkgit:git-status[1]. May be set to `always`,
823 `false` (or `never`) or `auto` (or `true`), in which case colors are used
824 only when the output is to a terminal. Defaults to false.
826 color.status.<slot>::
827 Use customized color for status colorization. `<slot>` is
828 one of `header` (the header text of the status message),
829 `added` or `updated` (files which are added but not committed),
830 `changed` (files which are changed but not added in the index),
831 `untracked` (files which are not tracked by git),
832 `branch` (the current branch), or
833 `nobranch` (the color the 'no branch' warning is shown in, defaulting
834 to red). The values of these variables may be specified as in
838 This variable determines the default value for variables such
839 as `color.diff` and `color.grep` that control the use of color
840 per command family. Its scope will expand as more commands learn
841 configuration to set a default for the `--color` option. Set it
842 to `always` if you want all output not intended for machine
843 consumption to use color, to `true` or `auto` if you want such
844 output to use color when written to the terminal, or to `false` or
845 `never` if you prefer git commands not to use color unless enabled
846 explicitly with some other configuration or the `--color` option.
849 A boolean to enable/disable inclusion of status information in the
850 commit message template when using an editor to prepare the commit
851 message. Defaults to true.
854 Specify a file to use as the template for new commit messages.
855 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the
856 specified user's home directory.
859 Specify an external helper to be called when a username or
860 password credential is needed; the helper may consult external
861 storage to avoid prompting the user for the credentials. See
862 linkgit:gitcredentials[7] for details.
864 credential.useHttpPath::
865 When acquiring credentials, consider the "path" component of an http
866 or https URL to be important. Defaults to false. See
867 linkgit:gitcredentials[7] for more information.
869 credential.username::
870 If no username is set for a network authentication, use this username
871 by default. See credential.<context>.* below, and
872 linkgit:gitcredentials[7].
875 Any of the credential.* options above can be applied selectively to
876 some credentials. For example "credential.https://example.com.username"
877 would set the default username only for https connections to
878 example.com. See linkgit:gitcredentials[7] for details on how URLs are
881 include::diff-config.txt[]
883 difftool.<tool>.path::
884 Override the path for the given tool. This is useful in case
885 your tool is not in the PATH.
887 difftool.<tool>.cmd::
888 Specify the command to invoke the specified diff tool.
889 The specified command is evaluated in shell with the following
890 variables available: 'LOCAL' is set to the name of the temporary
891 file containing the contents of the diff pre-image and 'REMOTE'
892 is set to the name of the temporary file containing the contents
893 of the diff post-image.
896 Prompt before each invocation of the diff tool.
899 A POSIX Extended Regular Expression used to determine what is a "word"
900 when performing word-by-word difference calculations. Character
901 sequences that match the regular expression are "words", all other
902 characters are *ignorable* whitespace.
904 fetch.recurseSubmodules::
905 This option can be either set to a boolean value or to 'on-demand'.
906 Setting it to a boolean changes the behavior of fetch and pull to
907 unconditionally recurse into submodules when set to true or to not
908 recurse at all when set to false. When set to 'on-demand' (the default
909 value), fetch and pull will only recurse into a populated submodule
910 when its superproject retrieves a commit that updates the submodule's
914 If it is set to true, git-fetch-pack will check all fetched
915 objects. It will abort in the case of a malformed object or a
916 broken link. The result of an abort are only dangling objects.
917 Defaults to false. If not set, the value of `transfer.fsckObjects`
921 If the number of objects fetched over the git native
922 transfer is below this
923 limit, then the objects will be unpacked into loose object
924 files. However if the number of received objects equals or
925 exceeds this limit then the received pack will be stored as
926 a pack, after adding any missing delta bases. Storing the
927 pack from a push can make the push operation complete faster,
928 especially on slow filesystems. If not set, the value of
929 `transfer.unpackLimit` is used instead.
932 Enable multipart/mixed attachments as the default for
933 'format-patch'. The value can also be a double quoted string
934 which will enable attachments as the default and set the
935 value as the boundary. See the --attach option in
936 linkgit:git-format-patch[1].
939 A boolean which can enable or disable sequence numbers in patch
940 subjects. It defaults to "auto" which enables it only if there
941 is more than one patch. It can be enabled or disabled for all
942 messages by setting it to "true" or "false". See --numbered
943 option in linkgit:git-format-patch[1].
946 Additional email headers to include in a patch to be submitted
947 by mail. See linkgit:git-format-patch[1].
951 Additional recipients to include in a patch to be submitted
952 by mail. See the --to and --cc options in
953 linkgit:git-format-patch[1].
955 format.subjectprefix::
956 The default for format-patch is to output files with the '[PATCH]'
957 subject prefix. Use this variable to change that prefix.
960 The default for format-patch is to output a signature containing
961 the git version number. Use this variable to change that default.
962 Set this variable to the empty string ("") to suppress
963 signature generation.
966 The default for format-patch is to output files with the suffix
967 `.patch`. Use this variable to change that suffix (make sure to
968 include the dot if you want it).
971 The default pretty format for log/show/whatchanged command,
972 See linkgit:git-log[1], linkgit:git-show[1],
973 linkgit:git-whatchanged[1].
976 The default threading style for 'git format-patch'. Can be
977 a boolean value, or `shallow` or `deep`. `shallow` threading
978 makes every mail a reply to the head of the series,
979 where the head is chosen from the cover letter, the
980 `\--in-reply-to`, and the first patch mail, in this order.
981 `deep` threading makes every mail a reply to the previous one.
982 A true boolean value is the same as `shallow`, and a false
983 value disables threading.
986 A boolean value which lets you enable the `-s/--signoff` option of
987 format-patch by default. *Note:* Adding the Signed-off-by: line to a
988 patch should be a conscious act and means that you certify you have
989 the rights to submit this work under the same open source license.
990 Please see the 'SubmittingPatches' document for further discussion.
992 filter.<driver>.clean::
993 The command which is used to convert the content of a worktree
994 file to a blob upon checkin. See linkgit:gitattributes[5] for
997 filter.<driver>.smudge::
998 The command which is used to convert the content of a blob
999 object to a worktree file upon checkout. See
1000 linkgit:gitattributes[5] for details.
1002 gc.aggressiveWindow::
1003 The window size parameter used in the delta compression
1004 algorithm used by 'git gc --aggressive'. This defaults
1008 When there are approximately more than this many loose
1009 objects in the repository, `git gc --auto` will pack them.
1010 Some Porcelain commands use this command to perform a
1011 light-weight garbage collection from time to time. The
1012 default value is 6700. Setting this to 0 disables it.
1015 When there are more than this many packs that are not
1016 marked with `*.keep` file in the repository, `git gc
1017 --auto` consolidates them into one larger pack. The
1018 default value is 50. Setting this to 0 disables it.
1021 Running `git pack-refs` in a repository renders it
1022 unclonable by Git versions prior to 1.5.1.2 over dumb
1023 transports such as HTTP. This variable determines whether
1024 'git gc' runs `git pack-refs`. This can be set to `notbare`
1025 to enable it within all non-bare repos or it can be set to a
1026 boolean value. The default is `true`.
1029 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
1030 Override the grace period with this config variable. The value
1031 "now" may be used to disable this grace period and always prune
1032 unreachable objects immediately.
1035 gc.<pattern>.reflogexpire::
1036 'git reflog expire' removes reflog entries older than
1037 this time; defaults to 90 days. With "<pattern>" (e.g.
1038 "refs/stash") in the middle the setting applies only to
1039 the refs that match the <pattern>.
1041 gc.reflogexpireunreachable::
1042 gc.<ref>.reflogexpireunreachable::
1043 'git reflog expire' removes reflog entries older than
1044 this time and are not reachable from the current tip;
1045 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")
1046 in the middle, the setting applies only to the refs that
1047 match the <pattern>.
1050 Records of conflicted merge you resolved earlier are
1051 kept for this many days when 'git rerere gc' is run.
1052 The default is 60 days. See linkgit:git-rerere[1].
1054 gc.rerereunresolved::
1055 Records of conflicted merge you have not resolved are
1056 kept for this many days when 'git rerere gc' is run.
1057 The default is 15 days. See linkgit:git-rerere[1].
1059 gitcvs.commitmsgannotation::
1060 Append this string to each commit message. Set to empty string
1061 to disable this feature. Defaults to "via git-CVS emulator".
1064 Whether the CVS server interface is enabled for this repository.
1065 See linkgit:git-cvsserver[1].
1068 Path to a log file where the CVS server interface well... logs
1069 various stuff. See linkgit:git-cvsserver[1].
1071 gitcvs.usecrlfattr::
1072 If true, the server will look up the end-of-line conversion
1073 attributes for files to determine the '-k' modes to use. If
1074 the attributes force git to treat a file as text,
1075 the '-k' mode will be left blank so CVS clients will
1076 treat it as text. If they suppress text conversion, the file
1077 will be set with '-kb' mode, which suppresses any newline munging
1078 the client might otherwise do. If the attributes do not allow
1079 the file type to be determined, then 'gitcvs.allbinary' is
1080 used. See linkgit:gitattributes[5].
1083 This is used if 'gitcvs.usecrlfattr' does not resolve
1084 the correct '-kb' mode to use. If true, all
1085 unresolved files are sent to the client in
1086 mode '-kb'. This causes the client to treat them
1087 as binary files, which suppresses any newline munging it
1088 otherwise might do. Alternatively, if it is set to "guess",
1089 then the contents of the file are examined to decide if
1090 it is binary, similar to 'core.autocrlf'.
1093 Database used by git-cvsserver to cache revision information
1094 derived from the git repository. The exact meaning depends on the
1095 used database driver, for SQLite (which is the default driver) this
1096 is a filename. Supports variable substitution (see
1097 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1098 Default: '%Ggitcvs.%m.sqlite'
1101 Used Perl DBI driver. You can specify any available driver
1102 for this here, but it might not work. git-cvsserver is tested
1103 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1104 reported *not* to work with 'DBD::mysql'. Experimental feature.
1105 May not contain double colons (`:`). Default: 'SQLite'.
1106 See linkgit:git-cvsserver[1].
1108 gitcvs.dbuser, gitcvs.dbpass::
1109 Database user and password. Only useful if setting 'gitcvs.dbdriver',
1110 since SQLite has no concept of database users and/or passwords.
1111 'gitcvs.dbuser' supports variable substitution (see
1112 linkgit:git-cvsserver[1] for details).
1114 gitcvs.dbTableNamePrefix::
1115 Database table name prefix. Prepended to the names of any
1116 database tables used, allowing a single database to be used
1117 for several repositories. Supports variable substitution (see
1118 linkgit:git-cvsserver[1] for details). Any non-alphabetic
1119 characters will be replaced with underscores.
1121 All gitcvs variables except for 'gitcvs.usecrlfattr' and
1122 'gitcvs.allbinary' can also be specified as
1123 'gitcvs.<access_method>.<varname>' (where 'access_method'
1124 is one of "ext" and "pserver") to make them apply only for the given
1128 gitweb.description::
1131 See linkgit:gitweb[1] for description.
1139 gitweb.remote_heads::
1142 See linkgit:gitweb.conf[5] for description.
1145 If set to true, enable '-n' option by default.
1147 grep.extendedRegexp::
1148 If set to true, enable '--extended-regexp' option by default.
1151 Use this custom program instead of "gpg" found on $PATH when
1152 making or verifying a PGP signature. The program must support the
1153 same command line interface as GPG, namely, to verify a detached
1154 signature, "gpg --verify $file - <$signature" is run, and the
1155 program is expected to signal a good signature by exiting with
1156 code 0, and to generate an ascii-armored detached signature, the
1157 standard input of "gpg -bsau $key" is fed with the contents to be
1158 signed, and the program is expected to send the result to its
1161 gui.commitmsgwidth::
1162 Defines how wide the commit message window is in the
1163 linkgit:git-gui[1]. "75" is the default.
1166 Specifies how many context lines should be used in calls to diff
1167 made by the linkgit:git-gui[1]. The default is "5".
1170 Specifies the default encoding to use for displaying of
1171 file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1172 It can be overridden by setting the 'encoding' attribute
1173 for relevant files (see linkgit:gitattributes[5]).
1174 If this option is not set, the tools default to the
1177 gui.matchtrackingbranch::
1178 Determines if new branches created with linkgit:git-gui[1] should
1179 default to tracking remote branches with matching names or
1180 not. Default: "false".
1182 gui.newbranchtemplate::
1183 Is used as suggested name when creating new branches using the
1186 gui.pruneduringfetch::
1187 "true" if linkgit:git-gui[1] should prune remote-tracking branches when
1188 performing a fetch. The default value is "false".
1191 Determines if linkgit:git-gui[1] should trust the file modification
1192 timestamp or not. By default the timestamps are not trusted.
1194 gui.spellingdictionary::
1195 Specifies the dictionary used for spell checking commit messages in
1196 the linkgit:git-gui[1]. When set to "none" spell checking is turned
1200 If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1201 location detection. It makes blame significantly faster on huge
1202 repositories at the expense of less thorough copy detection.
1204 gui.copyblamethreshold::
1205 Specifies the threshold to use in 'git gui blame' original location
1206 detection, measured in alphanumeric characters. See the
1207 linkgit:git-blame[1] manual for more information on copy detection.
1209 gui.blamehistoryctx::
1210 Specifies the radius of history context in days to show in
1211 linkgit:gitk[1] for the selected commit, when the `Show History
1212 Context` menu item is invoked from 'git gui blame'. If this
1213 variable is set to zero, the whole history is shown.
1215 guitool.<name>.cmd::
1216 Specifies the shell command line to execute when the corresponding item
1217 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1218 mandatory for every tool. The command is executed from the root of
1219 the working directory, and in the environment it receives the name of
1220 the tool as 'GIT_GUITOOL', the name of the currently selected file as
1221 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1222 the head is detached, 'CUR_BRANCH' is empty).
1224 guitool.<name>.needsfile::
1225 Run the tool only if a diff is selected in the GUI. It guarantees
1226 that 'FILENAME' is not empty.
1228 guitool.<name>.noconsole::
1229 Run the command silently, without creating a window to display its
1232 guitool.<name>.norescan::
1233 Don't rescan the working directory for changes after the tool
1236 guitool.<name>.confirm::
1237 Show a confirmation dialog before actually running the tool.
1239 guitool.<name>.argprompt::
1240 Request a string argument from the user, and pass it to the tool
1241 through the 'ARGS' environment variable. Since requesting an
1242 argument implies confirmation, the 'confirm' option has no effect
1243 if this is enabled. If the option is set to 'true', 'yes', or '1',
1244 the dialog uses a built-in generic prompt; otherwise the exact
1245 value of the variable is used.
1247 guitool.<name>.revprompt::
1248 Request a single valid revision from the user, and set the
1249 'REVISION' environment variable. In other aspects this option
1250 is similar to 'argprompt', and can be used together with it.
1252 guitool.<name>.revunmerged::
1253 Show only unmerged branches in the 'revprompt' subdialog.
1254 This is useful for tools similar to merge or rebase, but not
1255 for things like checkout or reset.
1257 guitool.<name>.title::
1258 Specifies the title to use for the prompt dialog. The default
1261 guitool.<name>.prompt::
1262 Specifies the general prompt string to display at the top of
1263 the dialog, before subsections for 'argprompt' and 'revprompt'.
1264 The default value includes the actual command.
1267 Specify the browser that will be used to display help in the
1268 'web' format. See linkgit:git-help[1].
1271 Override the default help format used by linkgit:git-help[1].
1272 Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1273 the default. 'web' and 'html' are the same.
1276 Automatically correct and execute mistyped commands after
1277 waiting for the given number of deciseconds (0.1 sec). If more
1278 than one command can be deduced from the entered text, nothing
1279 will be executed. If the value of this option is negative,
1280 the corrected command will be executed immediately. If the
1281 value is 0 - the command will be just shown but not executed.
1282 This is the default.
1285 Override the HTTP proxy, normally configured using the 'http_proxy',
1286 'https_proxy', and 'all_proxy' environment variables (see
1287 `curl(1)`). This can be overridden on a per-remote basis; see
1291 File containing previously stored cookie lines which should be used
1292 in the git http session, if they match the server. The file format
1293 of the file to read cookies from should be plain HTTP headers or
1294 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
1295 NOTE that the file specified with http.cookiefile is only used as
1296 input. No cookies will be stored in the file.
1299 Whether to verify the SSL certificate when fetching or pushing
1300 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1304 File containing the SSL certificate when fetching or pushing
1305 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1309 File containing the SSL private key when fetching or pushing
1310 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1313 http.sslCertPasswordProtected::
1314 Enable git's password prompt for the SSL certificate. Otherwise
1315 OpenSSL will prompt the user, possibly many times, if the
1316 certificate or private key is encrypted. Can be overridden by the
1317 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1320 File containing the certificates to verify the peer with when
1321 fetching or pushing over HTTPS. Can be overridden by the
1322 'GIT_SSL_CAINFO' environment variable.
1325 Path containing files with the CA certificates to verify the peer
1326 with when fetching or pushing over HTTPS. Can be overridden
1327 by the 'GIT_SSL_CAPATH' environment variable.
1330 How many HTTP requests to launch in parallel. Can be overridden
1331 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1334 The number of curl sessions (counted across slots) to be kept across
1335 requests. They will not be ended with curl_easy_cleanup() until
1336 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1337 value will be capped at 1. Defaults to 1.
1340 Maximum size in bytes of the buffer used by smart HTTP
1341 transports when POSTing data to the remote system.
1342 For requests larger than this buffer size, HTTP/1.1 and
1343 Transfer-Encoding: chunked is used to avoid creating a
1344 massive pack file locally. Default is 1 MiB, which is
1345 sufficient for most requests.
1347 http.lowSpeedLimit, http.lowSpeedTime::
1348 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1349 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1350 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1351 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1354 A boolean which disables using of EPSV ftp command by curl.
1355 This can helpful with some "poor" ftp servers which don't
1356 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1357 environment variable. Default is false (curl will use EPSV).
1360 The HTTP USER_AGENT string presented to an HTTP server. The default
1361 value represents the version of the client git such as git/1.7.1.
1362 This option allows you to override this value to a more common value
1363 such as Mozilla/4.0. This may be necessary, for instance, if
1364 connecting through a firewall that restricts HTTP connections to a set
1365 of common USER_AGENT strings (but not including those like git/1.7.1).
1366 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1368 i18n.commitEncoding::
1369 Character encoding the commit messages are stored in; git itself
1370 does not care per se, but this information is necessary e.g. when
1371 importing commits from emails or in the gitk graphical history
1372 browser (and possibly at other places in the future or in other
1373 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1375 i18n.logOutputEncoding::
1376 Character encoding the commit messages are converted to when
1377 running 'git log' and friends.
1380 The configuration variables in the 'imap' section are described
1381 in linkgit:git-imap-send[1].
1384 Specify the directory from which templates will be copied.
1385 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1388 Specify the program that will be used to browse your working
1389 repository in gitweb. See linkgit:git-instaweb[1].
1392 The HTTP daemon command-line to start gitweb on your working
1393 repository. See linkgit:git-instaweb[1].
1396 If true the web server started by linkgit:git-instaweb[1] will
1397 be bound to the local IP (127.0.0.1).
1399 instaweb.modulepath::
1400 The default module path for linkgit:git-instaweb[1] to use
1401 instead of /usr/lib/apache2/modules. Only used if httpd
1405 The port number to bind the gitweb httpd to. See
1406 linkgit:git-instaweb[1].
1408 interactive.singlekey::
1409 In interactive commands, allow the user to provide one-letter
1410 input with a single key (i.e., without hitting enter).
1411 Currently this is used by the `\--patch` mode of
1412 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],
1413 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this
1414 setting is silently ignored if portable keystroke input
1418 If true, makes linkgit:git-log[1], linkgit:git-show[1], and
1419 linkgit:git-whatchanged[1] assume `\--abbrev-commit`. You may
1420 override this option with `\--no-abbrev-commit`.
1423 Set the default date-time mode for the 'log' command.
1424 Setting a value for log.date is similar to using 'git log''s
1425 `\--date` option. Possible values are `relative`, `local`,
1426 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1430 Print out the ref names of any commits that are shown by the log
1431 command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1432 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1433 specified, the full ref name (including prefix) will be printed.
1434 This is the same as the log commands '--decorate' option.
1437 If true, the initial commit will be shown as a big creation event.
1438 This is equivalent to a diff against an empty tree.
1439 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1440 normally hide the root commit will now show it. True by default.
1443 The location of an augmenting mailmap file. The default
1444 mailmap, located in the root of the repository, is loaded
1445 first, then the mailmap file pointed to by this variable.
1446 The location of the mailmap file may be in a repository
1447 subdirectory, or somewhere outside of the repository itself.
1448 See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1451 Specify the programs that may be used to display help in the
1452 'man' format. See linkgit:git-help[1].
1455 Specify the command to invoke the specified man viewer. The
1456 specified command is evaluated in shell with the man page
1457 passed as argument. (See linkgit:git-help[1].)
1460 Override the path for the given tool that may be used to
1461 display help in the 'man' format. See linkgit:git-help[1].
1463 include::merge-config.txt[]
1465 mergetool.<tool>.path::
1466 Override the path for the given tool. This is useful in case
1467 your tool is not in the PATH.
1469 mergetool.<tool>.cmd::
1470 Specify the command to invoke the specified merge tool. The
1471 specified command is evaluated in shell with the following
1472 variables available: 'BASE' is the name of a temporary file
1473 containing the common base of the files to be merged, if available;
1474 'LOCAL' is the name of a temporary file containing the contents of
1475 the file on the current branch; 'REMOTE' is the name of a temporary
1476 file containing the contents of the file from the branch being
1477 merged; 'MERGED' contains the name of the file to which the merge
1478 tool should write the results of a successful merge.
1480 mergetool.<tool>.trustExitCode::
1481 For a custom merge command, specify whether the exit code of
1482 the merge command can be used to determine whether the merge was
1483 successful. If this is not set to true then the merge target file
1484 timestamp is checked and the merge assumed to have been successful
1485 if the file has been updated, otherwise the user is prompted to
1486 indicate the success of the merge.
1488 mergetool.keepBackup::
1489 After performing a merge, the original file with conflict markers
1490 can be saved as a file with a `.orig` extension. If this variable
1491 is set to `false` then this file is not preserved. Defaults to
1492 `true` (i.e. keep the backup files).
1494 mergetool.keepTemporaries::
1495 When invoking a custom merge tool, git uses a set of temporary
1496 files to pass to the tool. If the tool returns an error and this
1497 variable is set to `true`, then these temporary files will be
1498 preserved, otherwise they will be removed after the tool has
1499 exited. Defaults to `false`.
1502 Prompt before each invocation of the merge resolution program.
1505 The (fully qualified) refname from which to show notes when
1506 showing commit messages. The value of this variable can be set
1507 to a glob, in which case notes from all matching refs will be
1508 shown. You may also specify this configuration variable
1509 several times. A warning will be issued for refs that do not
1510 exist, but a glob that does not match any refs is silently
1513 This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1514 environment variable, which must be a colon separated list of refs or
1517 The effective value of "core.notesRef" (possibly overridden by
1518 GIT_NOTES_REF) is also implicitly added to the list of refs to be
1521 notes.rewrite.<command>::
1522 When rewriting commits with <command> (currently `amend` or
1523 `rebase`) and this variable is set to `true`, git
1524 automatically copies your notes from the original to the
1525 rewritten commit. Defaults to `true`, but see
1526 "notes.rewriteRef" below.
1529 When copying notes during a rewrite (see the
1530 "notes.rewrite.<command>" option), determines what to do if
1531 the target commit already has a note. Must be one of
1532 `overwrite`, `concatenate`, or `ignore`. Defaults to
1535 This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1536 environment variable.
1539 When copying notes during a rewrite, specifies the (fully
1540 qualified) ref whose notes should be copied. The ref may be a
1541 glob, in which case notes in all matching refs will be copied.
1542 You may also specify this configuration several times.
1544 Does not have a default value; you must configure this variable to
1545 enable note rewriting. Set it to `refs/notes/commits` to enable
1546 rewriting for the default commit notes.
1548 This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1549 environment variable, which must be a colon separated list of refs or
1553 The size of the window used by linkgit:git-pack-objects[1] when no
1554 window size is given on the command line. Defaults to 10.
1557 The maximum delta depth used by linkgit:git-pack-objects[1] when no
1558 maximum depth is given on the command line. Defaults to 50.
1561 The window memory size limit used by linkgit:git-pack-objects[1]
1562 when no limit is given on the command line. The value can be
1563 suffixed with "k", "m", or "g". Defaults to 0, meaning no
1567 An integer -1..9, indicating the compression level for objects
1568 in a pack file. -1 is the zlib default. 0 means no
1569 compression, and 1..9 are various speed/size tradeoffs, 9 being
1570 slowest. If not set, defaults to core.compression. If that is
1571 not set, defaults to -1, the zlib default, which is "a default
1572 compromise between speed and compression (currently equivalent
1575 Note that changing the compression level will not automatically recompress
1576 all existing objects. You can force recompression by passing the -F option
1577 to linkgit:git-repack[1].
1579 pack.deltaCacheSize::
1580 The maximum memory in bytes used for caching deltas in
1581 linkgit:git-pack-objects[1] before writing them out to a pack.
1582 This cache is used to speed up the writing object phase by not
1583 having to recompute the final delta result once the best match
1584 for all objects is found. Repacking large repositories on machines
1585 which are tight with memory might be badly impacted by this though,
1586 especially if this cache pushes the system into swapping.
1587 A value of 0 means no limit. The smallest size of 1 byte may be
1588 used to virtually disable this cache. Defaults to 256 MiB.
1590 pack.deltaCacheLimit::
1591 The maximum size of a delta, that is cached in
1592 linkgit:git-pack-objects[1]. This cache is used to speed up the
1593 writing object phase by not having to recompute the final delta
1594 result once the best match for all objects is found. Defaults to 1000.
1597 Specifies the number of threads to spawn when searching for best
1598 delta matches. This requires that linkgit:git-pack-objects[1]
1599 be compiled with pthreads otherwise this option is ignored with a
1600 warning. This is meant to reduce packing time on multiprocessor
1601 machines. The required amount of memory for the delta search window
1602 is however multiplied by the number of threads.
1603 Specifying 0 will cause git to auto-detect the number of CPU's
1604 and set the number of threads accordingly.
1607 Specify the default pack index version. Valid values are 1 for
1608 legacy pack index used by Git versions prior to 1.5.2, and 2 for
1609 the new pack index with capabilities for packs larger than 4 GB
1610 as well as proper protection against the repacking of corrupted
1611 packs. Version 2 is the default. Note that version 2 is enforced
1612 and this config option ignored whenever the corresponding pack is
1615 If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1616 cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1617 that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1618 other side may give you a repository that cannot be accessed with your
1619 older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1620 you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1621 the `{asterisk}.idx` file.
1623 pack.packSizeLimit::
1624 The maximum size of a pack. This setting only affects
1625 packing to a file when repacking, i.e. the git:// protocol
1626 is unaffected. It can be overridden by the `\--max-pack-size`
1627 option of linkgit:git-repack[1]. The minimum size allowed is
1628 limited to 1 MiB. The default is unlimited.
1629 Common unit suffixes of 'k', 'm', or 'g' are
1633 If the value is boolean, turns on or off pagination of the
1634 output of a particular git subcommand when writing to a tty.
1635 Otherwise, turns on pagination for the subcommand using the
1636 pager specified by the value of `pager.<cmd>`. If `\--paginate`
1637 or `\--no-pager` is specified on the command line, it takes
1638 precedence over this option. To disable pagination for all
1639 commands, set `core.pager` or `GIT_PAGER` to `cat`.
1642 Alias for a --pretty= format string, as specified in
1643 linkgit:git-log[1]. Any aliases defined here can be used just
1644 as the built-in pretty formats could. For example,
1645 running `git config pretty.changelog "format:{asterisk} %H %s"`
1646 would cause the invocation `git log --pretty=changelog`
1647 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.
1648 Note that an alias with the same name as a built-in format
1649 will be silently ignored.
1652 When true, rebase branches on top of the fetched branch, instead
1653 of merging the default branch from the default remote when "git
1654 pull" is run. See "branch.<name>.rebase" for setting this on a
1657 *NOTE*: this is a possibly dangerous operation; do *not* use
1658 it unless you understand the implications (see linkgit:git-rebase[1]
1662 The default merge strategy to use when pulling multiple branches
1666 The default merge strategy to use when pulling a single branch.
1669 Defines the action git push should take if no refspec is given
1670 on the command line, no refspec is configured in the remote, and
1671 no refspec is implied by any of the options given on the command
1672 line. Possible values are:
1674 * `nothing` - do not push anything.
1675 * `matching` - push all matching branches.
1676 All branches having the same name in both ends are considered to be
1677 matching. This is the default.
1678 * `upstream` - push the current branch to its upstream branch.
1679 * `tracking` - deprecated synonym for `upstream`.
1680 * `current` - push the current branch to a branch of the same name.
1683 Whether to show a diffstat of what changed upstream since the last
1684 rebase. False by default.
1687 If set to true enable '--autosquash' option by default.
1690 By default, git-receive-pack will run "git-gc --auto" after
1691 receiving data from git-push and updating refs. You can stop
1692 it by setting this variable to false.
1694 receive.fsckObjects::
1695 If it is set to true, git-receive-pack will check all received
1696 objects. It will abort in the case of a malformed object or a
1697 broken link. The result of an abort are only dangling objects.
1698 Defaults to false. If not set, the value of `transfer.fsckObjects`
1701 receive.unpackLimit::
1702 If the number of objects received in a push is below this
1703 limit then the objects will be unpacked into loose object
1704 files. However if the number of received objects equals or
1705 exceeds this limit then the received pack will be stored as
1706 a pack, after adding any missing delta bases. Storing the
1707 pack from a push can make the push operation complete faster,
1708 especially on slow filesystems. If not set, the value of
1709 `transfer.unpackLimit` is used instead.
1711 receive.denyDeletes::
1712 If set to true, git-receive-pack will deny a ref update that deletes
1713 the ref. Use this to prevent such a ref deletion via a push.
1715 receive.denyDeleteCurrent::
1716 If set to true, git-receive-pack will deny a ref update that
1717 deletes the currently checked out branch of a non-bare repository.
1719 receive.denyCurrentBranch::
1720 If set to true or "refuse", git-receive-pack will deny a ref update
1721 to the currently checked out branch of a non-bare repository.
1722 Such a push is potentially dangerous because it brings the HEAD
1723 out of sync with the index and working tree. If set to "warn",
1724 print a warning of such a push to stderr, but allow the push to
1725 proceed. If set to false or "ignore", allow such pushes with no
1726 message. Defaults to "refuse".
1728 There are two more options that are meant for Git experts: "updateInstead"
1729 which will run `read-tree -u -m HEAD` and "detachInstead" which will detach
1730 the HEAD so it does not need to change. Both options come with their own
1731 set of possible *complications*, but can be appropriate in rare workflows.
1733 receive.denyNonFastForwards::
1734 If set to true, git-receive-pack will deny a ref update which is
1735 not a fast-forward. Use this to prevent such an update via a push,
1736 even if that push is forced. This configuration variable is
1737 set when initializing a shared repository.
1739 receive.updateserverinfo::
1740 If set to true, git-receive-pack will run git-update-server-info
1741 after receiving data from git-push and updating refs.
1744 The URL of a remote repository. See linkgit:git-fetch[1] or
1745 linkgit:git-push[1].
1747 remote.<name>.pushurl::
1748 The push URL of a remote repository. See linkgit:git-push[1].
1750 remote.<name>.proxy::
1751 For remotes that require curl (http, https and ftp), the URL to
1752 the proxy to use for that remote. Set to the empty string to
1753 disable proxying for that remote.
1755 remote.<name>.fetch::
1756 The default set of "refspec" for linkgit:git-fetch[1]. See
1757 linkgit:git-fetch[1].
1759 remote.<name>.push::
1760 The default set of "refspec" for linkgit:git-push[1]. See
1761 linkgit:git-push[1].
1763 remote.<name>.mirror::
1764 If true, pushing to this remote will automatically behave
1765 as if the `\--mirror` option was given on the command line.
1767 remote.<name>.skipDefaultUpdate::
1768 If true, this remote will be skipped by default when updating
1769 using linkgit:git-fetch[1] or the `update` subcommand of
1770 linkgit:git-remote[1].
1772 remote.<name>.skipFetchAll::
1773 If true, this remote will be skipped by default when updating
1774 using linkgit:git-fetch[1] or the `update` subcommand of
1775 linkgit:git-remote[1].
1777 remote.<name>.receivepack::
1778 The default program to execute on the remote side when pushing. See
1779 option \--receive-pack of linkgit:git-push[1].
1781 remote.<name>.uploadpack::
1782 The default program to execute on the remote side when fetching. See
1783 option \--upload-pack of linkgit:git-fetch-pack[1].
1785 remote.<name>.tagopt::
1786 Setting this value to \--no-tags disables automatic tag following when
1787 fetching from remote <name>. Setting it to \--tags will fetch every
1788 tag from remote <name>, even if they are not reachable from remote
1789 branch heads. Passing these flags directly to linkgit:git-fetch[1] can
1790 override this setting. See options \--tags and \--no-tags of
1791 linkgit:git-fetch[1].
1794 Setting this to a value <vcs> will cause git to interact with
1795 the remote with the git-remote-<vcs> helper.
1798 The list of remotes which are fetched by "git remote update
1799 <group>". See linkgit:git-remote[1].
1801 repack.usedeltabaseoffset::
1802 By default, linkgit:git-repack[1] creates packs that use
1803 delta-base offset. If you need to share your repository with
1804 git older than version 1.4.4, either directly or via a dumb
1805 protocol such as http, then you need to set this option to
1806 "false" and repack. Access from old git versions over the
1807 native protocol are unaffected by this option.
1810 When set to true, `git-rerere` updates the index with the
1811 resulting contents after it cleanly resolves conflicts using
1812 previously recorded resolution. Defaults to false.
1815 Activate recording of resolved conflicts, so that identical
1816 conflict hunks can be resolved automatically, should they be
1817 encountered again. By default, linkgit:git-rerere[1] is
1818 enabled if there is an `rr-cache` directory under the
1819 `$GIT_DIR`, e.g. if "rerere" was previously used in the
1822 sendemail.identity::
1823 A configuration identity. When given, causes values in the
1824 'sendemail.<identity>' subsection to take precedence over
1825 values in the 'sendemail' section. The default identity is
1826 the value of 'sendemail.identity'.
1828 sendemail.smtpencryption::
1829 See linkgit:git-send-email[1] for description. Note that this
1830 setting is not subject to the 'identity' mechanism.
1833 Deprecated alias for 'sendemail.smtpencryption = ssl'.
1835 sendemail.<identity>.*::
1836 Identity-specific versions of the 'sendemail.*' parameters
1837 found below, taking precedence over those when the this
1838 identity is selected, through command-line or
1839 'sendemail.identity'.
1841 sendemail.aliasesfile::
1842 sendemail.aliasfiletype::
1846 sendemail.chainreplyto::
1848 sendemail.envelopesender::
1850 sendemail.multiedit::
1851 sendemail.signedoffbycc::
1852 sendemail.smtppass::
1853 sendemail.suppresscc::
1854 sendemail.suppressfrom::
1856 sendemail.smtpdomain::
1857 sendemail.smtpserver::
1858 sendemail.smtpserverport::
1859 sendemail.smtpserveroption::
1860 sendemail.smtpuser::
1862 sendemail.validate::
1863 See linkgit:git-send-email[1] for description.
1865 sendemail.signedoffcc::
1866 Deprecated alias for 'sendemail.signedoffbycc'.
1868 showbranch.default::
1869 The default set of branches for linkgit:git-show-branch[1].
1870 See linkgit:git-show-branch[1].
1872 status.relativePaths::
1873 By default, linkgit:git-status[1] shows paths relative to the
1874 current directory. Setting this variable to `false` shows paths
1875 relative to the repository root (this was the default for git
1878 status.showUntrackedFiles::
1879 By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1880 files which are not currently tracked by Git. Directories which
1881 contain only untracked files, are shown with the directory name
1882 only. Showing untracked files means that Git needs to lstat() all
1883 all the files in the whole repository, which might be slow on some
1884 systems. So, this variable controls how the commands displays
1885 the untracked files. Possible values are:
1888 * `no` - Show no untracked files.
1889 * `normal` - Show untracked files and directories.
1890 * `all` - Show also individual files in untracked directories.
1893 If this variable is not specified, it defaults to 'normal'.
1894 This variable can be overridden with the -u|--untracked-files option
1895 of linkgit:git-status[1] and linkgit:git-commit[1].
1897 status.submodulesummary::
1899 If this is set to a non zero number or true (identical to -1 or an
1900 unlimited number), the submodule summary will be enabled and a
1901 summary of commits for modified submodules will be shown (see
1902 --summary-limit option of linkgit:git-submodule[1]).
1904 submodule.<name>.path::
1905 submodule.<name>.url::
1906 submodule.<name>.update::
1907 The path within this project, URL, and the updating strategy
1908 for a submodule. These variables are initially populated
1909 by 'git submodule init'; edit them to override the
1910 URL and other values found in the `.gitmodules` file. See
1911 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
1913 submodule.<name>.fetchRecurseSubmodules::
1914 This option can be used to control recursive fetching of this
1915 submodule. It can be overridden by using the --[no-]recurse-submodules
1916 command line option to "git fetch" and "git pull".
1917 This setting will override that from in the linkgit:gitmodules[5]
1920 submodule.<name>.ignore::
1921 Defines under what circumstances "git status" and the diff family show
1922 a submodule as modified. When set to "all", it will never be considered
1923 modified, "dirty" will ignore all changes to the submodules work tree and
1924 takes only differences between the HEAD of the submodule and the commit
1925 recorded in the superproject into account. "untracked" will additionally
1926 let submodules with modified tracked files in their work tree show up.
1927 Using "none" (the default when this option is not set) also shows
1928 submodules that have untracked files in their work tree as changed.
1929 This setting overrides any setting made in .gitmodules for this submodule,
1930 both settings can be overridden on the command line by using the
1931 "--ignore-submodules" option.
1934 This variable can be used to restrict the permission bits of
1935 tar archive entries. The default is 0002, which turns off the
1936 world write bit. The special value "user" indicates that the
1937 archiving user's umask will be used instead. See umask(2) and
1938 linkgit:git-archive[1].
1940 transfer.fsckObjects::
1941 When `fetch.fsckObjects` or `receive.fsckObjects` are
1942 not set, the value of this variable is used instead.
1945 transfer.unpackLimit::
1946 When `fetch.unpackLimit` or `receive.unpackLimit` are
1947 not set, the value of this variable is used instead.
1948 The default value is 100.
1950 url.<base>.insteadOf::
1951 Any URL that starts with this value will be rewritten to
1952 start, instead, with <base>. In cases where some site serves a
1953 large number of repositories, and serves them with multiple
1954 access methods, and some users need to use different access
1955 methods, this feature allows people to specify any of the
1956 equivalent URLs and have git automatically rewrite the URL to
1957 the best alternative for the particular user, even for a
1958 never-before-seen repository on the site. When more than one
1959 insteadOf strings match a given URL, the longest match is used.
1961 url.<base>.pushInsteadOf::
1962 Any URL that starts with this value will not be pushed to;
1963 instead, it will be rewritten to start with <base>, and the
1964 resulting URL will be pushed to. In cases where some site serves
1965 a large number of repositories, and serves them with multiple
1966 access methods, some of which do not allow push, this feature
1967 allows people to specify a pull-only URL and have git
1968 automatically use an appropriate URL to push, even for a
1969 never-before-seen repository on the site. When more than one
1970 pushInsteadOf strings match a given URL, the longest match is
1971 used. If a remote has an explicit pushurl, git will ignore this
1972 setting for that remote.
1975 Your email address to be recorded in any newly created commits.
1976 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1977 'EMAIL' environment variables. See linkgit:git-commit-tree[1].
1980 Your full name to be recorded in any newly created commits.
1981 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1982 environment variables. See linkgit:git-commit-tree[1].
1985 If linkgit:git-tag[1] is not selecting the key you want it to
1986 automatically when creating a signed tag, you can override the
1987 default selection with this variable. This option is passed
1988 unchanged to gpg's --local-user parameter, so you may specify a key
1989 using any method that gpg supports.
1992 Specify a web browser that may be used by some commands.
1993 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]