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 and only alphanumeric
16 characters are allowed. Some variables may appear multiple times.
21 The syntax is fairly flexible and permissive; whitespaces are mostly
22 ignored. The '#' and ';' characters begin comments to the end of line,
23 blank lines are ignored.
25 The file consists of sections and variables. A section begins with
26 the name of the section in square brackets and continues until the next
27 section begins. Section names are not case sensitive. Only alphanumeric
28 characters, `-` and `.` are allowed in section names. Each variable
29 must belong to some section, which means that there must be a section
30 header before the first setting of a variable.
32 Sections can be further divided into subsections. To begin a subsection
33 put its name in double quotes, separated by space from the section name,
34 in the section header, like in the example below:
37 [section "subsection"]
41 Subsection names are case sensitive and can contain any characters except
42 newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
43 respectively). Section headers cannot span multiple
44 lines. Variables may belong directly to a section or to a given subsection.
45 You can have `[section]` if you have `[section "subsection"]`, but you
48 There is also a deprecated `[section.subsection]` syntax. With this
49 syntax, the subsection name is converted to lower-case and is also
50 compared case sensitively. These subsection names follow the same
51 restrictions as section names.
53 All the other lines (and the remainder of the line after the section
54 header) are recognized as setting variables, in the form
55 'name = value'. If there is no equal sign on the line, the entire line
56 is taken as 'name' and the variable is recognized as boolean "true".
57 The variable names are case-insensitive and only alphanumeric
58 characters and `-` are allowed. There can be more than one value
59 for a given variable; we say then that variable is multivalued.
61 Leading and trailing whitespace in a variable value is discarded.
62 Internal whitespace within a variable value is retained verbatim.
64 The values following the equals sign in variable assign are all either
65 a string, an integer, or a boolean. Boolean values may be given as yes/no,
66 1/0, true/false or on/off. Case is not significant in boolean values, when
67 converting value to the canonical form using '--bool' type specifier;
68 'git config' will ensure that the output is "true" or "false".
70 String values may be entirely or partially enclosed in double quotes.
71 You need to enclose variable values in double quotes if you want to
72 preserve leading or trailing whitespace, or if the variable value contains
73 comment characters (i.e. it contains '#' or ';').
74 Double quote `"` and backslash `\` characters in variable values must
75 be escaped: use `\"` for `"` and `\\` for `\`.
77 The following escape sequences (beside `\"` and `\\`) are recognized:
78 `\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
79 and `\b` for backspace (BS). No other char escape sequence, nor octal
80 char sequences are valid.
82 Variable values ending in a `\` are continued on the next line in the
83 customary UNIX fashion.
85 Some variables may require a special value format.
90 You can include one config file from another by setting the special
91 `include.path` variable to the name of the file to be included. The
92 included file is expanded immediately, as if its contents had been
93 found at the location of the include directive. If the value of the
94 `include.path` variable is a relative path, the path is considered to be
95 relative to the configuration file in which the include directive was
96 found. See below for examples.
103 ; Don't trust file modes
108 external = /usr/local/bin/diff-wrapper
113 merge = refs/heads/devel
117 gitProxy="ssh" for "kernel.org"
118 gitProxy=default-proxy ; for the rest
121 path = /path/to/foo.inc ; include by absolute path
122 path = foo ; expand "foo" relative to the current file
127 Note that this list is non-comprehensive and not necessarily complete.
128 For command-specific variables, you will find a more detailed description
129 in the appropriate manual page. You will find a description of non-core
130 porcelain configuration variables in the respective porcelain documentation.
133 These variables control various optional help messages designed to
134 aid new users. All 'advice.*' variables default to 'true', and you
135 can tell Git that you do not need help by setting these to 'false':
139 Advice shown when linkgit:git-push[1] refuses
140 non-fast-forward refs.
142 Directions on how to stage/unstage/add shown in the
143 output of linkgit:git-status[1] and the template shown
144 when writing commit messages.
146 Advice shown when linkgit:git-merge[1] refuses to
147 merge to avoid overwriting local changes.
149 Advices shown by various commands when conflicts
150 prevent the operation from being performed.
152 Advice on how to set your identity configuration when
153 your information is guessed from the system username and
156 Advice shown when you used linkgit:git-checkout[1] to
157 move to the detach HEAD state, to instruct how to create
158 a local branch after the fact.
162 If false, the executable bit differences between the index and
163 the working tree are ignored; useful on broken filesystems like FAT.
164 See linkgit:git-update-index[1].
166 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
167 will probe and set core.fileMode false if appropriate when the
168 repository is created.
171 (Windows-only) If true (which is the default), mark newly-created
172 directories and files whose name starts with a dot as hidden.
173 If 'dotGitOnly', only the .git/ directory is hidden, but no other
174 files starting with a dot.
176 core.ignoreCygwinFSTricks::
177 This option is only used by Cygwin implementation of Git. If false,
178 the Cygwin stat() and lstat() functions are used. This may be useful
179 if your repository consists of a few separate directories joined in
180 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
181 whenever it is possible and falls back to Cygwin functions only to
182 handle symbol links. The native mode is more than twice faster than
183 normal Cygwin l/stat() functions. True by default, unless core.filemode
184 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
185 POSIX emulation is required to support core.filemode.
188 If true, this option enables various workarounds to enable
189 git to work better on filesystems that are not case sensitive,
190 like FAT. For example, if a directory listing finds
191 "makefile" when git expects "Makefile", git will assume
192 it is really the same file, and continue to remember it as
195 The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
196 will probe and set core.ignorecase true if appropriate when the repository
200 If false, the ctime differences between the index and the
201 working tree are ignored; useful when the inode change time
202 is regularly modified by something outside Git (file system
203 crawlers and some backup systems).
204 See linkgit:git-update-index[1]. True by default.
207 The commands that output paths (e.g. 'ls-files',
208 'diff'), when not given the `-z` option, will quote
209 "unusual" characters in the pathname by enclosing the
210 pathname in a double-quote pair and with backslashes the
211 same way strings in C source code are quoted. If this
212 variable is set to false, the bytes higher than 0x80 are
213 not quoted but output as verbatim. Note that double
214 quote, backslash and control characters are always
215 quoted without `-z` regardless of the setting of this
219 Sets the line ending type to use in the working directory for
220 files that have the `text` property set. Alternatives are
221 'lf', 'crlf' and 'native', which uses the platform's native
222 line ending. The default value is `native`. See
223 linkgit:gitattributes[5] for more information on end-of-line
227 If true, makes git check if converting `CRLF` is reversible when
228 end-of-line conversion is active. Git will verify if a command
229 modifies a file in the work tree either directly or indirectly.
230 For example, committing a file followed by checking out the
231 same file should yield the original file in the work tree. If
232 this is not the case for the current setting of
233 `core.autocrlf`, git will reject the file. The variable can
234 be set to "warn", in which case git will only warn about an
235 irreversible conversion but continue the operation.
237 CRLF conversion bears a slight chance of corrupting data.
238 When it is enabled, git will convert CRLF to LF during commit and LF to
239 CRLF during checkout. A file that contains a mixture of LF and
240 CRLF before the commit cannot be recreated by git. For text
241 files this is the right thing to do: it corrects line endings
242 such that we have only LF line endings in the repository.
243 But for binary files that are accidentally classified as text the
244 conversion can corrupt data.
246 If you recognize such corruption early you can easily fix it by
247 setting the conversion type explicitly in .gitattributes. Right
248 after committing you still have the original file in your work
249 tree and this file is not yet corrupted. You can explicitly tell
250 git that this file is binary and git will handle the file
253 Unfortunately, the desired effect of cleaning up text files with
254 mixed line endings and the undesired effect of corrupting binary
255 files cannot be distinguished. In both cases CRLFs are removed
256 in an irreversible way. For text files this is the right thing
257 to do because CRLFs are line endings, while for binary files
258 converting CRLFs corrupts data.
260 Note, this safety check does not mean that a checkout will generate a
261 file identical to the original file for a different setting of
262 `core.eol` and `core.autocrlf`, but only for the current one. For
263 example, a text file with `LF` would be accepted with `core.eol=lf`
264 and could later be checked out with `core.eol=crlf`, in which case the
265 resulting file would contain `CRLF`, although the original file
266 contained `LF`. However, in both work trees the line endings would be
267 consistent, that is either all `LF` or all `CRLF`, but never mixed. A
268 file with mixed line endings would be reported by the `core.safecrlf`
272 Setting this variable to "true" is almost the same as setting
273 the `text` attribute to "auto" on all files except that text
274 files are not guaranteed to be normalized: files that contain
275 `CRLF` in the repository will not be touched. Use this
276 setting if you want to have `CRLF` line endings in your
277 working directory even though the repository does not have
278 normalized line endings. This variable can be set to 'input',
279 in which case no output conversion is performed.
282 If false, symbolic links are checked out as small plain files that
283 contain the link text. linkgit:git-update-index[1] and
284 linkgit:git-add[1] will not change the recorded type to regular
285 file. Useful on filesystems like FAT that do not support
288 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
289 will probe and set core.symlinks false if appropriate when the repository
293 A "proxy command" to execute (as 'command host port') instead
294 of establishing direct connection to the remote server when
295 using the git protocol for fetching. If the variable value is
296 in the "COMMAND for DOMAIN" format, the command is applied only
297 on hostnames ending with the specified domain string. This variable
298 may be set multiple times and is matched in the given order;
299 the first match wins.
301 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
302 (which always applies universally, without the special "for"
305 The special string `none` can be used as the proxy command to
306 specify that no proxy be used for a given domain pattern.
307 This is useful for excluding servers inside a firewall from
308 proxy use, while defaulting to a common proxy for external domains.
311 If true, commands which modify both the working tree and the index
312 will mark the updated paths with the "assume unchanged" bit in the
313 index. These marked files are then assumed to stay unchanged in the
314 working tree, until you mark them otherwise manually - Git will not
315 detect the file changes by lstat() calls. This is useful on systems
316 where those are very slow, such as Microsoft Windows.
317 See linkgit:git-update-index[1].
320 core.preferSymlinkRefs::
321 Instead of the default "symref" format for HEAD
322 and other symbolic reference files, use symbolic links.
323 This is sometimes needed to work with old scripts that
324 expect HEAD to be a symbolic link.
327 If true this repository is assumed to be 'bare' and has no
328 working directory associated with it. If this is the case a
329 number of commands that require a working directory will be
330 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
332 This setting is automatically guessed by linkgit:git-clone[1] or
333 linkgit:git-init[1] when the repository was created. By default a
334 repository that ends in "/.git" is assumed to be not bare (bare =
335 false), while all other repositories are assumed to be bare (bare
339 Set the path to the root of the working tree.
340 This can be overridden by the GIT_WORK_TREE environment
341 variable and the '--work-tree' command line option.
342 The value can be an absolute path or relative to the path to
343 the .git directory, which is either specified by --git-dir
344 or GIT_DIR, or automatically discovered.
345 If --git-dir or GIT_DIR is specified but none of
346 --work-tree, GIT_WORK_TREE and core.worktree is specified,
347 the current working directory is regarded as the top level
348 of your working tree.
350 Note that this variable is honored even when set in a configuration
351 file in a ".git" subdirectory of a directory and its value differs
352 from the latter directory (e.g. "/path/to/.git/config" has
353 core.worktree set to "/different/path"), which is most likely a
354 misconfiguration. Running git commands in the "/path/to" directory will
355 still use "/different/path" as the root of the work tree and can cause
356 confusion unless you know what you are doing (e.g. you are creating a
357 read-only snapshot of the same index to a location different from the
358 repository's usual working tree).
360 core.logAllRefUpdates::
361 Enable the reflog. Updates to a ref <ref> is logged to the file
362 "$GIT_DIR/logs/<ref>", by appending the new and old
363 SHA1, the date/time and the reason of the update, but
364 only when the file exists. If this configuration
365 variable is set to true, missing "$GIT_DIR/logs/<ref>"
366 file is automatically created for branch heads (i.e. under
367 refs/heads/), remote refs (i.e. under refs/remotes/),
368 note refs (i.e. under refs/notes/), and the symbolic ref HEAD.
370 This information can be used to determine what commit
371 was the tip of a branch "2 days ago".
373 This value is true by default in a repository that has
374 a working directory associated with it, and false by
375 default in a bare repository.
377 core.repositoryFormatVersion::
378 Internal variable identifying the repository format and layout
381 core.sharedRepository::
382 When 'group' (or 'true'), the repository is made shareable between
383 several users in a group (making sure all the files and objects are
384 group-writable). When 'all' (or 'world' or 'everybody'), the
385 repository will be readable by all users, additionally to being
386 group-shareable. When 'umask' (or 'false'), git will use permissions
387 reported by umask(2). When '0xxx', where '0xxx' is an octal number,
388 files in the repository will have this mode value. '0xxx' will override
389 user's umask value (whereas the other options will only override
390 requested parts of the user's umask value). Examples: '0660' will make
391 the repo read/write-able for the owner and group, but inaccessible to
392 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
393 repository that is group-readable but not group-writable.
394 See linkgit:git-init[1]. False by default.
396 core.warnAmbiguousRefs::
397 If true, git will warn you if the ref name you passed it is ambiguous
398 and might match multiple refs in the .git/refs/ tree. True by default.
401 An integer -1..9, indicating a default compression level.
402 -1 is the zlib default. 0 means no compression,
403 and 1..9 are various speed/size tradeoffs, 9 being slowest.
404 If set, this provides a default to other compression variables,
405 such as 'core.loosecompression' and 'pack.compression'.
407 core.loosecompression::
408 An integer -1..9, indicating the compression level for objects that
409 are not in a pack file. -1 is the zlib default. 0 means no
410 compression, and 1..9 are various speed/size tradeoffs, 9 being
411 slowest. If not set, defaults to core.compression. If that is
412 not set, defaults to 1 (best speed).
414 core.packedGitWindowSize::
415 Number of bytes of a pack file to map into memory in a
416 single mapping operation. Larger window sizes may allow
417 your system to process a smaller number of large pack files
418 more quickly. Smaller window sizes will negatively affect
419 performance due to increased calls to the operating system's
420 memory manager, but may improve performance when accessing
421 a large number of large pack files.
423 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
424 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
425 be reasonable for all users/operating systems. You probably do
426 not need to adjust this value.
428 Common unit suffixes of 'k', 'm', or 'g' are supported.
430 core.packedGitLimit::
431 Maximum number of bytes to map simultaneously into memory
432 from pack files. If Git needs to access more than this many
433 bytes at once to complete an operation it will unmap existing
434 regions to reclaim virtual address space within the process.
436 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
437 This should be reasonable for all users/operating systems, except on
438 the largest projects. You probably do not need to adjust this value.
440 Common unit suffixes of 'k', 'm', or 'g' are supported.
442 core.deltaBaseCacheLimit::
443 Maximum number of bytes to reserve for caching base objects
444 that may be referenced by multiple deltified objects. By storing the
445 entire decompressed base objects in a cache Git is able
446 to avoid unpacking and decompressing frequently used base
447 objects multiple times.
449 Default is 16 MiB on all platforms. This should be reasonable
450 for all users/operating systems, except on the largest projects.
451 You probably do not need to adjust this value.
453 Common unit suffixes of 'k', 'm', or 'g' are supported.
455 core.bigFileThreshold::
456 Files larger than this size are stored deflated, without
457 attempting delta compression. Storing large files without
458 delta compression avoids excessive memory usage, at the
459 slight expense of increased disk usage.
461 Default is 512 MiB on all platforms. This should be reasonable
462 for most projects as source code and other text files can still
463 be delta compressed, but larger binary media files won't be.
465 Common unit suffixes of 'k', 'm', or 'g' are supported.
468 In addition to '.gitignore' (per-directory) and
469 '.git/info/exclude', git looks into this file for patterns
470 of files which are not meant to be tracked. "{tilde}/" is expanded
471 to the value of `$HOME` and "{tilde}user/" to the specified user's
472 home directory. See linkgit:gitignore[5].
475 Some commands (e.g. svn and http interfaces) that interactively
476 ask for a password can be told to use an external program given
477 via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
478 environment variable. If not set, fall back to the value of the
479 'SSH_ASKPASS' environment variable or, failing that, a simple password
480 prompt. The external program shall be given a suitable prompt as
481 command line argument and write the password on its STDOUT.
483 core.attributesfile::
484 In addition to '.gitattributes' (per-directory) and
485 '.git/info/attributes', git looks into this file for attributes
486 (see linkgit:gitattributes[5]). Path expansions are made the same
487 way as for `core.excludesfile`.
490 Commands such as `commit` and `tag` that lets you edit
491 messages by launching an editor uses the value of this
492 variable when it is set, and the environment variable
493 `GIT_EDITOR` is not set. See linkgit:git-var[1].
496 Text editor used by `git rebase -i` for editing the rebase insn file.
497 The value is meant to be interpreted by the shell when it is used.
498 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
499 When not configured the default commit message editor is used instead.
502 The command that git will use to paginate output. Can
503 be overridden with the `GIT_PAGER` environment
504 variable. Note that git sets the `LESS` environment
505 variable to `FRSX` if it is unset when it runs the
506 pager. One can change these settings by setting the
507 `LESS` variable to some other value. Alternately,
508 these settings can be overridden on a project or
509 global basis by setting the `core.pager` option.
510 Setting `core.pager` has no affect on the `LESS`
511 environment variable behaviour above, so if you want
512 to override git's default settings this way, you need
513 to be explicit. For example, to disable the S option
514 in a backward compatible manner, set `core.pager`
515 to `less -+$LESS -FRX`. This will be passed to the
516 shell by git, which will translate the final command to
517 `LESS=FRSX less -+FRSX -FRX`.
520 A comma separated list of common whitespace problems to
521 notice. 'git diff' will use `color.diff.whitespace` to
522 highlight them, and 'git apply --whitespace=error' will
523 consider them as errors. You can prefix `-` to disable
524 any of them (e.g. `-trailing-space`):
526 * `blank-at-eol` treats trailing whitespaces at the end of the line
527 as an error (enabled by default).
528 * `space-before-tab` treats a space character that appears immediately
529 before a tab character in the initial indent part of the line as an
530 error (enabled by default).
531 * `indent-with-non-tab` treats a line that is indented with 8 or more
532 space characters as an error (not enabled by default).
533 * `tab-in-indent` treats a tab character in the initial indent part of
534 the line as an error (not enabled by default).
535 * `blank-at-eof` treats blank lines added at the end of file as an error
536 (enabled by default).
537 * `trailing-space` is a short-hand to cover both `blank-at-eol` and
539 * `cr-at-eol` treats a carriage-return at the end of line as
540 part of the line terminator, i.e. with it, `trailing-space`
541 does not trigger if the character before such a carriage-return
542 is not a whitespace (not enabled by default).
543 * `tabwidth=<n>` tells how many character positions a tab occupies; this
544 is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent`
545 errors. The default tab width is 8. Allowed values are 1 to 63.
547 core.fsyncobjectfiles::
548 This boolean will enable 'fsync()' when writing object files.
550 This is a total waste of time and effort on a filesystem that orders
551 data writes properly, but can be useful for filesystems that do not use
552 journalling (traditional UNIX filesystems) or that only journal metadata
553 and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
556 Enable parallel index preload for operations like 'git diff'
558 This can speed up operations like 'git diff' and 'git status' especially
559 on filesystems like NFS that have weak caching semantics and thus
560 relatively high IO latencies. With this set to 'true', git will do the
561 index comparison to the filesystem data in parallel, allowing
565 You can set this to 'link', in which case a hardlink followed by
566 a delete of the source are used to make sure that object creation
567 will not overwrite existing objects.
569 On some file system/operating system combinations, this is unreliable.
570 Set this config setting to 'rename' there; However, This will remove the
571 check that makes sure that existing object files will not get overwritten.
574 When showing commit messages, also show notes which are stored in
575 the given ref. The ref must be fully qualified. If the given
576 ref does not exist, it is not an error but means that no
577 notes should be printed.
579 This setting defaults to "refs/notes/commits", and it can be overridden by
580 the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1].
582 core.sparseCheckout::
583 Enable "sparse checkout" feature. See section "Sparse checkout" in
584 linkgit:git-read-tree[1] for more information.
587 Set the length object names are abbreviated to. If unspecified,
588 many commands abbreviate to 7 hexdigits, which may not be enough
589 for abbreviated object names to stay unique for sufficiently long
594 Tells 'git add' to continue adding files when some files cannot be
595 added due to indexing errors. Equivalent to the '--ignore-errors'
596 option of linkgit:git-add[1]. Older versions of git accept only
597 `add.ignore-errors`, which does not follow the usual naming
598 convention for configuration variables. Newer versions of git
599 honor `add.ignoreErrors` as well.
602 Command aliases for the linkgit:git[1] command wrapper - e.g.
603 after defining "alias.last = cat-file commit HEAD", the invocation
604 "git last" is equivalent to "git cat-file commit HEAD". To avoid
605 confusion and troubles with script usage, aliases that
606 hide existing git commands are ignored. Arguments are split by
607 spaces, the usual shell quoting and escaping is supported.
608 quote pair and a backslash can be used to quote them.
610 If the alias expansion is prefixed with an exclamation point,
611 it will be treated as a shell command. For example, defining
612 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
613 "git new" is equivalent to running the shell command
614 "gitk --all --not ORIG_HEAD". Note that shell commands will be
615 executed from the top-level directory of a repository, which may
616 not necessarily be the current directory.
617 'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix'
618 from the original current directory. See linkgit:git-rev-parse[1].
621 If true, git-am will call git-mailsplit for patches in mbox format
622 with parameter '--keep-cr'. In this case git-mailsplit will
623 not remove `\r` from lines ending with `\r\n`. Can be overridden
624 by giving '--no-keep-cr' from the command line.
625 See linkgit:git-am[1], linkgit:git-mailsplit[1].
627 apply.ignorewhitespace::
628 When set to 'change', tells 'git apply' to ignore changes in
629 whitespace, in the same way as the '--ignore-space-change'
631 When set to one of: no, none, never, false tells 'git apply' to
632 respect all whitespace differences.
633 See linkgit:git-apply[1].
636 Tells 'git apply' how to handle whitespaces, in the same way
637 as the '--whitespace' option. See linkgit:git-apply[1].
639 branch.autosetupmerge::
640 Tells 'git branch' and 'git checkout' to set up new branches
641 so that linkgit:git-pull[1] will appropriately merge from the
642 starting point branch. Note that even if this option is not set,
643 this behavior can be chosen per-branch using the `--track`
644 and `--no-track` options. The valid settings are: `false` -- no
645 automatic setup is done; `true` -- automatic setup is done when the
646 starting point is a remote-tracking branch; `always` --
647 automatic setup is done when the starting point is either a
648 local branch or remote-tracking
649 branch. This option defaults to true.
651 branch.autosetuprebase::
652 When a new branch is created with 'git branch' or 'git checkout'
653 that tracks another branch, this variable tells git to set
654 up pull to rebase instead of merge (see "branch.<name>.rebase").
655 When `never`, rebase is never automatically set to true.
656 When `local`, rebase is set to true for tracked branches of
657 other local branches.
658 When `remote`, rebase is set to true for tracked branches of
659 remote-tracking branches.
660 When `always`, rebase will be set to true for all tracking
662 See "branch.autosetupmerge" for details on how to set up a
663 branch to track another branch.
664 This option defaults to never.
666 branch.<name>.remote::
667 When in branch <name>, it tells 'git fetch' and 'git push' which
668 remote to fetch from/push to. It defaults to `origin` if no remote is
669 configured. `origin` is also used if you are not on any branch.
671 branch.<name>.merge::
672 Defines, together with branch.<name>.remote, the upstream branch
673 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which
674 branch to merge and can also affect 'git push' (see push.default).
675 When in branch <name>, it tells 'git fetch' the default
676 refspec to be marked for merging in FETCH_HEAD. The value is
677 handled like the remote part of a refspec, and must match a
678 ref which is fetched from the remote given by
679 "branch.<name>.remote".
680 The merge information is used by 'git pull' (which at first calls
681 'git fetch') to lookup the default branch for merging. Without
682 this option, 'git pull' defaults to merge the first refspec fetched.
683 Specify multiple values to get an octopus merge.
684 If you wish to setup 'git pull' so that it merges into <name> from
685 another branch in the local repository, you can point
686 branch.<name>.merge to the desired branch, and use the special setting
687 `.` (a period) for branch.<name>.remote.
689 branch.<name>.mergeoptions::
690 Sets default options for merging into branch <name>. The syntax and
691 supported options are the same as those of linkgit:git-merge[1], but
692 option values containing whitespace characters are currently not
695 branch.<name>.rebase::
696 When true, rebase the branch <name> on top of the fetched branch,
697 instead of merging the default branch from the default remote when
698 "git pull" is run. See "pull.rebase" for doing this in a non
699 branch-specific manner.
701 *NOTE*: this is a possibly dangerous operation; do *not* use
702 it unless you understand the implications (see linkgit:git-rebase[1]
706 Specify the command to invoke the specified browser. The
707 specified command is evaluated in shell with the URLs passed
708 as arguments. (See linkgit:git-web{litdd}browse[1].)
710 browser.<tool>.path::
711 Override the path for the given tool that may be used to
712 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
713 working repository in gitweb (see linkgit:git-instaweb[1]).
716 A boolean to make git-clean do nothing unless given -f
717 or -n. Defaults to true.
720 A boolean to enable/disable color in the output of
721 linkgit:git-branch[1]. May be set to `always`,
722 `false` (or `never`) or `auto` (or `true`), in which case colors are used
723 only when the output is to a terminal. Defaults to false.
725 color.branch.<slot>::
726 Use customized color for branch coloration. `<slot>` is one of
727 `current` (the current branch), `local` (a local branch),
728 `remote` (a remote-tracking branch in refs/remotes/), `plain` (other
731 The value for these configuration variables is a list of colors (at most
732 two) and attributes (at most one), separated by spaces. The colors
733 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
734 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
735 `blink` and `reverse`. The first color given is the foreground; the
736 second is the background. The position of the attribute, if any,
740 Whether to use ANSI escape sequences to add color to patches.
741 If this is set to `always`, linkgit:git-diff[1],
742 linkgit:git-log[1], and linkgit:git-show[1] will use color
743 for all patches. If it is set to `true` or `auto`, those
744 commands will only use color when output is to the terminal.
747 This does not affect linkgit:git-format-patch[1] nor the
748 'git-diff-{asterisk}' plumbing commands. Can be overridden on the
749 command line with the `--color[=<when>]` option.
752 Use customized color for diff colorization. `<slot>` specifies
753 which part of the patch to use the specified color, and is one
754 of `plain` (context text), `meta` (metainformation), `frag`
755 (hunk header), 'func' (function in hunk header), `old` (removed lines),
756 `new` (added lines), `commit` (commit headers), or `whitespace`
757 (highlighting whitespace errors). The values of these variables may be
758 specified as in color.branch.<slot>.
760 color.decorate.<slot>::
761 Use customized color for 'git log --decorate' output. `<slot>` is one
762 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
763 branches, remote-tracking branches, tags, stash and HEAD, respectively.
766 When set to `always`, always highlight matches. When `false` (or
767 `never`), never. When set to `true` or `auto`, use color only
768 when the output is written to the terminal. Defaults to `false`.
771 Use customized color for grep colorization. `<slot>` specifies which
772 part of the line to use the specified color, and is one of
776 non-matching text in context lines (when using `-A`, `-B`, or `-C`)
778 filename prefix (when not using `-h`)
780 function name lines (when using `-p`)
782 line number prefix (when using `-n`)
786 non-matching text in selected lines
788 separators between fields on a line (`:`, `-`, and `=`)
789 and between hunks (`--`)
792 The values of these variables may be specified as in color.branch.<slot>.
795 When set to `always`, always use colors for interactive prompts
796 and displays (such as those used by "git-add --interactive").
797 When false (or `never`), never. When set to `true` or `auto`, use
798 colors only when the output is to the terminal. Defaults to false.
800 color.interactive.<slot>::
801 Use customized color for 'git add --interactive'
802 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
803 four distinct types of normal output from interactive
804 commands. The values of these variables may be specified as
805 in color.branch.<slot>.
808 A boolean to enable/disable colored output when the pager is in
809 use (default is true).
812 A boolean to enable/disable color in the output of
813 linkgit:git-show-branch[1]. May be set to `always`,
814 `false` (or `never`) or `auto` (or `true`), in which case colors are used
815 only when the output is to a terminal. Defaults to false.
818 A boolean to enable/disable color in the output of
819 linkgit:git-status[1]. May be set to `always`,
820 `false` (or `never`) or `auto` (or `true`), in which case colors are used
821 only when the output is to a terminal. Defaults to false.
823 color.status.<slot>::
824 Use customized color for status colorization. `<slot>` is
825 one of `header` (the header text of the status message),
826 `added` or `updated` (files which are added but not committed),
827 `changed` (files which are changed but not added in the index),
828 `untracked` (files which are not tracked by git),
829 `branch` (the current branch), or
830 `nobranch` (the color the 'no branch' warning is shown in, defaulting
831 to red). The values of these variables may be specified as in
835 This variable determines the default value for variables such
836 as `color.diff` and `color.grep` that control the use of color
837 per command family. Its scope will expand as more commands learn
838 configuration to set a default for the `--color` option. Set it
839 to `always` if you want all output not intended for machine
840 consumption to use color, to `true` or `auto` if you want such
841 output to use color when written to the terminal, or to `false` or
842 `never` if you prefer git commands not to use color unless enabled
843 explicitly with some other configuration or the `--color` option.
846 A boolean to enable/disable inclusion of status information in the
847 commit message template when using an editor to prepare the commit
848 message. Defaults to true.
851 Specify a file to use as the template for new commit messages.
852 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the
853 specified user's home directory.
856 Specify an external helper to be called when a username or
857 password credential is needed; the helper may consult external
858 storage to avoid prompting the user for the credentials. See
859 linkgit:gitcredentials[7] for details.
861 credential.useHttpPath::
862 When acquiring credentials, consider the "path" component of an http
863 or https URL to be important. Defaults to false. See
864 linkgit:gitcredentials[7] for more information.
866 credential.username::
867 If no username is set for a network authentication, use this username
868 by default. See credential.<context>.* below, and
869 linkgit:gitcredentials[7].
872 Any of the credential.* options above can be applied selectively to
873 some credentials. For example "credential.https://example.com.username"
874 would set the default username only for https connections to
875 example.com. See linkgit:gitcredentials[7] for details on how URLs are
878 include::diff-config.txt[]
880 difftool.<tool>.path::
881 Override the path for the given tool. This is useful in case
882 your tool is not in the PATH.
884 difftool.<tool>.cmd::
885 Specify the command to invoke the specified diff tool.
886 The specified command is evaluated in shell with the following
887 variables available: 'LOCAL' is set to the name of the temporary
888 file containing the contents of the diff pre-image and 'REMOTE'
889 is set to the name of the temporary file containing the contents
890 of the diff post-image.
893 Prompt before each invocation of the diff tool.
896 A POSIX Extended Regular Expression used to determine what is a "word"
897 when performing word-by-word difference calculations. Character
898 sequences that match the regular expression are "words", all other
899 characters are *ignorable* whitespace.
901 fetch.recurseSubmodules::
902 This option can be either set to a boolean value or to 'on-demand'.
903 Setting it to a boolean changes the behavior of fetch and pull to
904 unconditionally recurse into submodules when set to true or to not
905 recurse at all when set to false. When set to 'on-demand' (the default
906 value), fetch and pull will only recurse into a populated submodule
907 when its superproject retrieves a commit that updates the submodule's
911 If it is set to true, git-fetch-pack will check all fetched
912 objects. It will abort in the case of a malformed object or a
913 broken link. The result of an abort are only dangling objects.
914 Defaults to false. If not set, the value of `transfer.fsckObjects`
918 If the number of objects fetched over the git native
919 transfer is below this
920 limit, then the objects will be unpacked into loose object
921 files. However if the number of received objects equals or
922 exceeds this limit then the received pack will be stored as
923 a pack, after adding any missing delta bases. Storing the
924 pack from a push can make the push operation complete faster,
925 especially on slow filesystems. If not set, the value of
926 `transfer.unpackLimit` is used instead.
929 Enable multipart/mixed attachments as the default for
930 'format-patch'. The value can also be a double quoted string
931 which will enable attachments as the default and set the
932 value as the boundary. See the --attach option in
933 linkgit:git-format-patch[1].
936 A boolean which can enable or disable sequence numbers in patch
937 subjects. It defaults to "auto" which enables it only if there
938 is more than one patch. It can be enabled or disabled for all
939 messages by setting it to "true" or "false". See --numbered
940 option in linkgit:git-format-patch[1].
943 Additional email headers to include in a patch to be submitted
944 by mail. See linkgit:git-format-patch[1].
948 Additional recipients to include in a patch to be submitted
949 by mail. See the --to and --cc options in
950 linkgit:git-format-patch[1].
952 format.subjectprefix::
953 The default for format-patch is to output files with the '[PATCH]'
954 subject prefix. Use this variable to change that prefix.
957 The default for format-patch is to output a signature containing
958 the git version number. Use this variable to change that default.
959 Set this variable to the empty string ("") to suppress
960 signature generation.
963 The default for format-patch is to output files with the suffix
964 `.patch`. Use this variable to change that suffix (make sure to
965 include the dot if you want it).
968 The default pretty format for log/show/whatchanged command,
969 See linkgit:git-log[1], linkgit:git-show[1],
970 linkgit:git-whatchanged[1].
973 The default threading style for 'git format-patch'. Can be
974 a boolean value, or `shallow` or `deep`. `shallow` threading
975 makes every mail a reply to the head of the series,
976 where the head is chosen from the cover letter, the
977 `\--in-reply-to`, and the first patch mail, in this order.
978 `deep` threading makes every mail a reply to the previous one.
979 A true boolean value is the same as `shallow`, and a false
980 value disables threading.
983 A boolean value which lets you enable the `-s/--signoff` option of
984 format-patch by default. *Note:* Adding the Signed-off-by: line to a
985 patch should be a conscious act and means that you certify you have
986 the rights to submit this work under the same open source license.
987 Please see the 'SubmittingPatches' document for further discussion.
989 filter.<driver>.clean::
990 The command which is used to convert the content of a worktree
991 file to a blob upon checkin. See linkgit:gitattributes[5] for
994 filter.<driver>.smudge::
995 The command which is used to convert the content of a blob
996 object to a worktree file upon checkout. See
997 linkgit:gitattributes[5] for details.
999 gc.aggressiveWindow::
1000 The window size parameter used in the delta compression
1001 algorithm used by 'git gc --aggressive'. This defaults
1005 When there are approximately more than this many loose
1006 objects in the repository, `git gc --auto` will pack them.
1007 Some Porcelain commands use this command to perform a
1008 light-weight garbage collection from time to time. The
1009 default value is 6700. Setting this to 0 disables it.
1012 When there are more than this many packs that are not
1013 marked with `*.keep` file in the repository, `git gc
1014 --auto` consolidates them into one larger pack. The
1015 default value is 50. Setting this to 0 disables it.
1018 Running `git pack-refs` in a repository renders it
1019 unclonable by Git versions prior to 1.5.1.2 over dumb
1020 transports such as HTTP. This variable determines whether
1021 'git gc' runs `git pack-refs`. This can be set to `notbare`
1022 to enable it within all non-bare repos or it can be set to a
1023 boolean value. The default is `true`.
1026 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
1027 Override the grace period with this config variable. The value
1028 "now" may be used to disable this grace period and always prune
1029 unreachable objects immediately.
1032 gc.<pattern>.reflogexpire::
1033 'git reflog expire' removes reflog entries older than
1034 this time; defaults to 90 days. With "<pattern>" (e.g.
1035 "refs/stash") in the middle the setting applies only to
1036 the refs that match the <pattern>.
1038 gc.reflogexpireunreachable::
1039 gc.<ref>.reflogexpireunreachable::
1040 'git reflog expire' removes reflog entries older than
1041 this time and are not reachable from the current tip;
1042 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")
1043 in the middle, the setting applies only to the refs that
1044 match the <pattern>.
1047 Records of conflicted merge you resolved earlier are
1048 kept for this many days when 'git rerere gc' is run.
1049 The default is 60 days. See linkgit:git-rerere[1].
1051 gc.rerereunresolved::
1052 Records of conflicted merge you have not resolved are
1053 kept for this many days when 'git rerere gc' is run.
1054 The default is 15 days. See linkgit:git-rerere[1].
1056 gitcvs.commitmsgannotation::
1057 Append this string to each commit message. Set to empty string
1058 to disable this feature. Defaults to "via git-CVS emulator".
1061 Whether the CVS server interface is enabled for this repository.
1062 See linkgit:git-cvsserver[1].
1065 Path to a log file where the CVS server interface well... logs
1066 various stuff. See linkgit:git-cvsserver[1].
1068 gitcvs.usecrlfattr::
1069 If true, the server will look up the end-of-line conversion
1070 attributes for files to determine the '-k' modes to use. If
1071 the attributes force git to treat a file as text,
1072 the '-k' mode will be left blank so CVS clients will
1073 treat it as text. If they suppress text conversion, the file
1074 will be set with '-kb' mode, which suppresses any newline munging
1075 the client might otherwise do. If the attributes do not allow
1076 the file type to be determined, then 'gitcvs.allbinary' is
1077 used. See linkgit:gitattributes[5].
1080 This is used if 'gitcvs.usecrlfattr' does not resolve
1081 the correct '-kb' mode to use. If true, all
1082 unresolved files are sent to the client in
1083 mode '-kb'. This causes the client to treat them
1084 as binary files, which suppresses any newline munging it
1085 otherwise might do. Alternatively, if it is set to "guess",
1086 then the contents of the file are examined to decide if
1087 it is binary, similar to 'core.autocrlf'.
1090 Database used by git-cvsserver to cache revision information
1091 derived from the git repository. The exact meaning depends on the
1092 used database driver, for SQLite (which is the default driver) this
1093 is a filename. Supports variable substitution (see
1094 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1095 Default: '%Ggitcvs.%m.sqlite'
1098 Used Perl DBI driver. You can specify any available driver
1099 for this here, but it might not work. git-cvsserver is tested
1100 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1101 reported *not* to work with 'DBD::mysql'. Experimental feature.
1102 May not contain double colons (`:`). Default: 'SQLite'.
1103 See linkgit:git-cvsserver[1].
1105 gitcvs.dbuser, gitcvs.dbpass::
1106 Database user and password. Only useful if setting 'gitcvs.dbdriver',
1107 since SQLite has no concept of database users and/or passwords.
1108 'gitcvs.dbuser' supports variable substitution (see
1109 linkgit:git-cvsserver[1] for details).
1111 gitcvs.dbTableNamePrefix::
1112 Database table name prefix. Prepended to the names of any
1113 database tables used, allowing a single database to be used
1114 for several repositories. Supports variable substitution (see
1115 linkgit:git-cvsserver[1] for details). Any non-alphabetic
1116 characters will be replaced with underscores.
1118 All gitcvs variables except for 'gitcvs.usecrlfattr' and
1119 'gitcvs.allbinary' can also be specified as
1120 'gitcvs.<access_method>.<varname>' (where 'access_method'
1121 is one of "ext" and "pserver") to make them apply only for the given
1125 gitweb.description::
1128 See linkgit:gitweb[1] for description.
1136 gitweb.remote_heads::
1139 See linkgit:gitweb.conf[5] for description.
1142 If set to true, enable '-n' option by default.
1144 grep.extendedRegexp::
1145 If set to true, enable '--extended-regexp' option by default.
1148 Use this custom program instead of "gpg" found on $PATH when
1149 making or verifying a PGP signature. The program must support the
1150 same command line interface as GPG, namely, to verify a detached
1151 signature, "gpg --verify $file - <$signature" is run, and the
1152 program is expected to signal a good signature by exiting with
1153 code 0, and to generate an ascii-armored detached signature, the
1154 standard input of "gpg -bsau $key" is fed with the contents to be
1155 signed, and the program is expected to send the result to its
1158 gui.commitmsgwidth::
1159 Defines how wide the commit message window is in the
1160 linkgit:git-gui[1]. "75" is the default.
1163 Specifies how many context lines should be used in calls to diff
1164 made by the linkgit:git-gui[1]. The default is "5".
1167 Specifies the default encoding to use for displaying of
1168 file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1169 It can be overridden by setting the 'encoding' attribute
1170 for relevant files (see linkgit:gitattributes[5]).
1171 If this option is not set, the tools default to the
1174 gui.matchtrackingbranch::
1175 Determines if new branches created with linkgit:git-gui[1] should
1176 default to tracking remote branches with matching names or
1177 not. Default: "false".
1179 gui.newbranchtemplate::
1180 Is used as suggested name when creating new branches using the
1183 gui.pruneduringfetch::
1184 "true" if linkgit:git-gui[1] should prune remote-tracking branches when
1185 performing a fetch. The default value is "false".
1188 Determines if linkgit:git-gui[1] should trust the file modification
1189 timestamp or not. By default the timestamps are not trusted.
1191 gui.spellingdictionary::
1192 Specifies the dictionary used for spell checking commit messages in
1193 the linkgit:git-gui[1]. When set to "none" spell checking is turned
1197 If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1198 location detection. It makes blame significantly faster on huge
1199 repositories at the expense of less thorough copy detection.
1201 gui.copyblamethreshold::
1202 Specifies the threshold to use in 'git gui blame' original location
1203 detection, measured in alphanumeric characters. See the
1204 linkgit:git-blame[1] manual for more information on copy detection.
1206 gui.blamehistoryctx::
1207 Specifies the radius of history context in days to show in
1208 linkgit:gitk[1] for the selected commit, when the `Show History
1209 Context` menu item is invoked from 'git gui blame'. If this
1210 variable is set to zero, the whole history is shown.
1212 guitool.<name>.cmd::
1213 Specifies the shell command line to execute when the corresponding item
1214 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1215 mandatory for every tool. The command is executed from the root of
1216 the working directory, and in the environment it receives the name of
1217 the tool as 'GIT_GUITOOL', the name of the currently selected file as
1218 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1219 the head is detached, 'CUR_BRANCH' is empty).
1221 guitool.<name>.needsfile::
1222 Run the tool only if a diff is selected in the GUI. It guarantees
1223 that 'FILENAME' is not empty.
1225 guitool.<name>.noconsole::
1226 Run the command silently, without creating a window to display its
1229 guitool.<name>.norescan::
1230 Don't rescan the working directory for changes after the tool
1233 guitool.<name>.confirm::
1234 Show a confirmation dialog before actually running the tool.
1236 guitool.<name>.argprompt::
1237 Request a string argument from the user, and pass it to the tool
1238 through the 'ARGS' environment variable. Since requesting an
1239 argument implies confirmation, the 'confirm' option has no effect
1240 if this is enabled. If the option is set to 'true', 'yes', or '1',
1241 the dialog uses a built-in generic prompt; otherwise the exact
1242 value of the variable is used.
1244 guitool.<name>.revprompt::
1245 Request a single valid revision from the user, and set the
1246 'REVISION' environment variable. In other aspects this option
1247 is similar to 'argprompt', and can be used together with it.
1249 guitool.<name>.revunmerged::
1250 Show only unmerged branches in the 'revprompt' subdialog.
1251 This is useful for tools similar to merge or rebase, but not
1252 for things like checkout or reset.
1254 guitool.<name>.title::
1255 Specifies the title to use for the prompt dialog. The default
1258 guitool.<name>.prompt::
1259 Specifies the general prompt string to display at the top of
1260 the dialog, before subsections for 'argprompt' and 'revprompt'.
1261 The default value includes the actual command.
1264 Specify the browser that will be used to display help in the
1265 'web' format. See linkgit:git-help[1].
1268 Override the default help format used by linkgit:git-help[1].
1269 Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1270 the default. 'web' and 'html' are the same.
1273 Automatically correct and execute mistyped commands after
1274 waiting for the given number of deciseconds (0.1 sec). If more
1275 than one command can be deduced from the entered text, nothing
1276 will be executed. If the value of this option is negative,
1277 the corrected command will be executed immediately. If the
1278 value is 0 - the command will be just shown but not executed.
1279 This is the default.
1282 Override the HTTP proxy, normally configured using the 'http_proxy'
1283 environment variable (see linkgit:curl[1]). This can be overridden
1284 on a per-remote basis; see remote.<name>.proxy
1287 File containing previously stored cookie lines which should be used
1288 in the git http session, if they match the server. The file format
1289 of the file to read cookies from should be plain HTTP headers or
1290 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
1291 NOTE that the file specified with http.cookiefile is only used as
1292 input. No cookies will be stored in the file.
1295 Whether to verify the SSL certificate when fetching or pushing
1296 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1300 File containing the SSL certificate when fetching or pushing
1301 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1305 File containing the SSL private key when fetching or pushing
1306 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1309 http.sslCertPasswordProtected::
1310 Enable git's password prompt for the SSL certificate. Otherwise
1311 OpenSSL will prompt the user, possibly many times, if the
1312 certificate or private key is encrypted. Can be overridden by the
1313 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1316 File containing the certificates to verify the peer with when
1317 fetching or pushing over HTTPS. Can be overridden by the
1318 'GIT_SSL_CAINFO' environment variable.
1321 Path containing files with the CA certificates to verify the peer
1322 with when fetching or pushing over HTTPS. Can be overridden
1323 by the 'GIT_SSL_CAPATH' environment variable.
1326 How many HTTP requests to launch in parallel. Can be overridden
1327 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1330 The number of curl sessions (counted across slots) to be kept across
1331 requests. They will not be ended with curl_easy_cleanup() until
1332 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1333 value will be capped at 1. Defaults to 1.
1336 Maximum size in bytes of the buffer used by smart HTTP
1337 transports when POSTing data to the remote system.
1338 For requests larger than this buffer size, HTTP/1.1 and
1339 Transfer-Encoding: chunked is used to avoid creating a
1340 massive pack file locally. Default is 1 MiB, which is
1341 sufficient for most requests.
1343 http.lowSpeedLimit, http.lowSpeedTime::
1344 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1345 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1346 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1347 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1350 A boolean which disables using of EPSV ftp command by curl.
1351 This can helpful with some "poor" ftp servers which don't
1352 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1353 environment variable. Default is false (curl will use EPSV).
1356 The HTTP USER_AGENT string presented to an HTTP server. The default
1357 value represents the version of the client git such as git/1.7.1.
1358 This option allows you to override this value to a more common value
1359 such as Mozilla/4.0. This may be necessary, for instance, if
1360 connecting through a firewall that restricts HTTP connections to a set
1361 of common USER_AGENT strings (but not including those like git/1.7.1).
1362 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1364 i18n.commitEncoding::
1365 Character encoding the commit messages are stored in; git itself
1366 does not care per se, but this information is necessary e.g. when
1367 importing commits from emails or in the gitk graphical history
1368 browser (and possibly at other places in the future or in other
1369 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1371 i18n.logOutputEncoding::
1372 Character encoding the commit messages are converted to when
1373 running 'git log' and friends.
1376 The configuration variables in the 'imap' section are described
1377 in linkgit:git-imap-send[1].
1380 Specify the directory from which templates will be copied.
1381 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1384 Specify the program that will be used to browse your working
1385 repository in gitweb. See linkgit:git-instaweb[1].
1388 The HTTP daemon command-line to start gitweb on your working
1389 repository. See linkgit:git-instaweb[1].
1392 If true the web server started by linkgit:git-instaweb[1] will
1393 be bound to the local IP (127.0.0.1).
1395 instaweb.modulepath::
1396 The default module path for linkgit:git-instaweb[1] to use
1397 instead of /usr/lib/apache2/modules. Only used if httpd
1401 The port number to bind the gitweb httpd to. See
1402 linkgit:git-instaweb[1].
1404 interactive.singlekey::
1405 In interactive commands, allow the user to provide one-letter
1406 input with a single key (i.e., without hitting enter).
1407 Currently this is used by the `\--patch` mode of
1408 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],
1409 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this
1410 setting is silently ignored if portable keystroke input
1414 If true, makes linkgit:git-log[1], linkgit:git-show[1], and
1415 linkgit:git-whatchanged[1] assume `\--abbrev-commit`. You may
1416 override this option with `\--no-abbrev-commit`.
1419 Set the default date-time mode for the 'log' command.
1420 Setting a value for log.date is similar to using 'git log''s
1421 `\--date` option. Possible values are `relative`, `local`,
1422 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1426 Print out the ref names of any commits that are shown by the log
1427 command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1428 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1429 specified, the full ref name (including prefix) will be printed.
1430 This is the same as the log commands '--decorate' option.
1433 If true, the initial commit will be shown as a big creation event.
1434 This is equivalent to a diff against an empty tree.
1435 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1436 normally hide the root commit will now show it. True by default.
1439 The location of an augmenting mailmap file. The default
1440 mailmap, located in the root of the repository, is loaded
1441 first, then the mailmap file pointed to by this variable.
1442 The location of the mailmap file may be in a repository
1443 subdirectory, or somewhere outside of the repository itself.
1444 See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1447 Specify the programs that may be used to display help in the
1448 'man' format. See linkgit:git-help[1].
1451 Specify the command to invoke the specified man viewer. The
1452 specified command is evaluated in shell with the man page
1453 passed as argument. (See linkgit:git-help[1].)
1456 Override the path for the given tool that may be used to
1457 display help in the 'man' format. See linkgit:git-help[1].
1459 include::merge-config.txt[]
1461 mergetool.<tool>.path::
1462 Override the path for the given tool. This is useful in case
1463 your tool is not in the PATH.
1465 mergetool.<tool>.cmd::
1466 Specify the command to invoke the specified merge tool. The
1467 specified command is evaluated in shell with the following
1468 variables available: 'BASE' is the name of a temporary file
1469 containing the common base of the files to be merged, if available;
1470 'LOCAL' is the name of a temporary file containing the contents of
1471 the file on the current branch; 'REMOTE' is the name of a temporary
1472 file containing the contents of the file from the branch being
1473 merged; 'MERGED' contains the name of the file to which the merge
1474 tool should write the results of a successful merge.
1476 mergetool.<tool>.trustExitCode::
1477 For a custom merge command, specify whether the exit code of
1478 the merge command can be used to determine whether the merge was
1479 successful. If this is not set to true then the merge target file
1480 timestamp is checked and the merge assumed to have been successful
1481 if the file has been updated, otherwise the user is prompted to
1482 indicate the success of the merge.
1484 mergetool.keepBackup::
1485 After performing a merge, the original file with conflict markers
1486 can be saved as a file with a `.orig` extension. If this variable
1487 is set to `false` then this file is not preserved. Defaults to
1488 `true` (i.e. keep the backup files).
1490 mergetool.keepTemporaries::
1491 When invoking a custom merge tool, git uses a set of temporary
1492 files to pass to the tool. If the tool returns an error and this
1493 variable is set to `true`, then these temporary files will be
1494 preserved, otherwise they will be removed after the tool has
1495 exited. Defaults to `false`.
1498 Prompt before each invocation of the merge resolution program.
1501 The (fully qualified) refname from which to show notes when
1502 showing commit messages. The value of this variable can be set
1503 to a glob, in which case notes from all matching refs will be
1504 shown. You may also specify this configuration variable
1505 several times. A warning will be issued for refs that do not
1506 exist, but a glob that does not match any refs is silently
1509 This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1510 environment variable, which must be a colon separated list of refs or
1513 The effective value of "core.notesRef" (possibly overridden by
1514 GIT_NOTES_REF) is also implicitly added to the list of refs to be
1517 notes.rewrite.<command>::
1518 When rewriting commits with <command> (currently `amend` or
1519 `rebase`) and this variable is set to `true`, git
1520 automatically copies your notes from the original to the
1521 rewritten commit. Defaults to `true`, but see
1522 "notes.rewriteRef" below.
1525 When copying notes during a rewrite (see the
1526 "notes.rewrite.<command>" option), determines what to do if
1527 the target commit already has a note. Must be one of
1528 `overwrite`, `concatenate`, or `ignore`. Defaults to
1531 This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1532 environment variable.
1535 When copying notes during a rewrite, specifies the (fully
1536 qualified) ref whose notes should be copied. The ref may be a
1537 glob, in which case notes in all matching refs will be copied.
1538 You may also specify this configuration several times.
1540 Does not have a default value; you must configure this variable to
1541 enable note rewriting. Set it to `refs/notes/commits` to enable
1542 rewriting for the default commit notes.
1544 This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1545 environment variable, which must be a colon separated list of refs or
1549 The size of the window used by linkgit:git-pack-objects[1] when no
1550 window size is given on the command line. Defaults to 10.
1553 The maximum delta depth used by linkgit:git-pack-objects[1] when no
1554 maximum depth is given on the command line. Defaults to 50.
1557 The window memory size limit used by linkgit:git-pack-objects[1]
1558 when no limit is given on the command line. The value can be
1559 suffixed with "k", "m", or "g". Defaults to 0, meaning no
1563 An integer -1..9, indicating the compression level for objects
1564 in a pack file. -1 is the zlib default. 0 means no
1565 compression, and 1..9 are various speed/size tradeoffs, 9 being
1566 slowest. If not set, defaults to core.compression. If that is
1567 not set, defaults to -1, the zlib default, which is "a default
1568 compromise between speed and compression (currently equivalent
1571 Note that changing the compression level will not automatically recompress
1572 all existing objects. You can force recompression by passing the -F option
1573 to linkgit:git-repack[1].
1575 pack.deltaCacheSize::
1576 The maximum memory in bytes used for caching deltas in
1577 linkgit:git-pack-objects[1] before writing them out to a pack.
1578 This cache is used to speed up the writing object phase by not
1579 having to recompute the final delta result once the best match
1580 for all objects is found. Repacking large repositories on machines
1581 which are tight with memory might be badly impacted by this though,
1582 especially if this cache pushes the system into swapping.
1583 A value of 0 means no limit. The smallest size of 1 byte may be
1584 used to virtually disable this cache. Defaults to 256 MiB.
1586 pack.deltaCacheLimit::
1587 The maximum size of a delta, that is cached in
1588 linkgit:git-pack-objects[1]. This cache is used to speed up the
1589 writing object phase by not having to recompute the final delta
1590 result once the best match for all objects is found. Defaults to 1000.
1593 Specifies the number of threads to spawn when searching for best
1594 delta matches. This requires that linkgit:git-pack-objects[1]
1595 be compiled with pthreads otherwise this option is ignored with a
1596 warning. This is meant to reduce packing time on multiprocessor
1597 machines. The required amount of memory for the delta search window
1598 is however multiplied by the number of threads.
1599 Specifying 0 will cause git to auto-detect the number of CPU's
1600 and set the number of threads accordingly.
1603 Specify the default pack index version. Valid values are 1 for
1604 legacy pack index used by Git versions prior to 1.5.2, and 2 for
1605 the new pack index with capabilities for packs larger than 4 GB
1606 as well as proper protection against the repacking of corrupted
1607 packs. Version 2 is the default. Note that version 2 is enforced
1608 and this config option ignored whenever the corresponding pack is
1611 If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1612 cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1613 that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1614 other side may give you a repository that cannot be accessed with your
1615 older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1616 you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1617 the `{asterisk}.idx` file.
1619 pack.packSizeLimit::
1620 The maximum size of a pack. This setting only affects
1621 packing to a file when repacking, i.e. the git:// protocol
1622 is unaffected. It can be overridden by the `\--max-pack-size`
1623 option of linkgit:git-repack[1]. The minimum size allowed is
1624 limited to 1 MiB. The default is unlimited.
1625 Common unit suffixes of 'k', 'm', or 'g' are
1629 If the value is boolean, turns on or off pagination of the
1630 output of a particular git subcommand when writing to a tty.
1631 Otherwise, turns on pagination for the subcommand using the
1632 pager specified by the value of `pager.<cmd>`. If `\--paginate`
1633 or `\--no-pager` is specified on the command line, it takes
1634 precedence over this option. To disable pagination for all
1635 commands, set `core.pager` or `GIT_PAGER` to `cat`.
1638 Alias for a --pretty= format string, as specified in
1639 linkgit:git-log[1]. Any aliases defined here can be used just
1640 as the built-in pretty formats could. For example,
1641 running `git config pretty.changelog "format:{asterisk} %H %s"`
1642 would cause the invocation `git log --pretty=changelog`
1643 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.
1644 Note that an alias with the same name as a built-in format
1645 will be silently ignored.
1648 When true, rebase branches on top of the fetched branch, instead
1649 of merging the default branch from the default remote when "git
1650 pull" is run. See "branch.<name>.rebase" for setting this on a
1653 *NOTE*: this is a possibly dangerous operation; do *not* use
1654 it unless you understand the implications (see linkgit:git-rebase[1]
1658 The default merge strategy to use when pulling multiple branches
1662 The default merge strategy to use when pulling a single branch.
1665 Defines the action git push should take if no refspec is given
1666 on the command line, no refspec is configured in the remote, and
1667 no refspec is implied by any of the options given on the command
1668 line. Possible values are:
1670 * `nothing` - do not push anything.
1671 * `matching` - push all matching branches.
1672 All branches having the same name in both ends are considered to be
1673 matching. This is the default.
1674 * `upstream` - push the current branch to its upstream branch.
1675 * `tracking` - deprecated synonym for `upstream`.
1676 * `current` - push the current branch to a branch of the same name.
1679 Whether to show a diffstat of what changed upstream since the last
1680 rebase. False by default.
1683 If set to true enable '--autosquash' option by default.
1686 By default, git-receive-pack will run "git-gc --auto" after
1687 receiving data from git-push and updating refs. You can stop
1688 it by setting this variable to false.
1690 receive.fsckObjects::
1691 If it is set to true, git-receive-pack will check all received
1692 objects. It will abort in the case of a malformed object or a
1693 broken link. The result of an abort are only dangling objects.
1694 Defaults to false. If not set, the value of `transfer.fsckObjects`
1697 receive.unpackLimit::
1698 If the number of objects received in a push is below this
1699 limit then the objects will be unpacked into loose object
1700 files. However if the number of received objects equals or
1701 exceeds this limit then the received pack will be stored as
1702 a pack, after adding any missing delta bases. Storing the
1703 pack from a push can make the push operation complete faster,
1704 especially on slow filesystems. If not set, the value of
1705 `transfer.unpackLimit` is used instead.
1707 receive.denyDeletes::
1708 If set to true, git-receive-pack will deny a ref update that deletes
1709 the ref. Use this to prevent such a ref deletion via a push.
1711 receive.denyDeleteCurrent::
1712 If set to true, git-receive-pack will deny a ref update that
1713 deletes the currently checked out branch of a non-bare repository.
1715 receive.denyCurrentBranch::
1716 If set to true or "refuse", git-receive-pack will deny a ref update
1717 to the currently checked out branch of a non-bare repository.
1718 Such a push is potentially dangerous because it brings the HEAD
1719 out of sync with the index and working tree. If set to "warn",
1720 print a warning of such a push to stderr, but allow the push to
1721 proceed. If set to false or "ignore", allow such pushes with no
1722 message. Defaults to "refuse".
1724 There are two more options that are meant for Git experts: "updateInstead"
1725 which will run `read-tree -u -m HEAD` and "detachInstead" which will detach
1726 the HEAD so it does not need to change. Both options come with their own
1727 set of possible *complications*, but can be appropriate in rare workflows.
1729 receive.denyNonFastForwards::
1730 If set to true, git-receive-pack will deny a ref update which is
1731 not a fast-forward. Use this to prevent such an update via a push,
1732 even if that push is forced. This configuration variable is
1733 set when initializing a shared repository.
1735 receive.updateserverinfo::
1736 If set to true, git-receive-pack will run git-update-server-info
1737 after receiving data from git-push and updating refs.
1740 The URL of a remote repository. See linkgit:git-fetch[1] or
1741 linkgit:git-push[1].
1743 remote.<name>.pushurl::
1744 The push URL of a remote repository. See linkgit:git-push[1].
1746 remote.<name>.proxy::
1747 For remotes that require curl (http, https and ftp), the URL to
1748 the proxy to use for that remote. Set to the empty string to
1749 disable proxying for that remote.
1751 remote.<name>.fetch::
1752 The default set of "refspec" for linkgit:git-fetch[1]. See
1753 linkgit:git-fetch[1].
1755 remote.<name>.push::
1756 The default set of "refspec" for linkgit:git-push[1]. See
1757 linkgit:git-push[1].
1759 remote.<name>.mirror::
1760 If true, pushing to this remote will automatically behave
1761 as if the `\--mirror` option was given on the command line.
1763 remote.<name>.skipDefaultUpdate::
1764 If true, this remote will be skipped by default when updating
1765 using linkgit:git-fetch[1] or the `update` subcommand of
1766 linkgit:git-remote[1].
1768 remote.<name>.skipFetchAll::
1769 If true, this remote will be skipped by default when updating
1770 using linkgit:git-fetch[1] or the `update` subcommand of
1771 linkgit:git-remote[1].
1773 remote.<name>.receivepack::
1774 The default program to execute on the remote side when pushing. See
1775 option \--receive-pack of linkgit:git-push[1].
1777 remote.<name>.uploadpack::
1778 The default program to execute on the remote side when fetching. See
1779 option \--upload-pack of linkgit:git-fetch-pack[1].
1781 remote.<name>.tagopt::
1782 Setting this value to \--no-tags disables automatic tag following when
1783 fetching from remote <name>. Setting it to \--tags will fetch every
1784 tag from remote <name>, even if they are not reachable from remote
1785 branch heads. Passing these flags directly to linkgit:git-fetch[1] can
1786 override this setting. See options \--tags and \--no-tags of
1787 linkgit:git-fetch[1].
1790 Setting this to a value <vcs> will cause git to interact with
1791 the remote with the git-remote-<vcs> helper.
1794 The list of remotes which are fetched by "git remote update
1795 <group>". See linkgit:git-remote[1].
1797 repack.usedeltabaseoffset::
1798 By default, linkgit:git-repack[1] creates packs that use
1799 delta-base offset. If you need to share your repository with
1800 git older than version 1.4.4, either directly or via a dumb
1801 protocol such as http, then you need to set this option to
1802 "false" and repack. Access from old git versions over the
1803 native protocol are unaffected by this option.
1806 When set to true, `git-rerere` updates the index with the
1807 resulting contents after it cleanly resolves conflicts using
1808 previously recorded resolution. Defaults to false.
1811 Activate recording of resolved conflicts, so that identical
1812 conflict hunks can be resolved automatically, should they be
1813 encountered again. By default, linkgit:git-rerere[1] is
1814 enabled if there is an `rr-cache` directory under the
1815 `$GIT_DIR`, e.g. if "rerere" was previously used in the
1818 sendemail.identity::
1819 A configuration identity. When given, causes values in the
1820 'sendemail.<identity>' subsection to take precedence over
1821 values in the 'sendemail' section. The default identity is
1822 the value of 'sendemail.identity'.
1824 sendemail.smtpencryption::
1825 See linkgit:git-send-email[1] for description. Note that this
1826 setting is not subject to the 'identity' mechanism.
1829 Deprecated alias for 'sendemail.smtpencryption = ssl'.
1831 sendemail.<identity>.*::
1832 Identity-specific versions of the 'sendemail.*' parameters
1833 found below, taking precedence over those when the this
1834 identity is selected, through command-line or
1835 'sendemail.identity'.
1837 sendemail.aliasesfile::
1838 sendemail.aliasfiletype::
1842 sendemail.chainreplyto::
1844 sendemail.envelopesender::
1846 sendemail.multiedit::
1847 sendemail.signedoffbycc::
1848 sendemail.smtppass::
1849 sendemail.suppresscc::
1850 sendemail.suppressfrom::
1852 sendemail.smtpdomain::
1853 sendemail.smtpserver::
1854 sendemail.smtpserverport::
1855 sendemail.smtpserveroption::
1856 sendemail.smtpuser::
1858 sendemail.validate::
1859 See linkgit:git-send-email[1] for description.
1861 sendemail.signedoffcc::
1862 Deprecated alias for 'sendemail.signedoffbycc'.
1864 showbranch.default::
1865 The default set of branches for linkgit:git-show-branch[1].
1866 See linkgit:git-show-branch[1].
1868 status.relativePaths::
1869 By default, linkgit:git-status[1] shows paths relative to the
1870 current directory. Setting this variable to `false` shows paths
1871 relative to the repository root (this was the default for git
1874 status.showUntrackedFiles::
1875 By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1876 files which are not currently tracked by Git. Directories which
1877 contain only untracked files, are shown with the directory name
1878 only. Showing untracked files means that Git needs to lstat() all
1879 all the files in the whole repository, which might be slow on some
1880 systems. So, this variable controls how the commands displays
1881 the untracked files. Possible values are:
1884 * `no` - Show no untracked files.
1885 * `normal` - Show untracked files and directories.
1886 * `all` - Show also individual files in untracked directories.
1889 If this variable is not specified, it defaults to 'normal'.
1890 This variable can be overridden with the -u|--untracked-files option
1891 of linkgit:git-status[1] and linkgit:git-commit[1].
1893 status.submodulesummary::
1895 If this is set to a non zero number or true (identical to -1 or an
1896 unlimited number), the submodule summary will be enabled and a
1897 summary of commits for modified submodules will be shown (see
1898 --summary-limit option of linkgit:git-submodule[1]).
1900 submodule.<name>.path::
1901 submodule.<name>.url::
1902 submodule.<name>.update::
1903 The path within this project, URL, and the updating strategy
1904 for a submodule. These variables are initially populated
1905 by 'git submodule init'; edit them to override the
1906 URL and other values found in the `.gitmodules` file. See
1907 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
1909 submodule.<name>.fetchRecurseSubmodules::
1910 This option can be used to control recursive fetching of this
1911 submodule. It can be overridden by using the --[no-]recurse-submodules
1912 command line option to "git fetch" and "git pull".
1913 This setting will override that from in the linkgit:gitmodules[5]
1916 submodule.<name>.ignore::
1917 Defines under what circumstances "git status" and the diff family show
1918 a submodule as modified. When set to "all", it will never be considered
1919 modified, "dirty" will ignore all changes to the submodules work tree and
1920 takes only differences between the HEAD of the submodule and the commit
1921 recorded in the superproject into account. "untracked" will additionally
1922 let submodules with modified tracked files in their work tree show up.
1923 Using "none" (the default when this option is not set) also shows
1924 submodules that have untracked files in their work tree as changed.
1925 This setting overrides any setting made in .gitmodules for this submodule,
1926 both settings can be overridden on the command line by using the
1927 "--ignore-submodules" option.
1930 This variable can be used to restrict the permission bits of
1931 tar archive entries. The default is 0002, which turns off the
1932 world write bit. The special value "user" indicates that the
1933 archiving user's umask will be used instead. See umask(2) and
1934 linkgit:git-archive[1].
1936 transfer.fsckObjects::
1937 When `fetch.fsckObjects` or `receive.fsckObjects` are
1938 not set, the value of this variable is used instead.
1941 transfer.unpackLimit::
1942 When `fetch.unpackLimit` or `receive.unpackLimit` are
1943 not set, the value of this variable is used instead.
1944 The default value is 100.
1946 url.<base>.insteadOf::
1947 Any URL that starts with this value will be rewritten to
1948 start, instead, with <base>. In cases where some site serves a
1949 large number of repositories, and serves them with multiple
1950 access methods, and some users need to use different access
1951 methods, this feature allows people to specify any of the
1952 equivalent URLs and have git automatically rewrite the URL to
1953 the best alternative for the particular user, even for a
1954 never-before-seen repository on the site. When more than one
1955 insteadOf strings match a given URL, the longest match is used.
1957 url.<base>.pushInsteadOf::
1958 Any URL that starts with this value will not be pushed to;
1959 instead, it will be rewritten to start with <base>, and the
1960 resulting URL will be pushed to. In cases where some site serves
1961 a large number of repositories, and serves them with multiple
1962 access methods, some of which do not allow push, this feature
1963 allows people to specify a pull-only URL and have git
1964 automatically use an appropriate URL to push, even for a
1965 never-before-seen repository on the site. When more than one
1966 pushInsteadOf strings match a given URL, the longest match is
1967 used. If a remote has an explicit pushurl, git will ignore this
1968 setting for that remote.
1971 Your email address to be recorded in any newly created commits.
1972 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1973 'EMAIL' environment variables. See linkgit:git-commit-tree[1].
1976 Your full name to be recorded in any newly created commits.
1977 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1978 environment variables. See linkgit:git-commit-tree[1].
1981 If linkgit:git-tag[1] is not selecting the key you want it to
1982 automatically when creating a signed tag, you can override the
1983 default selection with this variable. This option is passed
1984 unchanged to gpg's --local-user parameter, so you may specify a key
1985 using any method that gpg supports.
1988 Specify a web browser that may be used by some commands.
1989 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]