1 CONFIGURATION FILE
2 ------------------
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.
18 Syntax
19 ~~~~~~
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:
36 --------
37 [section "subsection"]
39 --------
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
46 don't need to.
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 0/1, 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.
87 Example
88 ~~~~~~~
90 # Core variables
91 [core]
92 ; Don't trust file modes
93 filemode = false
95 # Our diff algorithm
96 [diff]
97 external = /usr/local/bin/diff-wrapper
98 renames = true
100 [branch "devel"]
101 remote = origin
102 merge = refs/heads/devel
104 # Proxy settings
105 [core]
106 gitProxy="ssh" for "kernel.org"
107 gitProxy=default-proxy ; for the rest
109 Variables
110 ~~~~~~~~~
112 Note that this list is non-comprehensive and not necessarily complete.
113 For command-specific variables, you will find a more detailed description
114 in the appropriate manual page. You will find a description of non-core
115 porcelain configuration variables in the respective porcelain documentation.
117 advice.*::
118 When set to 'true', display the given optional help message.
119 When set to 'false', do not display. The configuration variables
120 are:
121 +
122 --
123 pushNonFastForward::
124 Advice shown when linkgit:git-push[1] refuses
125 non-fast-forward refs. Default: true.
126 statusHints::
127 Directions on how to stage/unstage/add shown in the
128 output of linkgit:git-status[1] and the template shown
129 when writing commit messages. Default: true.
130 commitBeforeMerge::
131 Advice shown when linkgit:git-merge[1] refuses to
132 merge to avoid overwriting local changes.
133 Default: true.
134 resolveConflict::
135 Advices shown by various commands when conflicts
136 prevent the operation from being performed.
137 Default: true.
138 implicitIdentity::
139 Advice on how to set your identity configuration when
140 your information is guessed from the system username and
141 domain name. Default: true.
143 detachedHead::
144 Advice shown when you used linkgit::git-checkout[1] to
145 move to the detach HEAD state, to instruct how to create
146 a local branch after the fact. Default: true.
147 --
149 core.fileMode::
150 If false, the executable bit differences between the index and
151 the working copy are ignored; useful on broken filesystems like FAT.
152 See linkgit:git-update-index[1].
153 +
154 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
155 will probe and set core.fileMode false if appropriate when the
156 repository is created.
158 core.ignoreCygwinFSTricks::
159 This option is only used by Cygwin implementation of Git. If false,
160 the Cygwin stat() and lstat() functions are used. This may be useful
161 if your repository consists of a few separate directories joined in
162 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
163 whenever it is possible and falls back to Cygwin functions only to
164 handle symbol links. The native mode is more than twice faster than
165 normal Cygwin l/stat() functions. True by default, unless core.filemode
166 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
167 POSIX emulation is required to support core.filemode.
169 core.ignorecase::
170 If true, this option enables various workarounds to enable
171 git to work better on filesystems that are not case sensitive,
172 like FAT. For example, if a directory listing finds
173 "makefile" when git expects "Makefile", git will assume
174 it is really the same file, and continue to remember it as
175 "Makefile".
176 +
177 The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
178 will probe and set core.ignorecase true if appropriate when the repository
179 is created.
181 core.trustctime::
182 If false, the ctime differences between the index and the
183 working copy are ignored; useful when the inode change time
184 is regularly modified by something outside Git (file system
185 crawlers and some backup systems).
186 See linkgit:git-update-index[1]. True by default.
188 core.quotepath::
189 The commands that output paths (e.g. 'ls-files',
190 'diff'), when not given the `-z` option, will quote
191 "unusual" characters in the pathname by enclosing the
192 pathname in a double-quote pair and with backslashes the
193 same way strings in C source code are quoted. If this
194 variable is set to false, the bytes higher than 0x80 are
195 not quoted but output as verbatim. Note that double
196 quote, backslash and control characters are always
197 quoted without `-z` regardless of the setting of this
198 variable.
200 core.eol::
201 Sets the line ending type to use in the working directory for
202 files that have the `text` property set. Alternatives are
203 'lf', 'crlf' and 'native', which uses the platform's native
204 line ending. The default value is `native`. See
205 linkgit:gitattributes[5] for more information on end-of-line
206 conversion.
208 core.safecrlf::
209 If true, makes git check if converting `CRLF` is reversible when
210 end-of-line conversion is active. Git will verify if a command
211 modifies a file in the work tree either directly or indirectly.
212 For example, committing a file followed by checking out the
213 same file should yield the original file in the work tree. If
214 this is not the case for the current setting of
215 `core.autocrlf`, git will reject the file. The variable can
216 be set to "warn", in which case git will only warn about an
217 irreversible conversion but continue the operation.
218 +
219 CRLF conversion bears a slight chance of corrupting data.
220 When it is enabled, git will convert CRLF to LF during commit and LF to
221 CRLF during checkout. A file that contains a mixture of LF and
222 CRLF before the commit cannot be recreated by git. For text
223 files this is the right thing to do: it corrects line endings
224 such that we have only LF line endings in the repository.
225 But for binary files that are accidentally classified as text the
226 conversion can corrupt data.
227 +
228 If you recognize such corruption early you can easily fix it by
229 setting the conversion type explicitly in .gitattributes. Right
230 after committing you still have the original file in your work
231 tree and this file is not yet corrupted. You can explicitly tell
232 git that this file is binary and git will handle the file
233 appropriately.
234 +
235 Unfortunately, the desired effect of cleaning up text files with
236 mixed line endings and the undesired effect of corrupting binary
237 files cannot be distinguished. In both cases CRLFs are removed
238 in an irreversible way. For text files this is the right thing
239 to do because CRLFs are line endings, while for binary files
240 converting CRLFs corrupts data.
241 +
242 Note, this safety check does not mean that a checkout will generate a
243 file identical to the original file for a different setting of
244 `core.eol` and `core.autocrlf`, but only for the current one. For
245 example, a text file with `LF` would be accepted with `core.eol=lf`
246 and could later be checked out with `core.eol=crlf`, in which case the
247 resulting file would contain `CRLF`, although the original file
248 contained `LF`. However, in both work trees the line endings would be
249 consistent, that is either all `LF` or all `CRLF`, but never mixed. A
250 file with mixed line endings would be reported by the `core.safecrlf`
251 mechanism.
253 core.autocrlf::
254 Setting this variable to "true" is almost the same as setting
255 the `text` attribute to "auto" on all files except that text
256 files are not guaranteed to be normalized: files that contain
257 `CRLF` in the repository will not be touched. Use this
258 setting if you want to have `CRLF` line endings in your
259 working directory even though the repository does not have
260 normalized line endings. This variable can be set to 'input',
261 in which case no output conversion is performed.
263 core.symlinks::
264 If false, symbolic links are checked out as small plain files that
265 contain the link text. linkgit:git-update-index[1] and
266 linkgit:git-add[1] will not change the recorded type to regular
267 file. Useful on filesystems like FAT that do not support
268 symbolic links.
269 +
270 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
271 will probe and set core.symlinks false if appropriate when the repository
272 is created.
274 core.gitProxy::
275 A "proxy command" to execute (as 'command host port') instead
276 of establishing direct connection to the remote server when
277 using the git protocol for fetching. If the variable value is
278 in the "COMMAND for DOMAIN" format, the command is applied only
279 on hostnames ending with the specified domain string. This variable
280 may be set multiple times and is matched in the given order;
281 the first match wins.
282 +
283 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
284 (which always applies universally, without the special "for"
285 handling).
286 +
287 The special string `none` can be used as the proxy command to
288 specify that no proxy be used for a given domain pattern.
289 This is useful for excluding servers inside a firewall from
290 proxy use, while defaulting to a common proxy for external domains.
292 core.ignoreStat::
293 If true, commands which modify both the working tree and the index
294 will mark the updated paths with the "assume unchanged" bit in the
295 index. These marked files are then assumed to stay unchanged in the
296 working copy, until you mark them otherwise manually - Git will not
297 detect the file changes by lstat() calls. This is useful on systems
298 where those are very slow, such as Microsoft Windows.
299 See linkgit:git-update-index[1].
300 False by default.
302 core.preferSymlinkRefs::
303 Instead of the default "symref" format for HEAD
304 and other symbolic reference files, use symbolic links.
305 This is sometimes needed to work with old scripts that
306 expect HEAD to be a symbolic link.
308 core.bare::
309 If true this repository is assumed to be 'bare' and has no
310 working directory associated with it. If this is the case a
311 number of commands that require a working directory will be
312 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
313 +
314 This setting is automatically guessed by linkgit:git-clone[1] or
315 linkgit:git-init[1] when the repository was created. By default a
316 repository that ends in "/.git" is assumed to be not bare (bare =
317 false), while all other repositories are assumed to be bare (bare
318 = true).
320 core.worktree::
321 Set the path to the root of the work tree.
322 This can be overridden by the GIT_WORK_TREE environment
323 variable and the '--work-tree' command line option. It can be
324 an absolute path or a relative path to the .git directory,
325 either specified by --git-dir or GIT_DIR, or automatically
326 discovered.
327 If --git-dir or GIT_DIR are specified but none of
328 --work-tree, GIT_WORK_TREE and core.worktree is specified,
329 the current working directory is regarded as the root of the
330 work tree.
331 +
332 Note that this variable is honored even when set in a configuration
333 file in a ".git" subdirectory of a directory, and its value differs
334 from the latter directory (e.g. "/path/to/.git/config" has
335 core.worktree set to "/different/path"), which is most likely a
336 misconfiguration. Running git commands in "/path/to" directory will
337 still use "/different/path" as the root of the work tree and can cause
338 great confusion to the users.
340 core.logAllRefUpdates::
341 Enable the reflog. Updates to a ref <ref> is logged to the file
342 "$GIT_DIR/logs/<ref>", by appending the new and old
343 SHA1, the date/time and the reason of the update, but
344 only when the file exists. If this configuration
345 variable is set to true, missing "$GIT_DIR/logs/<ref>"
346 file is automatically created for branch heads.
347 +
348 This information can be used to determine what commit
349 was the tip of a branch "2 days ago".
350 +
351 This value is true by default in a repository that has
352 a working directory associated with it, and false by
353 default in a bare repository.
355 core.repositoryFormatVersion::
356 Internal variable identifying the repository format and layout
357 version.
359 core.sharedRepository::
360 When 'group' (or 'true'), the repository is made shareable between
361 several users in a group (making sure all the files and objects are
362 group-writable). When 'all' (or 'world' or 'everybody'), the
363 repository will be readable by all users, additionally to being
364 group-shareable. When 'umask' (or 'false'), git will use permissions
365 reported by umask(2). When '0xxx', where '0xxx' is an octal number,
366 files in the repository will have this mode value. '0xxx' will override
367 user's umask value (whereas the other options will only override
368 requested parts of the user's umask value). Examples: '0660' will make
369 the repo read/write-able for the owner and group, but inaccessible to
370 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
371 repository that is group-readable but not group-writable.
372 See linkgit:git-init[1]. False by default.
374 core.warnAmbiguousRefs::
375 If true, git will warn you if the ref name you passed it is ambiguous
376 and might match multiple refs in the .git/refs/ tree. True by default.
378 core.compression::
379 An integer -1..9, indicating a default compression level.
380 -1 is the zlib default. 0 means no compression,
381 and 1..9 are various speed/size tradeoffs, 9 being slowest.
382 If set, this provides a default to other compression variables,
383 such as 'core.loosecompression' and 'pack.compression'.
385 core.loosecompression::
386 An integer -1..9, indicating the compression level for objects that
387 are not in a pack file. -1 is the zlib default. 0 means no
388 compression, and 1..9 are various speed/size tradeoffs, 9 being
389 slowest. If not set, defaults to core.compression. If that is
390 not set, defaults to 1 (best speed).
392 core.packedGitWindowSize::
393 Number of bytes of a pack file to map into memory in a
394 single mapping operation. Larger window sizes may allow
395 your system to process a smaller number of large pack files
396 more quickly. Smaller window sizes will negatively affect
397 performance due to increased calls to the operating system's
398 memory manager, but may improve performance when accessing
399 a large number of large pack files.
400 +
401 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
402 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
403 be reasonable for all users/operating systems. You probably do
404 not need to adjust this value.
405 +
406 Common unit suffixes of 'k', 'm', or 'g' are supported.
408 core.packedGitLimit::
409 Maximum number of bytes to map simultaneously into memory
410 from pack files. If Git needs to access more than this many
411 bytes at once to complete an operation it will unmap existing
412 regions to reclaim virtual address space within the process.
413 +
414 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
415 This should be reasonable for all users/operating systems, except on
416 the largest projects. You probably do not need to adjust this value.
417 +
418 Common unit suffixes of 'k', 'm', or 'g' are supported.
420 core.deltaBaseCacheLimit::
421 Maximum number of bytes to reserve for caching base objects
422 that may be referenced by multiple deltified objects. By storing the
423 entire decompressed base objects in a cache Git is able
424 to avoid unpacking and decompressing frequently used base
425 objects multiple times.
426 +
427 Default is 16 MiB on all platforms. This should be reasonable
428 for all users/operating systems, except on the largest projects.
429 You probably do not need to adjust this value.
430 +
431 Common unit suffixes of 'k', 'm', or 'g' are supported.
433 core.bigFileThreshold::
434 Files larger than this size are stored deflated, without
435 attempting delta compression. Storing large files without
436 delta compression avoids excessive memory usage, at the
437 slight expense of increased disk usage.
438 +
439 Default is 512 MiB on all platforms. This should be reasonable
440 for most projects as source code and other text files can still
441 be delta compressed, but larger binary media files won't be.
442 +
443 Common unit suffixes of 'k', 'm', or 'g' are supported.
444 +
445 Currently only linkgit:git-fast-import[1] honors this setting.
447 core.excludesfile::
448 In addition to '.gitignore' (per-directory) and
449 '.git/info/exclude', git looks into this file for patterns
450 of files which are not meant to be tracked. "{tilde}/" is expanded
451 to the value of `$HOME` and "{tilde}user/" to the specified user's
452 home directory. See linkgit:gitignore[5].
454 core.askpass::
455 Some commands (e.g. svn and http interfaces) that interactively
456 ask for a password can be told to use an external program given
457 via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
458 environment variable. If not set, fall back to the value of the
459 'SSH_ASKPASS' environment variable or, failing that, a simple password
460 prompt. The external program shall be given a suitable prompt as
461 command line argument and write the password on its STDOUT.
463 core.editor::
464 Commands such as `commit` and `tag` that lets you edit
465 messages by launching an editor uses the value of this
466 variable when it is set, and the environment variable
467 `GIT_EDITOR` is not set. See linkgit:git-var[1].
469 core.pager::
470 The command that git will use to paginate output. Can
471 be overridden with the `GIT_PAGER` environment
472 variable. Note that git sets the `LESS` environment
473 variable to `FRSX` if it is unset when it runs the
474 pager. One can change these settings by setting the
475 `LESS` variable to some other value. Alternately,
476 these settings can be overridden on a project or
477 global basis by setting the `core.pager` option.
478 Setting `core.pager` has no affect on the `LESS`
479 environment variable behaviour above, so if you want
480 to override git's default settings this way, you need
481 to be explicit. For example, to disable the S option
482 in a backward compatible manner, set `core.pager`
483 to `less -+$LESS -FRX`. This will be passed to the
484 shell by git, which will translate the final command to
485 `LESS=FRSX less -+FRSX -FRX`.
487 core.whitespace::
488 A comma separated list of common whitespace problems to
489 notice. 'git diff' will use `color.diff.whitespace` to
490 highlight them, and 'git apply --whitespace=error' will
491 consider them as errors. You can prefix `-` to disable
492 any of them (e.g. `-trailing-space`):
493 +
494 * `blank-at-eol` treats trailing whitespaces at the end of the line
495 as an error (enabled by default).
496 * `space-before-tab` treats a space character that appears immediately
497 before a tab character in the initial indent part of the line as an
498 error (enabled by default).
499 * `indent-with-non-tab` treats a line that is indented with 8 or more
500 space characters as an error (not enabled by default).
501 * `tab-in-indent` treats a tab character in the initial indent part of
502 the line as an error (not enabled by default).
503 * `blank-at-eof` treats blank lines added at the end of file as an error
504 (enabled by default).
505 * `trailing-space` is a short-hand to cover both `blank-at-eol` and
506 `blank-at-eof`.
507 * `cr-at-eol` treats a carriage-return at the end of line as
508 part of the line terminator, i.e. with it, `trailing-space`
509 does not trigger if the character before such a carriage-return
510 is not a whitespace (not enabled by default).
512 core.fsyncobjectfiles::
513 This boolean will enable 'fsync()' when writing object files.
514 +
515 This is a total waste of time and effort on a filesystem that orders
516 data writes properly, but can be useful for filesystems that do not use
517 journalling (traditional UNIX filesystems) or that only journal metadata
518 and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
520 core.preloadindex::
521 Enable parallel index preload for operations like 'git diff'
522 +
523 This can speed up operations like 'git diff' and 'git status' especially
524 on filesystems like NFS that have weak caching semantics and thus
525 relatively high IO latencies. With this set to 'true', git will do the
526 index comparison to the filesystem data in parallel, allowing
527 overlapping IO's.
529 core.createObject::
530 You can set this to 'link', in which case a hardlink followed by
531 a delete of the source are used to make sure that object creation
532 will not overwrite existing objects.
533 +
534 On some file system/operating system combinations, this is unreliable.
535 Set this config setting to 'rename' there; However, This will remove the
536 check that makes sure that existing object files will not get overwritten.
538 core.notesRef::
539 When showing commit messages, also show notes which are stored in
540 the given ref. The ref must be fully qualified. If the given
541 ref does not exist, it is not an error but means that no
542 notes should be printed.
543 +
544 This setting defaults to "refs/notes/commits", and it can be overridden by
545 the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1].
547 core.sparseCheckout::
548 Enable "sparse checkout" feature. See section "Sparse checkout" in
549 linkgit:git-read-tree[1] for more information.
551 add.ignore-errors::
552 Tells 'git add' to continue adding files when some files cannot be
553 added due to indexing errors. Equivalent to the '--ignore-errors'
554 option of linkgit:git-add[1].
556 alias.*::
557 Command aliases for the linkgit:git[1] command wrapper - e.g.
558 after defining "alias.last = cat-file commit HEAD", the invocation
559 "git last" is equivalent to "git cat-file commit HEAD". To avoid
560 confusion and troubles with script usage, aliases that
561 hide existing git commands are ignored. Arguments are split by
562 spaces, the usual shell quoting and escaping is supported.
563 quote pair and a backslash can be used to quote them.
564 +
565 If the alias expansion is prefixed with an exclamation point,
566 it will be treated as a shell command. For example, defining
567 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
568 "git new" is equivalent to running the shell command
569 "gitk --all --not ORIG_HEAD". Note that shell commands will be
570 executed from the top-level directory of a repository, which may
571 not necessarily be the current directory.
573 am.keepcr::
574 If true, git-am will call git-mailsplit for patches in mbox format
575 with parameter '--keep-cr'. In this case git-mailsplit will
576 not remove `\r` from lines ending with `\r\n`. Can be overridden
577 by giving '--no-keep-cr' from the command line.
578 See linkgit:git-am[1], linkgit:git-mailsplit[1].
580 apply.ignorewhitespace::
581 When set to 'change', tells 'git apply' to ignore changes in
582 whitespace, in the same way as the '--ignore-space-change'
583 option.
584 When set to one of: no, none, never, false tells 'git apply' to
585 respect all whitespace differences.
586 See linkgit:git-apply[1].
588 apply.whitespace::
589 Tells 'git apply' how to handle whitespaces, in the same way
590 as the '--whitespace' option. See linkgit:git-apply[1].
592 branch.autosetupmerge::
593 Tells 'git branch' and 'git checkout' to set up new branches
594 so that linkgit:git-pull[1] will appropriately merge from the
595 starting point branch. Note that even if this option is not set,
596 this behavior can be chosen per-branch using the `--track`
597 and `--no-track` options. The valid settings are: `false` -- no
598 automatic setup is done; `true` -- automatic setup is done when the
599 starting point is a remote branch; `always` -- automatic setup is
600 done when the starting point is either a local branch or remote
601 branch. This option defaults to true.
603 branch.autosetuprebase::
604 When a new branch is created with 'git branch' or 'git checkout'
605 that tracks another branch, this variable tells git to set
606 up pull to rebase instead of merge (see "branch.<name>.rebase").
607 When `never`, rebase is never automatically set to true.
608 When `local`, rebase is set to true for tracked branches of
609 other local branches.
610 When `remote`, rebase is set to true for tracked branches of
611 remote branches.
612 When `always`, rebase will be set to true for all tracking
613 branches.
614 See "branch.autosetupmerge" for details on how to set up a
615 branch to track another branch.
616 This option defaults to never.
618 branch.<name>.remote::
619 When in branch <name>, it tells 'git fetch' and 'git push' which
620 remote to fetch from/push to. It defaults to `origin` if no remote is
621 configured. `origin` is also used if you are not on any branch.
623 branch.<name>.merge::
624 Defines, together with branch.<name>.remote, the upstream branch
625 for the given branch. It tells 'git fetch'/'git pull' which
626 branch to merge and can also affect 'git push' (see push.default).
627 When in branch <name>, it tells 'git fetch' the default
628 refspec to be marked for merging in FETCH_HEAD. The value is
629 handled like the remote part of a refspec, and must match a
630 ref which is fetched from the remote given by
631 "branch.<name>.remote".
632 The merge information is used by 'git pull' (which at first calls
633 'git fetch') to lookup the default branch for merging. Without
634 this option, 'git pull' defaults to merge the first refspec fetched.
635 Specify multiple values to get an octopus merge.
636 If you wish to setup 'git pull' so that it merges into <name> from
637 another branch in the local repository, you can point
638 branch.<name>.merge to the desired branch, and use the special setting
639 `.` (a period) for branch.<name>.remote.
641 branch.<name>.mergeoptions::
642 Sets default options for merging into branch <name>. The syntax and
643 supported options are the same as those of linkgit:git-merge[1], but
644 option values containing whitespace characters are currently not
645 supported.
647 branch.<name>.rebase::
648 When true, rebase the branch <name> on top of the fetched branch,
649 instead of merging the default branch from the default remote when
650 "git pull" is run.
651 *NOTE*: this is a possibly dangerous operation; do *not* use
652 it unless you understand the implications (see linkgit:git-rebase[1]
653 for details).
655 browser.<tool>.cmd::
656 Specify the command to invoke the specified browser. The
657 specified command is evaluated in shell with the URLs passed
658 as arguments. (See linkgit:git-web--browse[1].)
660 browser.<tool>.path::
661 Override the path for the given tool that may be used to
662 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
663 working repository in gitweb (see linkgit:git-instaweb[1]).
665 clean.requireForce::
666 A boolean to make git-clean do nothing unless given -f
667 or -n. Defaults to true.
669 color.branch::
670 A boolean to enable/disable color in the output of
671 linkgit:git-branch[1]. May be set to `always`,
672 `false` (or `never`) or `auto` (or `true`), in which case colors are used
673 only when the output is to a terminal. Defaults to false.
675 color.branch.<slot>::
676 Use customized color for branch coloration. `<slot>` is one of
677 `current` (the current branch), `local` (a local branch),
678 `remote` (a tracking branch in refs/remotes/), `plain` (other
679 refs).
680 +
681 The value for these configuration variables is a list of colors (at most
682 two) and attributes (at most one), separated by spaces. The colors
683 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
684 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
685 `blink` and `reverse`. The first color given is the foreground; the
686 second is the background. The position of the attribute, if any,
687 doesn't matter.
689 color.diff::
690 When set to `always`, always use colors in patch.
691 When false (or `never`), never. When set to `true` or `auto`, use
692 colors only when the output is to the terminal. Defaults to false.
694 color.diff.<slot>::
695 Use customized color for diff colorization. `<slot>` specifies
696 which part of the patch to use the specified color, and is one
697 of `plain` (context text), `meta` (metainformation), `frag`
698 (hunk header), 'func' (function in hunk header), `old` (removed lines),
699 `new` (added lines), `commit` (commit headers), or `whitespace`
700 (highlighting whitespace errors). The values of these variables may be
701 specified as in color.branch.<slot>.
703 color.decorate.<slot>::
704 Use customized color for 'git log --decorate' output. `<slot>` is one
705 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
706 branches, remote tracking branches, tags, stash and HEAD, respectively.
708 color.grep::
709 When set to `always`, always highlight matches. When `false` (or
710 `never`), never. When set to `true` or `auto`, use color only
711 when the output is written to the terminal. Defaults to `false`.
713 color.grep.<slot>::
714 Use customized color for grep colorization. `<slot>` specifies which
715 part of the line to use the specified color, and is one of
716 +
717 --
718 `context`;;
719 non-matching text in context lines (when using `-A`, `-B`, or `-C`)
720 `filename`;;
721 filename prefix (when not using `-h`)
722 `function`;;
723 function name lines (when using `-p`)
724 `linenumber`;;
725 line number prefix (when using `-n`)
726 `match`;;
727 matching text
728 `selected`;;
729 non-matching text in selected lines
730 `separator`;;
731 separators between fields on a line (`:`, `-`, and `=`)
732 and between hunks (`--`)
733 --
734 +
735 The values of these variables may be specified as in color.branch.<slot>.
737 color.interactive::
738 When set to `always`, always use colors for interactive prompts
739 and displays (such as those used by "git-add --interactive").
740 When false (or `never`), never. When set to `true` or `auto`, use
741 colors only when the output is to the terminal. Defaults to false.
743 color.interactive.<slot>::
744 Use customized color for 'git add --interactive'
745 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
746 four distinct types of normal output from interactive
747 commands. The values of these variables may be specified as
748 in color.branch.<slot>.
750 color.pager::
751 A boolean to enable/disable colored output when the pager is in
752 use (default is true).
754 color.showbranch::
755 A boolean to enable/disable color in the output of
756 linkgit:git-show-branch[1]. May be set to `always`,
757 `false` (or `never`) or `auto` (or `true`), in which case colors are used
758 only when the output is to a terminal. Defaults to false.
760 color.status::
761 A boolean to enable/disable color in the output of
762 linkgit:git-status[1]. May be set to `always`,
763 `false` (or `never`) or `auto` (or `true`), in which case colors are used
764 only when the output is to a terminal. Defaults to false.
766 color.status.<slot>::
767 Use customized color for status colorization. `<slot>` is
768 one of `header` (the header text of the status message),
769 `added` or `updated` (files which are added but not committed),
770 `changed` (files which are changed but not added in the index),
771 `untracked` (files which are not tracked by git), or
772 `nobranch` (the color the 'no branch' warning is shown in, defaulting
773 to red). The values of these variables may be specified as in
774 color.branch.<slot>.
776 color.ui::
777 When set to `always`, always use colors in all git commands which
778 are capable of colored output. When false (or `never`), never. When
779 set to `true` or `auto`, use colors only when the output is to the
780 terminal. When more specific variables of color.* are set, they always
781 take precedence over this setting. Defaults to false.
783 commit.status::
784 A boolean to enable/disable inclusion of status information in the
785 commit message template when using an editor to prepare the commit
786 message. Defaults to true.
788 commit.template::
789 Specify a file to use as the template for new commit messages.
790 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the
791 specified user's home directory.
793 diff.autorefreshindex::
794 When using 'git diff' to compare with work tree
795 files, do not consider stat-only change as changed.
796 Instead, silently run `git update-index --refresh` to
797 update the cached stat information for paths whose
798 contents in the work tree match the contents in the
799 index. This option defaults to true. Note that this
800 affects only 'git diff' Porcelain, and not lower level
801 'diff' commands such as 'git diff-files'.
803 diff.external::
804 If this config variable is set, diff generation is not
805 performed using the internal diff machinery, but using the
806 given command. Can be overridden with the `GIT_EXTERNAL_DIFF'
807 environment variable. The command is called with parameters
808 as described under "git Diffs" in linkgit:git[1]. Note: if
809 you want to use an external diff program only on a subset of
810 your files, you might want to use linkgit:gitattributes[5] instead.
812 diff.mnemonicprefix::
813 If set, 'git diff' uses a prefix pair that is different from the
814 standard "a/" and "b/" depending on what is being compared. When
815 this configuration is in effect, reverse diff output also swaps
816 the order of the prefixes:
817 `git diff`;;
818 compares the (i)ndex and the (w)ork tree;
819 `git diff HEAD`;;
820 compares a (c)ommit and the (w)ork tree;
821 `git diff --cached`;;
822 compares a (c)ommit and the (i)ndex;
823 `git diff HEAD:file1 file2`;;
824 compares an (o)bject and a (w)ork tree entity;
825 `git diff --no-index a b`;;
826 compares two non-git things (1) and (2).
828 diff.noprefix::
829 If set, 'git diff' does not show any source or destination prefix.
831 diff.renameLimit::
832 The number of files to consider when performing the copy/rename
833 detection; equivalent to the 'git diff' option '-l'.
835 diff.renames::
836 Tells git to detect renames. If set to any boolean value, it
837 will enable basic rename detection. If set to "copies" or
838 "copy", it will detect copies, as well.
840 diff.ignoreSubmodules::
841 Sets the default value of --ignore-submodules. Note that this
842 affects only 'git diff' Porcelain, and not lower level 'diff'
843 commands such as 'git diff-files'. 'git checkout' also honors
844 this setting when reporting uncommitted changes.
846 diff.suppressBlankEmpty::
847 A boolean to inhibit the standard behavior of printing a space
848 before each empty output line. Defaults to false.
850 diff.tool::
851 Controls which diff tool is used. `diff.tool` overrides
852 `merge.tool` when used by linkgit:git-difftool[1] and has
853 the same valid values as `merge.tool` minus "tortoisemerge"
854 and plus "kompare".
856 difftool.<tool>.path::
857 Override the path for the given tool. This is useful in case
858 your tool is not in the PATH.
860 difftool.<tool>.cmd::
861 Specify the command to invoke the specified diff tool.
862 The specified command is evaluated in shell with the following
863 variables available: 'LOCAL' is set to the name of the temporary
864 file containing the contents of the diff pre-image and 'REMOTE'
865 is set to the name of the temporary file containing the contents
866 of the diff post-image.
868 difftool.prompt::
869 Prompt before each invocation of the diff tool.
871 diff.wordRegex::
872 A POSIX Extended Regular Expression used to determine what is a "word"
873 when performing word-by-word difference calculations. Character
874 sequences that match the regular expression are "words", all other
875 characters are *ignorable* whitespace.
877 fetch.unpackLimit::
878 If the number of objects fetched over the git native
879 transfer is below this
880 limit, then the objects will be unpacked into loose object
881 files. However if the number of received objects equals or
882 exceeds this limit then the received pack will be stored as
883 a pack, after adding any missing delta bases. Storing the
884 pack from a push can make the push operation complete faster,
885 especially on slow filesystems. If not set, the value of
886 `transfer.unpackLimit` is used instead.
888 format.attach::
889 Enable multipart/mixed attachments as the default for
890 'format-patch'. The value can also be a double quoted string
891 which will enable attachments as the default and set the
892 value as the boundary. See the --attach option in
893 linkgit:git-format-patch[1].
895 format.numbered::
896 A boolean which can enable or disable sequence numbers in patch
897 subjects. It defaults to "auto" which enables it only if there
898 is more than one patch. It can be enabled or disabled for all
899 messages by setting it to "true" or "false". See --numbered
900 option in linkgit:git-format-patch[1].
902 format.headers::
903 Additional email headers to include in a patch to be submitted
904 by mail. See linkgit:git-format-patch[1].
906 format.to::
907 format.cc::
908 Additional recipients to include in a patch to be submitted
909 by mail. See the --to and --cc options in
910 linkgit:git-format-patch[1].
912 format.subjectprefix::
913 The default for format-patch is to output files with the '[PATCH]'
914 subject prefix. Use this variable to change that prefix.
916 format.signature::
917 The default for format-patch is to output a signature containing
918 the git version number. Use this variable to change that default.
919 Set this variable to the empty string ("") to suppress
920 signature generation.
922 format.suffix::
923 The default for format-patch is to output files with the suffix
924 `.patch`. Use this variable to change that suffix (make sure to
925 include the dot if you want it).
927 format.pretty::
928 The default pretty format for log/show/whatchanged command,
929 See linkgit:git-log[1], linkgit:git-show[1],
930 linkgit:git-whatchanged[1].
932 format.thread::
933 The default threading style for 'git format-patch'. Can be
934 a boolean value, or `shallow` or `deep`. `shallow` threading
935 makes every mail a reply to the head of the series,
936 where the head is chosen from the cover letter, the
937 `\--in-reply-to`, and the first patch mail, in this order.
938 `deep` threading makes every mail a reply to the previous one.
939 A true boolean value is the same as `shallow`, and a false
940 value disables threading.
942 format.signoff::
943 A boolean value which lets you enable the `-s/--signoff` option of
944 format-patch by default. *Note:* Adding the Signed-off-by: line to a
945 patch should be a conscious act and means that you certify you have
946 the rights to submit this work under the same open source license.
947 Please see the 'SubmittingPatches' document for further discussion.
949 gc.aggressiveWindow::
950 The window size parameter used in the delta compression
951 algorithm used by 'git gc --aggressive'. This defaults
952 to 250.
954 gc.auto::
955 When there are approximately more than this many loose
956 objects in the repository, `git gc --auto` will pack them.
957 Some Porcelain commands use this command to perform a
958 light-weight garbage collection from time to time. The
959 default value is 6700. Setting this to 0 disables it.
961 gc.autopacklimit::
962 When there are more than this many packs that are not
963 marked with `*.keep` file in the repository, `git gc
964 --auto` consolidates them into one larger pack. The
965 default value is 50. Setting this to 0 disables it.
967 gc.packrefs::
968 Running `git pack-refs` in a repository renders it
969 unclonable by Git versions prior to 1.5.1.2 over dumb
970 transports such as HTTP. This variable determines whether
971 'git gc' runs `git pack-refs`. This can be set to `nobare`
972 to enable it within all non-bare repos or it can be set to a
973 boolean value. The default is `true`.
975 gc.pruneexpire::
976 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
977 Override the grace period with this config variable. The value
978 "now" may be used to disable this grace period and always prune
979 unreachable objects immediately.
981 gc.reflogexpire::
982 gc.<pattern>.reflogexpire::
983 'git reflog expire' removes reflog entries older than
984 this time; defaults to 90 days. With "<pattern>" (e.g.
985 "refs/stash") in the middle the setting applies only to
986 the refs that match the <pattern>.
988 gc.reflogexpireunreachable::
989 gc.<ref>.reflogexpireunreachable::
990 'git reflog expire' removes reflog entries older than
991 this time and are not reachable from the current tip;
992 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")
993 in the middle, the setting applies only to the refs that
994 match the <pattern>.
996 gc.rerereresolved::
997 Records of conflicted merge you resolved earlier are
998 kept for this many days when 'git rerere gc' is run.
999 The default is 60 days. See linkgit:git-rerere[1].
1001 gc.rerereunresolved::
1002 Records of conflicted merge you have not resolved are
1003 kept for this many days when 'git rerere gc' is run.
1004 The default is 15 days. See linkgit:git-rerere[1].
1006 gitcvs.commitmsgannotation::
1007 Append this string to each commit message. Set to empty string
1008 to disable this feature. Defaults to "via git-CVS emulator".
1010 gitcvs.enabled::
1011 Whether the CVS server interface is enabled for this repository.
1012 See linkgit:git-cvsserver[1].
1014 gitcvs.logfile::
1015 Path to a log file where the CVS server interface well... logs
1016 various stuff. See linkgit:git-cvsserver[1].
1018 gitcvs.usecrlfattr::
1019 If true, the server will look up the end-of-line conversion
1020 attributes for files to determine the '-k' modes to use. If
1021 the attributes force git to treat a file as text,
1022 the '-k' mode will be left blank so CVS clients will
1023 treat it as text. If they suppress text conversion, the file
1024 will be set with '-kb' mode, which suppresses any newline munging
1025 the client might otherwise do. If the attributes do not allow
1026 the file type to be determined, then 'gitcvs.allbinary' is
1027 used. See linkgit:gitattributes[5].
1029 gitcvs.allbinary::
1030 This is used if 'gitcvs.usecrlfattr' does not resolve
1031 the correct '-kb' mode to use. If true, all
1032 unresolved files are sent to the client in
1033 mode '-kb'. This causes the client to treat them
1034 as binary files, which suppresses any newline munging it
1035 otherwise might do. Alternatively, if it is set to "guess",
1036 then the contents of the file are examined to decide if
1037 it is binary, similar to 'core.autocrlf'.
1039 gitcvs.dbname::
1040 Database used by git-cvsserver to cache revision information
1041 derived from the git repository. The exact meaning depends on the
1042 used database driver, for SQLite (which is the default driver) this
1043 is a filename. Supports variable substitution (see
1044 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1045 Default: '%Ggitcvs.%m.sqlite'
1047 gitcvs.dbdriver::
1048 Used Perl DBI driver. You can specify any available driver
1049 for this here, but it might not work. git-cvsserver is tested
1050 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1051 reported *not* to work with 'DBD::mysql'. Experimental feature.
1052 May not contain double colons (`:`). Default: 'SQLite'.
1053 See linkgit:git-cvsserver[1].
1055 gitcvs.dbuser, gitcvs.dbpass::
1056 Database user and password. Only useful if setting 'gitcvs.dbdriver',
1057 since SQLite has no concept of database users and/or passwords.
1058 'gitcvs.dbuser' supports variable substitution (see
1059 linkgit:git-cvsserver[1] for details).
1061 gitcvs.dbTableNamePrefix::
1062 Database table name prefix. Prepended to the names of any
1063 database tables used, allowing a single database to be used
1064 for several repositories. Supports variable substitution (see
1065 linkgit:git-cvsserver[1] for details). Any non-alphabetic
1066 characters will be replaced with underscores.
1068 All gitcvs variables except for 'gitcvs.usecrlfattr' and
1069 'gitcvs.allbinary' can also be specified as
1070 'gitcvs.<access_method>.<varname>' (where 'access_method'
1071 is one of "ext" and "pserver") to make them apply only for the given
1072 access method.
1074 gui.commitmsgwidth::
1075 Defines how wide the commit message window is in the
1076 linkgit:git-gui[1]. "75" is the default.
1078 gui.diffcontext::
1079 Specifies how many context lines should be used in calls to diff
1080 made by the linkgit:git-gui[1]. The default is "5".
1082 gui.encoding::
1083 Specifies the default encoding to use for displaying of
1084 file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1085 It can be overridden by setting the 'encoding' attribute
1086 for relevant files (see linkgit:gitattributes[5]).
1087 If this option is not set, the tools default to the
1088 locale encoding.
1090 gui.matchtrackingbranch::
1091 Determines if new branches created with linkgit:git-gui[1] should
1092 default to tracking remote branches with matching names or
1093 not. Default: "false".
1095 gui.newbranchtemplate::
1096 Is used as suggested name when creating new branches using the
1097 linkgit:git-gui[1].
1099 gui.pruneduringfetch::
1100 "true" if linkgit:git-gui[1] should prune tracking branches when
1101 performing a fetch. The default value is "false".
1103 gui.trustmtime::
1104 Determines if linkgit:git-gui[1] should trust the file modification
1105 timestamp or not. By default the timestamps are not trusted.
1107 gui.spellingdictionary::
1108 Specifies the dictionary used for spell checking commit messages in
1109 the linkgit:git-gui[1]. When set to "none" spell checking is turned
1110 off.
1112 gui.fastcopyblame::
1113 If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1114 location detection. It makes blame significantly faster on huge
1115 repositories at the expense of less thorough copy detection.
1117 gui.copyblamethreshold::
1118 Specifies the threshold to use in 'git gui blame' original location
1119 detection, measured in alphanumeric characters. See the
1120 linkgit:git-blame[1] manual for more information on copy detection.
1122 gui.blamehistoryctx::
1123 Specifies the radius of history context in days to show in
1124 linkgit:gitk[1] for the selected commit, when the `Show History
1125 Context` menu item is invoked from 'git gui blame'. If this
1126 variable is set to zero, the whole history is shown.
1128 guitool.<name>.cmd::
1129 Specifies the shell command line to execute when the corresponding item
1130 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1131 mandatory for every tool. The command is executed from the root of
1132 the working directory, and in the environment it receives the name of
1133 the tool as 'GIT_GUITOOL', the name of the currently selected file as
1134 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1135 the head is detached, 'CUR_BRANCH' is empty).
1137 guitool.<name>.needsfile::
1138 Run the tool only if a diff is selected in the GUI. It guarantees
1139 that 'FILENAME' is not empty.
1141 guitool.<name>.noconsole::
1142 Run the command silently, without creating a window to display its
1143 output.
1145 guitool.<name>.norescan::
1146 Don't rescan the working directory for changes after the tool
1147 finishes execution.
1149 guitool.<name>.confirm::
1150 Show a confirmation dialog before actually running the tool.
1152 guitool.<name>.argprompt::
1153 Request a string argument from the user, and pass it to the tool
1154 through the 'ARGS' environment variable. Since requesting an
1155 argument implies confirmation, the 'confirm' option has no effect
1156 if this is enabled. If the option is set to 'true', 'yes', or '1',
1157 the dialog uses a built-in generic prompt; otherwise the exact
1158 value of the variable is used.
1160 guitool.<name>.revprompt::
1161 Request a single valid revision from the user, and set the
1162 'REVISION' environment variable. In other aspects this option
1163 is similar to 'argprompt', and can be used together with it.
1165 guitool.<name>.revunmerged::
1166 Show only unmerged branches in the 'revprompt' subdialog.
1167 This is useful for tools similar to merge or rebase, but not
1168 for things like checkout or reset.
1170 guitool.<name>.title::
1171 Specifies the title to use for the prompt dialog. The default
1172 is the tool name.
1174 guitool.<name>.prompt::
1175 Specifies the general prompt string to display at the top of
1176 the dialog, before subsections for 'argprompt' and 'revprompt'.
1177 The default value includes the actual command.
1179 help.browser::
1180 Specify the browser that will be used to display help in the
1181 'web' format. See linkgit:git-help[1].
1183 help.format::
1184 Override the default help format used by linkgit:git-help[1].
1185 Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1186 the default. 'web' and 'html' are the same.
1188 help.autocorrect::
1189 Automatically correct and execute mistyped commands after
1190 waiting for the given number of deciseconds (0.1 sec). If more
1191 than one command can be deduced from the entered text, nothing
1192 will be executed. If the value of this option is negative,
1193 the corrected command will be executed immediately. If the
1194 value is 0 - the command will be just shown but not executed.
1195 This is the default.
1197 http.proxy::
1198 Override the HTTP proxy, normally configured using the 'http_proxy'
1199 environment variable (see linkgit:curl[1]). This can be overridden
1200 on a per-remote basis; see remote.<name>.proxy
1202 http.sslVerify::
1203 Whether to verify the SSL certificate when fetching or pushing
1204 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1205 variable.
1207 http.sslCert::
1208 File containing the SSL certificate when fetching or pushing
1209 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1210 variable.
1212 http.sslKey::
1213 File containing the SSL private key when fetching or pushing
1214 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1215 variable.
1217 http.sslCertPasswordProtected::
1218 Enable git's password prompt for the SSL certificate. Otherwise
1219 OpenSSL will prompt the user, possibly many times, if the
1220 certificate or private key is encrypted. Can be overridden by the
1221 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1223 http.sslCAInfo::
1224 File containing the certificates to verify the peer with when
1225 fetching or pushing over HTTPS. Can be overridden by the
1226 'GIT_SSL_CAINFO' environment variable.
1228 http.sslCAPath::
1229 Path containing files with the CA certificates to verify the peer
1230 with when fetching or pushing over HTTPS. Can be overridden
1231 by the 'GIT_SSL_CAPATH' environment variable.
1233 http.maxRequests::
1234 How many HTTP requests to launch in parallel. Can be overridden
1235 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1237 http.minSessions::
1238 The number of curl sessions (counted across slots) to be kept across
1239 requests. They will not be ended with curl_easy_cleanup() until
1240 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1241 value will be capped at 1. Defaults to 1.
1243 http.postBuffer::
1244 Maximum size in bytes of the buffer used by smart HTTP
1245 transports when POSTing data to the remote system.
1246 For requests larger than this buffer size, HTTP/1.1 and
1247 Transfer-Encoding: chunked is used to avoid creating a
1248 massive pack file locally. Default is 1 MiB, which is
1249 sufficient for most requests.
1251 http.lowSpeedLimit, http.lowSpeedTime::
1252 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1253 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1254 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1255 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1257 http.noEPSV::
1258 A boolean which disables using of EPSV ftp command by curl.
1259 This can helpful with some "poor" ftp servers which don't
1260 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1261 environment variable. Default is false (curl will use EPSV).
1263 http.useragent::
1264 The HTTP USER_AGENT string presented to an HTTP server. The default
1265 value represents the version of the client git such as git/1.7.1.
1266 This option allows you to override this value to a more common value
1267 such as Mozilla/4.0. This may be necessary, for instance, if
1268 connecting through a firewall that restricts HTTP connections to a set
1269 of common USER_AGENT strings (but not including those like git/1.7.1).
1270 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1272 i18n.commitEncoding::
1273 Character encoding the commit messages are stored in; git itself
1274 does not care per se, but this information is necessary e.g. when
1275 importing commits from emails or in the gitk graphical history
1276 browser (and possibly at other places in the future or in other
1277 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1279 i18n.logOutputEncoding::
1280 Character encoding the commit messages are converted to when
1281 running 'git log' and friends.
1283 imap::
1284 The configuration variables in the 'imap' section are described
1285 in linkgit:git-imap-send[1].
1287 init.templatedir::
1288 Specify the directory from which templates will be copied.
1289 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1291 instaweb.browser::
1292 Specify the program that will be used to browse your working
1293 repository in gitweb. See linkgit:git-instaweb[1].
1295 instaweb.httpd::
1296 The HTTP daemon command-line to start gitweb on your working
1297 repository. See linkgit:git-instaweb[1].
1299 instaweb.local::
1300 If true the web server started by linkgit:git-instaweb[1] will
1301 be bound to the local IP (127.0.0.1).
1303 instaweb.modulepath::
1304 The default module path for linkgit:git-instaweb[1] to use
1305 instead of /usr/lib/apache2/modules. Only used if httpd
1306 is Apache.
1308 instaweb.port::
1309 The port number to bind the gitweb httpd to. See
1310 linkgit:git-instaweb[1].
1312 interactive.singlekey::
1313 In interactive commands, allow the user to provide one-letter
1314 input with a single key (i.e., without hitting enter).
1315 Currently this is used only by the `\--patch` mode of
1316 linkgit:git-add[1]. Note that this setting is silently
1317 ignored if portable keystroke input is not available.
1319 log.date::
1320 Set the default date-time mode for the 'log' command.
1321 Setting a value for log.date is similar to using 'git log''s
1322 `\--date` option. Possible values are `relative`, `local`,
1323 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1324 for details.
1326 log.decorate::
1327 Print out the ref names of any commits that are shown by the log
1328 command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1329 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1330 specified, the full ref name (including prefix) will be printed.
1331 This is the same as the log commands '--decorate' option.
1333 log.showroot::
1334 If true, the initial commit will be shown as a big creation event.
1335 This is equivalent to a diff against an empty tree.
1336 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1337 normally hide the root commit will now show it. True by default.
1339 mailmap.file::
1340 The location of an augmenting mailmap file. The default
1341 mailmap, located in the root of the repository, is loaded
1342 first, then the mailmap file pointed to by this variable.
1343 The location of the mailmap file may be in a repository
1344 subdirectory, or somewhere outside of the repository itself.
1345 See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1347 man.viewer::
1348 Specify the programs that may be used to display help in the
1349 'man' format. See linkgit:git-help[1].
1351 man.<tool>.cmd::
1352 Specify the command to invoke the specified man viewer. The
1353 specified command is evaluated in shell with the man page
1354 passed as argument. (See linkgit:git-help[1].)
1356 man.<tool>.path::
1357 Override the path for the given tool that may be used to
1358 display help in the 'man' format. See linkgit:git-help[1].
1360 include::merge-config.txt[]
1362 mergetool.<tool>.path::
1363 Override the path for the given tool. This is useful in case
1364 your tool is not in the PATH.
1366 mergetool.<tool>.cmd::
1367 Specify the command to invoke the specified merge tool. The
1368 specified command is evaluated in shell with the following
1369 variables available: 'BASE' is the name of a temporary file
1370 containing the common base of the files to be merged, if available;
1371 'LOCAL' is the name of a temporary file containing the contents of
1372 the file on the current branch; 'REMOTE' is the name of a temporary
1373 file containing the contents of the file from the branch being
1374 merged; 'MERGED' contains the name of the file to which the merge
1375 tool should write the results of a successful merge.
1377 mergetool.<tool>.trustExitCode::
1378 For a custom merge command, specify whether the exit code of
1379 the merge command can be used to determine whether the merge was
1380 successful. If this is not set to true then the merge target file
1381 timestamp is checked and the merge assumed to have been successful
1382 if the file has been updated, otherwise the user is prompted to
1383 indicate the success of the merge.
1385 mergetool.keepBackup::
1386 After performing a merge, the original file with conflict markers
1387 can be saved as a file with a `.orig` extension. If this variable
1388 is set to `false` then this file is not preserved. Defaults to
1389 `true` (i.e. keep the backup files).
1391 mergetool.keepTemporaries::
1392 When invoking a custom merge tool, git uses a set of temporary
1393 files to pass to the tool. If the tool returns an error and this
1394 variable is set to `true`, then these temporary files will be
1395 preserved, otherwise they will be removed after the tool has
1396 exited. Defaults to `false`.
1398 mergetool.prompt::
1399 Prompt before each invocation of the merge resolution program.
1401 notes.displayRef::
1402 The (fully qualified) refname from which to show notes when
1403 showing commit messages. The value of this variable can be set
1404 to a glob, in which case notes from all matching refs will be
1405 shown. You may also specify this configuration variable
1406 several times. A warning will be issued for refs that do not
1407 exist, but a glob that does not match any refs is silently
1408 ignored.
1409 +
1410 This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1411 environment variable, which must be a colon separated list of refs or
1412 globs.
1413 +
1414 The effective value of "core.notesRef" (possibly overridden by
1415 GIT_NOTES_REF) is also implicitly added to the list of refs to be
1416 displayed.
1418 notes.rewrite.<command>::
1419 When rewriting commits with <command> (currently `amend` or
1420 `rebase`) and this variable is set to `true`, git
1421 automatically copies your notes from the original to the
1422 rewritten commit. Defaults to `true`, but see
1423 "notes.rewriteRef" below.
1425 notes.rewriteMode::
1426 When copying notes during a rewrite (see the
1427 "notes.rewrite.<command>" option), determines what to do if
1428 the target commit already has a note. Must be one of
1429 `overwrite`, `concatenate`, or `ignore`. Defaults to
1430 `concatenate`.
1431 +
1432 This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1433 environment variable.
1435 notes.rewriteRef::
1436 When copying notes during a rewrite, specifies the (fully
1437 qualified) ref whose notes should be copied. The ref may be a
1438 glob, in which case notes in all matching refs will be copied.
1439 You may also specify this configuration several times.
1440 +
1441 Does not have a default value; you must configure this variable to
1442 enable note rewriting.
1443 +
1444 This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1445 environment variable, which must be a colon separated list of refs or
1446 globs.
1448 pack.window::
1449 The size of the window used by linkgit:git-pack-objects[1] when no
1450 window size is given on the command line. Defaults to 10.
1452 pack.depth::
1453 The maximum delta depth used by linkgit:git-pack-objects[1] when no
1454 maximum depth is given on the command line. Defaults to 50.
1456 pack.windowMemory::
1457 The window memory size limit used by linkgit:git-pack-objects[1]
1458 when no limit is given on the command line. The value can be
1459 suffixed with "k", "m", or "g". Defaults to 0, meaning no
1460 limit.
1462 pack.compression::
1463 An integer -1..9, indicating the compression level for objects
1464 in a pack file. -1 is the zlib default. 0 means no
1465 compression, and 1..9 are various speed/size tradeoffs, 9 being
1466 slowest. If not set, defaults to core.compression. If that is
1467 not set, defaults to -1, the zlib default, which is "a default
1468 compromise between speed and compression (currently equivalent
1469 to level 6)."
1471 pack.deltaCacheSize::
1472 The maximum memory in bytes used for caching deltas in
1473 linkgit:git-pack-objects[1] before writing them out to a pack.
1474 This cache is used to speed up the writing object phase by not
1475 having to recompute the final delta result once the best match
1476 for all objects is found. Repacking large repositories on machines
1477 which are tight with memory might be badly impacted by this though,
1478 especially if this cache pushes the system into swapping.
1479 A value of 0 means no limit. The smallest size of 1 byte may be
1480 used to virtually disable this cache. Defaults to 256 MiB.
1482 pack.deltaCacheLimit::
1483 The maximum size of a delta, that is cached in
1484 linkgit:git-pack-objects[1]. This cache is used to speed up the
1485 writing object phase by not having to recompute the final delta
1486 result once the best match for all objects is found. Defaults to 1000.
1488 pack.threads::
1489 Specifies the number of threads to spawn when searching for best
1490 delta matches. This requires that linkgit:git-pack-objects[1]
1491 be compiled with pthreads otherwise this option is ignored with a
1492 warning. This is meant to reduce packing time on multiprocessor
1493 machines. The required amount of memory for the delta search window
1494 is however multiplied by the number of threads.
1495 Specifying 0 will cause git to auto-detect the number of CPU's
1496 and set the number of threads accordingly.
1498 pack.indexVersion::
1499 Specify the default pack index version. Valid values are 1 for
1500 legacy pack index used by Git versions prior to 1.5.2, and 2 for
1501 the new pack index with capabilities for packs larger than 4 GB
1502 as well as proper protection against the repacking of corrupted
1503 packs. Version 2 is the default. Note that version 2 is enforced
1504 and this config option ignored whenever the corresponding pack is
1505 larger than 2 GB.
1506 +
1507 If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1508 cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1509 that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1510 other side may give you a repository that cannot be accessed with your
1511 older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1512 you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1513 the `{asterisk}.idx` file.
1515 pack.packSizeLimit::
1516 The maximum size of a pack. This setting only affects
1517 packing to a file when repacking, i.e. the git:// protocol
1518 is unaffected. It can be overridden by the `\--max-pack-size`
1519 option of linkgit:git-repack[1]. The minimum size allowed is
1520 limited to 1 MiB. The default is unlimited.
1521 Common unit suffixes of 'k', 'm', or 'g' are
1522 supported.
1524 pager.<cmd>::
1525 Allows turning on or off pagination of the output of a
1526 particular git subcommand when writing to a tty. If
1527 `\--paginate` or `\--no-pager` is specified on the command line,
1528 it takes precedence over this option. To disable pagination for
1529 all commands, set `core.pager` or `GIT_PAGER` to `cat`.
1531 pretty.<name>::
1532 Alias for a --pretty= format string, as specified in
1533 linkgit:git-log[1]. Any aliases defined here can be used just
1534 as the built-in pretty formats could. For example,
1535 running `git config pretty.changelog "format:{asterisk} %H %s"`
1536 would cause the invocation `git log --pretty=changelog`
1537 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.
1538 Note that an alias with the same name as a built-in format
1539 will be silently ignored.
1541 pull.octopus::
1542 The default merge strategy to use when pulling multiple branches
1543 at once.
1545 pull.twohead::
1546 The default merge strategy to use when pulling a single branch.
1548 push.default::
1549 Defines the action git push should take if no refspec is given
1550 on the command line, no refspec is configured in the remote, and
1551 no refspec is implied by any of the options given on the command
1552 line. Possible values are:
1553 +
1554 * `nothing` do not push anything.
1555 * `matching` push all matching branches.
1556 All branches having the same name in both ends are considered to be
1557 matching. This is the default.
1558 * `tracking` push the current branch to its upstream branch.
1559 * `current` push the current branch to a branch of the same name.
1561 rebase.stat::
1562 Whether to show a diffstat of what changed upstream since the last
1563 rebase. False by default.
1565 rebase.autosquash::
1566 If set to true enable '--autosquash' option by default.
1568 receive.autogc::
1569 By default, git-receive-pack will run "git-gc --auto" after
1570 receiving data from git-push and updating refs. You can stop
1571 it by setting this variable to false.
1573 receive.fsckObjects::
1574 If it is set to true, git-receive-pack will check all received
1575 objects. It will abort in the case of a malformed object or a
1576 broken link. The result of an abort are only dangling objects.
1577 Defaults to false.
1579 receive.unpackLimit::
1580 If the number of objects received in a push is below this
1581 limit then the objects will be unpacked into loose object
1582 files. However if the number of received objects equals or
1583 exceeds this limit then the received pack will be stored as
1584 a pack, after adding any missing delta bases. Storing the
1585 pack from a push can make the push operation complete faster,
1586 especially on slow filesystems. If not set, the value of
1587 `transfer.unpackLimit` is used instead.
1589 receive.denyDeletes::
1590 If set to true, git-receive-pack will deny a ref update that deletes
1591 the ref. Use this to prevent such a ref deletion via a push.
1593 receive.denyDeleteCurrent::
1594 If set to true, git-receive-pack will deny a ref update that
1595 deletes the currently checked out branch of a non-bare repository.
1597 receive.denyCurrentBranch::
1598 If set to true or "refuse", git-receive-pack will deny a ref update
1599 to the currently checked out branch of a non-bare repository.
1600 Such a push is potentially dangerous because it brings the HEAD
1601 out of sync with the index and working tree. If set to "warn",
1602 print a warning of such a push to stderr, but allow the push to
1603 proceed. If set to false or "ignore", allow such pushes with no
1604 message. Defaults to "refuse".
1606 receive.denyNonFastForwards::
1607 If set to true, git-receive-pack will deny a ref update which is
1608 not a fast-forward. Use this to prevent such an update via a push,
1609 even if that push is forced. This configuration variable is
1610 set when initializing a shared repository.
1612 receive.updateserverinfo::
1613 If set to true, git-receive-pack will run git-update-server-info
1614 after receiving data from git-push and updating refs.
1616 remote.<name>.url::
1617 The URL of a remote repository. See linkgit:git-fetch[1] or
1618 linkgit:git-push[1].
1620 remote.<name>.pushurl::
1621 The push URL of a remote repository. See linkgit:git-push[1].
1623 remote.<name>.proxy::
1624 For remotes that require curl (http, https and ftp), the URL to
1625 the proxy to use for that remote. Set to the empty string to
1626 disable proxying for that remote.
1628 remote.<name>.fetch::
1629 The default set of "refspec" for linkgit:git-fetch[1]. See
1630 linkgit:git-fetch[1].
1632 remote.<name>.push::
1633 The default set of "refspec" for linkgit:git-push[1]. See
1634 linkgit:git-push[1].
1636 remote.<name>.mirror::
1637 If true, pushing to this remote will automatically behave
1638 as if the `\--mirror` option was given on the command line.
1640 remote.<name>.skipDefaultUpdate::
1641 If true, this remote will be skipped by default when updating
1642 using linkgit:git-fetch[1] or the `update` subcommand of
1643 linkgit:git-remote[1].
1645 remote.<name>.skipFetchAll::
1646 If true, this remote will be skipped by default when updating
1647 using linkgit:git-fetch[1] or the `update` subcommand of
1648 linkgit:git-remote[1].
1650 remote.<name>.receivepack::
1651 The default program to execute on the remote side when pushing. See
1652 option \--receive-pack of linkgit:git-push[1].
1654 remote.<name>.uploadpack::
1655 The default program to execute on the remote side when fetching. See
1656 option \--upload-pack of linkgit:git-fetch-pack[1].
1658 remote.<name>.tagopt::
1659 Setting this value to \--no-tags disables automatic tag following when
1660 fetching from remote <name>. Setting it to \--tags will fetch every
1661 tag from remote <name>, even if they are not reachable from remote
1662 branch heads. Passing these flags directly to linkgit:git-fetch[1] can
1663 override this setting. See options \--tags and \--no-tags of
1664 linkgit:git-fetch[1].
1666 remote.<name>.vcs::
1667 Setting this to a value <vcs> will cause git to interact with
1668 the remote with the git-remote-<vcs> helper.
1670 remotes.<group>::
1671 The list of remotes which are fetched by "git remote update
1672 <group>". See linkgit:git-remote[1].
1674 repack.usedeltabaseoffset::
1675 By default, linkgit:git-repack[1] creates packs that use
1676 delta-base offset. If you need to share your repository with
1677 git older than version 1.4.4, either directly or via a dumb
1678 protocol such as http, then you need to set this option to
1679 "false" and repack. Access from old git versions over the
1680 native protocol are unaffected by this option.
1682 rerere.autoupdate::
1683 When set to true, `git-rerere` updates the index with the
1684 resulting contents after it cleanly resolves conflicts using
1685 previously recorded resolution. Defaults to false.
1687 rerere.enabled::
1688 Activate recording of resolved conflicts, so that identical
1689 conflict hunks can be resolved automatically, should they
1690 be encountered again. linkgit:git-rerere[1] command is by
1691 default enabled if you create `rr-cache` directory under
1692 `$GIT_DIR`, but can be disabled by setting this option to false.
1694 sendemail.identity::
1695 A configuration identity. When given, causes values in the
1696 'sendemail.<identity>' subsection to take precedence over
1697 values in the 'sendemail' section. The default identity is
1698 the value of 'sendemail.identity'.
1700 sendemail.smtpencryption::
1701 See linkgit:git-send-email[1] for description. Note that this
1702 setting is not subject to the 'identity' mechanism.
1704 sendemail.smtpssl::
1705 Deprecated alias for 'sendemail.smtpencryption = ssl'.
1707 sendemail.<identity>.*::
1708 Identity-specific versions of the 'sendemail.*' parameters
1709 found below, taking precedence over those when the this
1710 identity is selected, through command-line or
1711 'sendemail.identity'.
1713 sendemail.aliasesfile::
1714 sendemail.aliasfiletype::
1715 sendemail.bcc::
1716 sendemail.cc::
1717 sendemail.cccmd::
1718 sendemail.chainreplyto::
1719 sendemail.confirm::
1720 sendemail.envelopesender::
1721 sendemail.from::
1722 sendemail.multiedit::
1723 sendemail.signedoffbycc::
1724 sendemail.smtppass::
1725 sendemail.suppresscc::
1726 sendemail.suppressfrom::
1727 sendemail.to::
1728 sendemail.smtpdomain::
1729 sendemail.smtpserver::
1730 sendemail.smtpserverport::
1731 sendemail.smtpuser::
1732 sendemail.thread::
1733 sendemail.validate::
1734 See linkgit:git-send-email[1] for description.
1736 sendemail.signedoffcc::
1737 Deprecated alias for 'sendemail.signedoffbycc'.
1739 showbranch.default::
1740 The default set of branches for linkgit:git-show-branch[1].
1741 See linkgit:git-show-branch[1].
1743 status.relativePaths::
1744 By default, linkgit:git-status[1] shows paths relative to the
1745 current directory. Setting this variable to `false` shows paths
1746 relative to the repository root (this was the default for git
1747 prior to v1.5.4).
1749 status.showUntrackedFiles::
1750 By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1751 files which are not currently tracked by Git. Directories which
1752 contain only untracked files, are shown with the directory name
1753 only. Showing untracked files means that Git needs to lstat() all
1754 all the files in the whole repository, which might be slow on some
1755 systems. So, this variable controls how the commands displays
1756 the untracked files. Possible values are:
1757 +
1758 --
1759 - 'no' - Show no untracked files
1760 - 'normal' - Shows untracked files and directories
1761 - 'all' - Shows also individual files in untracked directories.
1762 --
1763 +
1764 If this variable is not specified, it defaults to 'normal'.
1765 This variable can be overridden with the -u|--untracked-files option
1766 of linkgit:git-status[1] and linkgit:git-commit[1].
1768 status.submodulesummary::
1769 Defaults to false.
1770 If this is set to a non zero number or true (identical to -1 or an
1771 unlimited number), the submodule summary will be enabled and a
1772 summary of commits for modified submodules will be shown (see
1773 --summary-limit option of linkgit:git-submodule[1]).
1775 submodule.<name>.path::
1776 submodule.<name>.url::
1777 submodule.<name>.update::
1778 The path within this project, URL, and the updating strategy
1779 for a submodule. These variables are initially populated
1780 by 'git submodule init'; edit them to override the
1781 URL and other values found in the `.gitmodules` file. See
1782 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
1784 submodule.<name>.ignore::
1785 Defines under what circumstances "git status" and the diff family show
1786 a submodule as modified. When set to "all", it will never be considered
1787 modified, "dirty" will ignore all changes to the submodules work tree and
1788 takes only differences between the HEAD of the submodule and the commit
1789 recorded in the superproject into account. "untracked" will additionally
1790 let submodules with modified tracked files in their work tree show up.
1791 Using "none" (the default when this option is not set) also shows
1792 submodules that have untracked files in their work tree as changed.
1793 This setting overrides any setting made in .gitmodules for this submodule,
1794 both settings can be overridden on the command line by using the
1795 "--ignore-submodules" option.
1797 tar.umask::
1798 This variable can be used to restrict the permission bits of
1799 tar archive entries. The default is 0002, which turns off the
1800 world write bit. The special value "user" indicates that the
1801 archiving user's umask will be used instead. See umask(2) and
1802 linkgit:git-archive[1].
1804 transfer.unpackLimit::
1805 When `fetch.unpackLimit` or `receive.unpackLimit` are
1806 not set, the value of this variable is used instead.
1807 The default value is 100.
1809 url.<base>.insteadOf::
1810 Any URL that starts with this value will be rewritten to
1811 start, instead, with <base>. In cases where some site serves a
1812 large number of repositories, and serves them with multiple
1813 access methods, and some users need to use different access
1814 methods, this feature allows people to specify any of the
1815 equivalent URLs and have git automatically rewrite the URL to
1816 the best alternative for the particular user, even for a
1817 never-before-seen repository on the site. When more than one
1818 insteadOf strings match a given URL, the longest match is used.
1820 url.<base>.pushInsteadOf::
1821 Any URL that starts with this value will not be pushed to;
1822 instead, it will be rewritten to start with <base>, and the
1823 resulting URL will be pushed to. In cases where some site serves
1824 a large number of repositories, and serves them with multiple
1825 access methods, some of which do not allow push, this feature
1826 allows people to specify a pull-only URL and have git
1827 automatically use an appropriate URL to push, even for a
1828 never-before-seen repository on the site. When more than one
1829 pushInsteadOf strings match a given URL, the longest match is
1830 used. If a remote has an explicit pushurl, git will ignore this
1831 setting for that remote.
1833 user.email::
1834 Your email address to be recorded in any newly created commits.
1835 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1836 'EMAIL' environment variables. See linkgit:git-commit-tree[1].
1838 user.name::
1839 Your full name to be recorded in any newly created commits.
1840 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1841 environment variables. See linkgit:git-commit-tree[1].
1843 user.signingkey::
1844 If linkgit:git-tag[1] is not selecting the key you want it to
1845 automatically when creating a signed tag, you can override the
1846 default selection with this variable. This option is passed
1847 unchanged to gpg's --local-user parameter, so you may specify a key
1848 using any method that gpg supports.
1850 web.browser::
1851 Specify a web browser that may be used by some commands.
1852 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]
1853 may use it.