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