4 The git configuration file contains a number of variables that affect
5 the git command's behavior. The `.git/config` file in each repository
6 is used to store the configuration for that repository, and
7 `$HOME/.gitconfig` is used to store a per-user configuration as
8 fallback values for the `.git/config` file. The file `/etc/gitconfig`
9 can be used to store a system-wide default configuration.
11 The configuration variables are used by both the git plumbing
12 and the porcelains. The variables are divided into sections, wherein
13 the fully qualified variable name of the variable itself is the last
14 dot-separated segment and the section name is everything before the last
15 dot. The variable names are case-insensitive and only alphanumeric
16 characters are allowed. Some variables may appear multiple times.
21 The syntax is fairly flexible and permissive; whitespaces are mostly
22 ignored. The '#' and ';' characters begin comments to the end of line,
23 blank lines are ignored.
25 The file consists of sections and variables. A section begins with
26 the name of the section in square brackets and continues until the next
27 section begins. Section names are not case sensitive. Only alphanumeric
28 characters, `-` and `.` are allowed in section names. Each variable
29 must belong to some section, which means that there must be a section
30 header before the first setting of a variable.
32 Sections can be further divided into subsections. To begin a subsection
33 put its name in double quotes, separated by space from the section name,
34 in the section header, like in the example below:
37 [section "subsection"]
41 Subsection names are case sensitive and can contain any characters except
42 newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
43 respectively). Section headers cannot span multiple
44 lines. Variables may belong directly to a section or to a given subsection.
45 You can have `[section]` if you have `[section "subsection"]`, but you
48 There is also a deprecated `[section.subsection]` syntax. With this
49 syntax, the subsection name is converted to lower-case and is also
50 compared case sensitively. These subsection names follow the same
51 restrictions as section names.
53 All the other lines (and the remainder of the line after the section
54 header) are recognized as setting variables, in the form
55 'name = value'. If there is no equal sign on the line, the entire line
56 is taken as 'name' and the variable is recognized as boolean "true".
57 The variable names are case-insensitive and only alphanumeric
58 characters and `-` are allowed. There can be more than one value
59 for a given variable; we say then that variable is multivalued.
61 Leading and trailing whitespace in a variable value is discarded.
62 Internal whitespace within a variable value is retained verbatim.
64 The values following the equals sign in variable assign are all either
65 a string, an integer, or a boolean. Boolean values may be given as yes/no,
66 1/0, true/false or on/off. Case is not significant in boolean values, when
67 converting value to the canonical form using '--bool' type specifier;
68 'git config' will ensure that the output is "true" or "false".
70 String values may be entirely or partially enclosed in double quotes.
71 You need to enclose variable values in double quotes if you want to
72 preserve leading or trailing whitespace, or if the variable value contains
73 comment characters (i.e. it contains '#' or ';').
74 Double quote `"` and backslash `\` characters in variable values must
75 be escaped: use `\"` for `"` and `\\` for `\`.
77 The following escape sequences (beside `\"` and `\\`) are recognized:
78 `\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
79 and `\b` for backspace (BS). No other char escape sequence, nor octal
80 char sequences are valid.
82 Variable values ending in a `\` are continued on the next line in the
83 customary UNIX fashion.
85 Some variables may require a special value format.
92 ; Don't trust file modes
97 external = /usr/local/bin/diff-wrapper
102 merge = refs/heads/devel
106 gitProxy="ssh" for "kernel.org"
107 gitProxy=default-proxy ; for the rest
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.
118 When set to 'true', display the given optional help message.
119 When set to 'false', do not display. The configuration variables
124 Advice shown when linkgit:git-push[1] refuses
125 non-fast-forward refs. Default: true.
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.
131 Advice shown when linkgit:git-merge[1] refuses to
132 merge to avoid overwriting local changes.
135 Advices shown by various commands when conflicts
136 prevent the operation from being performed.
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.
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.
150 If false, the executable bit differences between the index and
151 the working tree are ignored; useful on broken filesystems like FAT.
152 See linkgit:git-update-index[1].
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.
159 (Windows-only) If true (which is the default), mark newly-created
160 directories and files whose name starts with a dot as hidden.
161 If 'dotGitOnly', only the .git/ directory is hidden, but no other
162 files starting with a dot.
164 core.ignoreCygwinFSTricks::
165 This option is only used by Cygwin implementation of Git. If false,
166 the Cygwin stat() and lstat() functions are used. This may be useful
167 if your repository consists of a few separate directories joined in
168 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
169 whenever it is possible and falls back to Cygwin functions only to
170 handle symbol links. The native mode is more than twice faster than
171 normal Cygwin l/stat() functions. True by default, unless core.filemode
172 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
173 POSIX emulation is required to support core.filemode.
176 If true, this option enables various workarounds to enable
177 git to work better on filesystems that are not case sensitive,
178 like FAT. For example, if a directory listing finds
179 "makefile" when git expects "Makefile", git will assume
180 it is really the same file, and continue to remember it as
183 The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
184 will probe and set core.ignorecase true if appropriate when the repository
188 If false, the ctime differences between the index and the
189 working tree are ignored; useful when the inode change time
190 is regularly modified by something outside Git (file system
191 crawlers and some backup systems).
192 See linkgit:git-update-index[1]. True by default.
195 The commands that output paths (e.g. 'ls-files',
196 'diff'), when not given the `-z` option, will quote
197 "unusual" characters in the pathname by enclosing the
198 pathname in a double-quote pair and with backslashes the
199 same way strings in C source code are quoted. If this
200 variable is set to false, the bytes higher than 0x80 are
201 not quoted but output as verbatim. Note that double
202 quote, backslash and control characters are always
203 quoted without `-z` regardless of the setting of this
207 Sets the line ending type to use in the working directory for
208 files that have the `text` property set. Alternatives are
209 'lf', 'crlf' and 'native', which uses the platform's native
210 line ending. The default value is `native`. See
211 linkgit:gitattributes[5] for more information on end-of-line
215 If true, makes git check if converting `CRLF` is reversible when
216 end-of-line conversion is active. Git will verify if a command
217 modifies a file in the work tree either directly or indirectly.
218 For example, committing a file followed by checking out the
219 same file should yield the original file in the work tree. If
220 this is not the case for the current setting of
221 `core.autocrlf`, git will reject the file. The variable can
222 be set to "warn", in which case git will only warn about an
223 irreversible conversion but continue the operation.
225 CRLF conversion bears a slight chance of corrupting data.
226 When it is enabled, git will convert CRLF to LF during commit and LF to
227 CRLF during checkout. A file that contains a mixture of LF and
228 CRLF before the commit cannot be recreated by git. For text
229 files this is the right thing to do: it corrects line endings
230 such that we have only LF line endings in the repository.
231 But for binary files that are accidentally classified as text the
232 conversion can corrupt data.
234 If you recognize such corruption early you can easily fix it by
235 setting the conversion type explicitly in .gitattributes. Right
236 after committing you still have the original file in your work
237 tree and this file is not yet corrupted. You can explicitly tell
238 git that this file is binary and git will handle the file
241 Unfortunately, the desired effect of cleaning up text files with
242 mixed line endings and the undesired effect of corrupting binary
243 files cannot be distinguished. In both cases CRLFs are removed
244 in an irreversible way. For text files this is the right thing
245 to do because CRLFs are line endings, while for binary files
246 converting CRLFs corrupts data.
248 Note, this safety check does not mean that a checkout will generate a
249 file identical to the original file for a different setting of
250 `core.eol` and `core.autocrlf`, but only for the current one. For
251 example, a text file with `LF` would be accepted with `core.eol=lf`
252 and could later be checked out with `core.eol=crlf`, in which case the
253 resulting file would contain `CRLF`, although the original file
254 contained `LF`. However, in both work trees the line endings would be
255 consistent, that is either all `LF` or all `CRLF`, but never mixed. A
256 file with mixed line endings would be reported by the `core.safecrlf`
260 Setting this variable to "true" is almost the same as setting
261 the `text` attribute to "auto" on all files except that text
262 files are not guaranteed to be normalized: files that contain
263 `CRLF` in the repository will not be touched. Use this
264 setting if you want to have `CRLF` line endings in your
265 working directory even though the repository does not have
266 normalized line endings. This variable can be set to 'input',
267 in which case no output conversion is performed.
270 If false, symbolic links are checked out as small plain files that
271 contain the link text. linkgit:git-update-index[1] and
272 linkgit:git-add[1] will not change the recorded type to regular
273 file. Useful on filesystems like FAT that do not support
276 The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
277 will probe and set core.symlinks false if appropriate when the repository
281 A "proxy command" to execute (as 'command host port') instead
282 of establishing direct connection to the remote server when
283 using the git protocol for fetching. If the variable value is
284 in the "COMMAND for DOMAIN" format, the command is applied only
285 on hostnames ending with the specified domain string. This variable
286 may be set multiple times and is matched in the given order;
287 the first match wins.
289 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
290 (which always applies universally, without the special "for"
293 The special string `none` can be used as the proxy command to
294 specify that no proxy be used for a given domain pattern.
295 This is useful for excluding servers inside a firewall from
296 proxy use, while defaulting to a common proxy for external domains.
299 If true, commands which modify both the working tree and the index
300 will mark the updated paths with the "assume unchanged" bit in the
301 index. These marked files are then assumed to stay unchanged in the
302 working tree, until you mark them otherwise manually - Git will not
303 detect the file changes by lstat() calls. This is useful on systems
304 where those are very slow, such as Microsoft Windows.
305 See linkgit:git-update-index[1].
308 core.preferSymlinkRefs::
309 Instead of the default "symref" format for HEAD
310 and other symbolic reference files, use symbolic links.
311 This is sometimes needed to work with old scripts that
312 expect HEAD to be a symbolic link.
315 If true this repository is assumed to be 'bare' and has no
316 working directory associated with it. If this is the case a
317 number of commands that require a working directory will be
318 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
320 This setting is automatically guessed by linkgit:git-clone[1] or
321 linkgit:git-init[1] when the repository was created. By default a
322 repository that ends in "/.git" is assumed to be not bare (bare =
323 false), while all other repositories are assumed to be bare (bare
327 Set the path to the root of the working tree.
328 This can be overridden by the GIT_WORK_TREE environment
329 variable and the '--work-tree' command line option.
330 The value can be an absolute path or relative to the path to
331 the .git directory, which is either specified by --git-dir
332 or GIT_DIR, or automatically discovered.
333 If --git-dir or GIT_DIR is specified but none of
334 --work-tree, GIT_WORK_TREE and core.worktree is specified,
335 the current working directory is regarded as the top level
336 of your working tree.
338 Note that this variable is honored even when set in a configuration
339 file in a ".git" subdirectory of a directory and its value differs
340 from the latter directory (e.g. "/path/to/.git/config" has
341 core.worktree set to "/different/path"), which is most likely a
342 misconfiguration. Running git commands in the "/path/to" directory will
343 still use "/different/path" as the root of the work tree and can cause
344 confusion unless you know what you are doing (e.g. you are creating a
345 read-only snapshot of the same index to a location different from the
346 repository's usual working tree).
348 core.logAllRefUpdates::
349 Enable the reflog. Updates to a ref <ref> is logged to the file
350 "$GIT_DIR/logs/<ref>", by appending the new and old
351 SHA1, the date/time and the reason of the update, but
352 only when the file exists. If this configuration
353 variable is set to true, missing "$GIT_DIR/logs/<ref>"
354 file is automatically created for branch heads (i.e. under
355 refs/heads/), remote refs (i.e. under refs/remotes/),
356 note refs (i.e. under refs/notes/), and the symbolic ref HEAD.
358 This information can be used to determine what commit
359 was the tip of a branch "2 days ago".
361 This value is true by default in a repository that has
362 a working directory associated with it, and false by
363 default in a bare repository.
365 core.repositoryFormatVersion::
366 Internal variable identifying the repository format and layout
369 core.sharedRepository::
370 When 'group' (or 'true'), the repository is made shareable between
371 several users in a group (making sure all the files and objects are
372 group-writable). When 'all' (or 'world' or 'everybody'), the
373 repository will be readable by all users, additionally to being
374 group-shareable. When 'umask' (or 'false'), git will use permissions
375 reported by umask(2). When '0xxx', where '0xxx' is an octal number,
376 files in the repository will have this mode value. '0xxx' will override
377 user's umask value (whereas the other options will only override
378 requested parts of the user's umask value). Examples: '0660' will make
379 the repo read/write-able for the owner and group, but inaccessible to
380 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
381 repository that is group-readable but not group-writable.
382 See linkgit:git-init[1]. False by default.
384 core.warnAmbiguousRefs::
385 If true, git will warn you if the ref name you passed it is ambiguous
386 and might match multiple refs in the .git/refs/ tree. True by default.
389 An integer -1..9, indicating a default compression level.
390 -1 is the zlib default. 0 means no compression,
391 and 1..9 are various speed/size tradeoffs, 9 being slowest.
392 If set, this provides a default to other compression variables,
393 such as 'core.loosecompression' and 'pack.compression'.
395 core.loosecompression::
396 An integer -1..9, indicating the compression level for objects that
397 are not in a pack file. -1 is the zlib default. 0 means no
398 compression, and 1..9 are various speed/size tradeoffs, 9 being
399 slowest. If not set, defaults to core.compression. If that is
400 not set, defaults to 1 (best speed).
402 core.packedGitWindowSize::
403 Number of bytes of a pack file to map into memory in a
404 single mapping operation. Larger window sizes may allow
405 your system to process a smaller number of large pack files
406 more quickly. Smaller window sizes will negatively affect
407 performance due to increased calls to the operating system's
408 memory manager, but may improve performance when accessing
409 a large number of large pack files.
411 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
412 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
413 be reasonable for all users/operating systems. You probably do
414 not need to adjust this value.
416 Common unit suffixes of 'k', 'm', or 'g' are supported.
418 core.packedGitLimit::
419 Maximum number of bytes to map simultaneously into memory
420 from pack files. If Git needs to access more than this many
421 bytes at once to complete an operation it will unmap existing
422 regions to reclaim virtual address space within the process.
424 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
425 This should be reasonable for all users/operating systems, except on
426 the largest projects. You probably do not need to adjust this value.
428 Common unit suffixes of 'k', 'm', or 'g' are supported.
430 core.deltaBaseCacheLimit::
431 Maximum number of bytes to reserve for caching base objects
432 that may be referenced by multiple deltified objects. By storing the
433 entire decompressed base objects in a cache Git is able
434 to avoid unpacking and decompressing frequently used base
435 objects multiple times.
437 Default is 16 MiB on all platforms. This should be reasonable
438 for all users/operating systems, except on the largest projects.
439 You probably do not need to adjust this value.
441 Common unit suffixes of 'k', 'm', or 'g' are supported.
443 core.bigFileThreshold::
444 Files larger than this size are stored deflated, without
445 attempting delta compression. Storing large files without
446 delta compression avoids excessive memory usage, at the
447 slight expense of increased disk usage.
449 Default is 512 MiB on all platforms. This should be reasonable
450 for most projects as source code and other text files can still
451 be delta compressed, but larger binary media files won't be.
453 Common unit suffixes of 'k', 'm', or 'g' are supported.
456 In addition to '.gitignore' (per-directory) and
457 '.git/info/exclude', git looks into this file for patterns
458 of files which are not meant to be tracked. "{tilde}/" is expanded
459 to the value of `$HOME` and "{tilde}user/" to the specified user's
460 home directory. See linkgit:gitignore[5].
463 Some commands (e.g. svn and http interfaces) that interactively
464 ask for a password can be told to use an external program given
465 via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
466 environment variable. If not set, fall back to the value of the
467 'SSH_ASKPASS' environment variable or, failing that, a simple password
468 prompt. The external program shall be given a suitable prompt as
469 command line argument and write the password on its STDOUT.
471 core.attributesfile::
472 In addition to '.gitattributes' (per-directory) and
473 '.git/info/attributes', git looks into this file for attributes
474 (see linkgit:gitattributes[5]). Path expansions are made the same
475 way as for `core.excludesfile`.
478 Commands such as `commit` and `tag` that lets you edit
479 messages by launching an editor uses the value of this
480 variable when it is set, and the environment variable
481 `GIT_EDITOR` is not set. See linkgit:git-var[1].
484 Text editor used by `git rebase -i` for editing the rebase insn file.
485 The value is meant to be interpreted by the shell when it is used.
486 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
487 When not configured the default commit message editor is used instead.
490 The command that git will use to paginate output. Can
491 be overridden with the `GIT_PAGER` environment
492 variable. Note that git sets the `LESS` environment
493 variable to `FRSX` if it is unset when it runs the
494 pager. One can change these settings by setting the
495 `LESS` variable to some other value. Alternately,
496 these settings can be overridden on a project or
497 global basis by setting the `core.pager` option.
498 Setting `core.pager` has no affect on the `LESS`
499 environment variable behaviour above, so if you want
500 to override git's default settings this way, you need
501 to be explicit. For example, to disable the S option
502 in a backward compatible manner, set `core.pager`
503 to `less -+$LESS -FRX`. This will be passed to the
504 shell by git, which will translate the final command to
505 `LESS=FRSX less -+FRSX -FRX`.
508 A comma separated list of common whitespace problems to
509 notice. 'git diff' will use `color.diff.whitespace` to
510 highlight them, and 'git apply --whitespace=error' will
511 consider them as errors. You can prefix `-` to disable
512 any of them (e.g. `-trailing-space`):
514 * `blank-at-eol` treats trailing whitespaces at the end of the line
515 as an error (enabled by default).
516 * `space-before-tab` treats a space character that appears immediately
517 before a tab character in the initial indent part of the line as an
518 error (enabled by default).
519 * `indent-with-non-tab` treats a line that is indented with 8 or more
520 space characters as an error (not enabled by default).
521 * `tab-in-indent` treats a tab character in the initial indent part of
522 the line as an error (not enabled by default).
523 * `blank-at-eof` treats blank lines added at the end of file as an error
524 (enabled by default).
525 * `trailing-space` is a short-hand to cover both `blank-at-eol` and
527 * `cr-at-eol` treats a carriage-return at the end of line as
528 part of the line terminator, i.e. with it, `trailing-space`
529 does not trigger if the character before such a carriage-return
530 is not a whitespace (not enabled by default).
531 * `tabwidth=<n>` tells how many character positions a tab occupies; this
532 is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent`
533 errors. The default tab width is 8. Allowed values are 1 to 63.
535 core.fsyncobjectfiles::
536 This boolean will enable 'fsync()' when writing object files.
538 This is a total waste of time and effort on a filesystem that orders
539 data writes properly, but can be useful for filesystems that do not use
540 journalling (traditional UNIX filesystems) or that only journal metadata
541 and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
544 Enable parallel index preload for operations like 'git diff'
546 This can speed up operations like 'git diff' and 'git status' especially
547 on filesystems like NFS that have weak caching semantics and thus
548 relatively high IO latencies. With this set to 'true', git will do the
549 index comparison to the filesystem data in parallel, allowing
553 You can set this to 'link', in which case a hardlink followed by
554 a delete of the source are used to make sure that object creation
555 will not overwrite existing objects.
557 On some file system/operating system combinations, this is unreliable.
558 Set this config setting to 'rename' there; However, This will remove the
559 check that makes sure that existing object files will not get overwritten.
562 When showing commit messages, also show notes which are stored in
563 the given ref. The ref must be fully qualified. If the given
564 ref does not exist, it is not an error but means that no
565 notes should be printed.
567 This setting defaults to "refs/notes/commits", and it can be overridden by
568 the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1].
570 core.sparseCheckout::
571 Enable "sparse checkout" feature. See section "Sparse checkout" in
572 linkgit:git-read-tree[1] for more information.
575 Set the length object names are abbreviated to. If unspecified,
576 many commands abbreviate to 7 hexdigits, which may not be enough
577 for abbreviated object names to stay unique for sufficiently long
582 Tells 'git add' to continue adding files when some files cannot be
583 added due to indexing errors. Equivalent to the '--ignore-errors'
584 option of linkgit:git-add[1]. Older versions of git accept only
585 `add.ignore-errors`, which does not follow the usual naming
586 convention for configuration variables. Newer versions of git
587 honor `add.ignoreErrors` as well.
590 Command aliases for the linkgit:git[1] command wrapper - e.g.
591 after defining "alias.last = cat-file commit HEAD", the invocation
592 "git last" is equivalent to "git cat-file commit HEAD". To avoid
593 confusion and troubles with script usage, aliases that
594 hide existing git commands are ignored. Arguments are split by
595 spaces, the usual shell quoting and escaping is supported.
596 quote pair and a backslash can be used to quote them.
598 If the alias expansion is prefixed with an exclamation point,
599 it will be treated as a shell command. For example, defining
600 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
601 "git new" is equivalent to running the shell command
602 "gitk --all --not ORIG_HEAD". Note that shell commands will be
603 executed from the top-level directory of a repository, which may
604 not necessarily be the current directory.
605 'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix'
606 from the original current directory. See linkgit:git-rev-parse[1].
609 If true, git-am will call git-mailsplit for patches in mbox format
610 with parameter '--keep-cr'. In this case git-mailsplit will
611 not remove `\r` from lines ending with `\r\n`. Can be overridden
612 by giving '--no-keep-cr' from the command line.
613 See linkgit:git-am[1], linkgit:git-mailsplit[1].
615 apply.ignorewhitespace::
616 When set to 'change', tells 'git apply' to ignore changes in
617 whitespace, in the same way as the '--ignore-space-change'
619 When set to one of: no, none, never, false tells 'git apply' to
620 respect all whitespace differences.
621 See linkgit:git-apply[1].
624 Tells 'git apply' how to handle whitespaces, in the same way
625 as the '--whitespace' option. See linkgit:git-apply[1].
627 branch.autosetupmerge::
628 Tells 'git branch' and 'git checkout' to set up new branches
629 so that linkgit:git-pull[1] will appropriately merge from the
630 starting point branch. Note that even if this option is not set,
631 this behavior can be chosen per-branch using the `--track`
632 and `--no-track` options. The valid settings are: `false` -- no
633 automatic setup is done; `true` -- automatic setup is done when the
634 starting point is a remote-tracking branch; `always` --
635 automatic setup is done when the starting point is either a
636 local branch or remote-tracking
637 branch. This option defaults to true.
639 branch.autosetuprebase::
640 When a new branch is created with 'git branch' or 'git checkout'
641 that tracks another branch, this variable tells git to set
642 up pull to rebase instead of merge (see "branch.<name>.rebase").
643 When `never`, rebase is never automatically set to true.
644 When `local`, rebase is set to true for tracked branches of
645 other local branches.
646 When `remote`, rebase is set to true for tracked branches of
647 remote-tracking branches.
648 When `always`, rebase will be set to true for all tracking
650 See "branch.autosetupmerge" for details on how to set up a
651 branch to track another branch.
652 This option defaults to never.
654 branch.<name>.remote::
655 When in branch <name>, it tells 'git fetch' and 'git push' which
656 remote to fetch from/push to. It defaults to `origin` if no remote is
657 configured. `origin` is also used if you are not on any branch.
659 branch.<name>.merge::
660 Defines, together with branch.<name>.remote, the upstream branch
661 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which
662 branch to merge and can also affect 'git push' (see push.default).
663 When in branch <name>, it tells 'git fetch' the default
664 refspec to be marked for merging in FETCH_HEAD. The value is
665 handled like the remote part of a refspec, and must match a
666 ref which is fetched from the remote given by
667 "branch.<name>.remote".
668 The merge information is used by 'git pull' (which at first calls
669 'git fetch') to lookup the default branch for merging. Without
670 this option, 'git pull' defaults to merge the first refspec fetched.
671 Specify multiple values to get an octopus merge.
672 If you wish to setup 'git pull' so that it merges into <name> from
673 another branch in the local repository, you can point
674 branch.<name>.merge to the desired branch, and use the special setting
675 `.` (a period) for branch.<name>.remote.
677 branch.<name>.mergeoptions::
678 Sets default options for merging into branch <name>. The syntax and
679 supported options are the same as those of linkgit:git-merge[1], but
680 option values containing whitespace characters are currently not
683 branch.<name>.rebase::
684 When true, rebase the branch <name> on top of the fetched branch,
685 instead of merging the default branch from the default remote when
686 "git pull" is run. See "pull.rebase" for doing this in a non
687 branch-specific manner.
689 *NOTE*: this is a possibly dangerous operation; do *not* use
690 it unless you understand the implications (see linkgit:git-rebase[1]
694 Specify the command to invoke the specified browser. The
695 specified command is evaluated in shell with the URLs passed
696 as arguments. (See linkgit:git-web{litdd}browse[1].)
698 browser.<tool>.path::
699 Override the path for the given tool that may be used to
700 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
701 working repository in gitweb (see linkgit:git-instaweb[1]).
704 A boolean to make git-clean do nothing unless given -f
705 or -n. Defaults to true.
708 A boolean to enable/disable color in the output of
709 linkgit:git-branch[1]. May be set to `always`,
710 `false` (or `never`) or `auto` (or `true`), in which case colors are used
711 only when the output is to a terminal. Defaults to false.
713 color.branch.<slot>::
714 Use customized color for branch coloration. `<slot>` is one of
715 `current` (the current branch), `local` (a local branch),
716 `remote` (a remote-tracking branch in refs/remotes/), `plain` (other
719 The value for these configuration variables is a list of colors (at most
720 two) and attributes (at most one), separated by spaces. The colors
721 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
722 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
723 `blink` and `reverse`. The first color given is the foreground; the
724 second is the background. The position of the attribute, if any,
728 Whether to use ANSI escape sequences to add color to patches.
729 If this is set to `always`, linkgit:git-diff[1],
730 linkgit:git-log[1], and linkgit:git-show[1] will use color
731 for all patches. If it is set to `true` or `auto`, those
732 commands will only use color when output is to the terminal.
735 This does not affect linkgit:git-format-patch[1] nor the
736 'git-diff-{asterisk}' plumbing commands. Can be overridden on the
737 command line with the `--color[=<when>]` option.
740 Use customized color for diff colorization. `<slot>` specifies
741 which part of the patch to use the specified color, and is one
742 of `plain` (context text), `meta` (metainformation), `frag`
743 (hunk header), 'func' (function in hunk header), `old` (removed lines),
744 `new` (added lines), `commit` (commit headers), or `whitespace`
745 (highlighting whitespace errors). The values of these variables may be
746 specified as in color.branch.<slot>.
748 color.decorate.<slot>::
749 Use customized color for 'git log --decorate' output. `<slot>` is one
750 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
751 branches, remote-tracking branches, tags, stash and HEAD, respectively.
754 When set to `always`, always highlight matches. When `false` (or
755 `never`), never. When set to `true` or `auto`, use color only
756 when the output is written to the terminal. Defaults to `false`.
759 Use customized color for grep colorization. `<slot>` specifies which
760 part of the line to use the specified color, and is one of
764 non-matching text in context lines (when using `-A`, `-B`, or `-C`)
766 filename prefix (when not using `-h`)
768 function name lines (when using `-p`)
770 line number prefix (when using `-n`)
774 non-matching text in selected lines
776 separators between fields on a line (`:`, `-`, and `=`)
777 and between hunks (`--`)
780 The values of these variables may be specified as in color.branch.<slot>.
783 When set to `always`, always use colors for interactive prompts
784 and displays (such as those used by "git-add --interactive").
785 When false (or `never`), never. When set to `true` or `auto`, use
786 colors only when the output is to the terminal. Defaults to false.
788 color.interactive.<slot>::
789 Use customized color for 'git add --interactive'
790 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
791 four distinct types of normal output from interactive
792 commands. The values of these variables may be specified as
793 in color.branch.<slot>.
796 A boolean to enable/disable colored output when the pager is in
797 use (default is true).
800 A boolean to enable/disable color in the output of
801 linkgit:git-show-branch[1]. May be set to `always`,
802 `false` (or `never`) or `auto` (or `true`), in which case colors are used
803 only when the output is to a terminal. Defaults to false.
806 A boolean to enable/disable color in the output of
807 linkgit:git-status[1]. May be set to `always`,
808 `false` (or `never`) or `auto` (or `true`), in which case colors are used
809 only when the output is to a terminal. Defaults to false.
811 color.status.<slot>::
812 Use customized color for status colorization. `<slot>` is
813 one of `header` (the header text of the status message),
814 `added` or `updated` (files which are added but not committed),
815 `changed` (files which are changed but not added in the index),
816 `untracked` (files which are not tracked by git),
817 `branch` (the current branch), or
818 `nobranch` (the color the 'no branch' warning is shown in, defaulting
819 to red). The values of these variables may be specified as in
823 This variable determines the default value for variables such
824 as `color.diff` and `color.grep` that control the use of color
825 per command family. Its scope will expand as more commands learn
826 configuration to set a default for the `--color` option. Set it
827 to `always` if you want all output not intended for machine
828 consumption to use color, to `true` or `auto` if you want such
829 output to use color when written to the terminal, or to `false` or
830 `never` if you prefer git commands not to use color unless enabled
831 explicitly with some other configuration or the `--color` option.
834 A boolean to enable/disable inclusion of status information in the
835 commit message template when using an editor to prepare the commit
836 message. Defaults to true.
839 Specify a file to use as the template for new commit messages.
840 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the
841 specified user's home directory.
843 include::diff-config.txt[]
845 difftool.<tool>.path::
846 Override the path for the given tool. This is useful in case
847 your tool is not in the PATH.
849 difftool.<tool>.cmd::
850 Specify the command to invoke the specified diff tool.
851 The specified command is evaluated in shell with the following
852 variables available: 'LOCAL' is set to the name of the temporary
853 file containing the contents of the diff pre-image and 'REMOTE'
854 is set to the name of the temporary file containing the contents
855 of the diff post-image.
858 Prompt before each invocation of the diff tool.
861 A POSIX Extended Regular Expression used to determine what is a "word"
862 when performing word-by-word difference calculations. Character
863 sequences that match the regular expression are "words", all other
864 characters are *ignorable* whitespace.
866 fetch.recurseSubmodules::
867 This option can be either set to a boolean value or to 'on-demand'.
868 Setting it to a boolean changes the behavior of fetch and pull to
869 unconditionally recurse into submodules when set to true or to not
870 recurse at all when set to false. When set to 'on-demand' (the default
871 value), fetch and pull will only recurse into a populated submodule
872 when its superproject retrieves a commit that updates the submodule's
876 If it is set to true, git-fetch-pack will check all fetched
877 objects. It will abort in the case of a malformed object or a
878 broken link. The result of an abort are only dangling objects.
879 Defaults to false. If not set, the value of `transfer.fsckObjects`
883 If the number of objects fetched over the git native
884 transfer is below this
885 limit, then the objects will be unpacked into loose object
886 files. However if the number of received objects equals or
887 exceeds this limit then the received pack will be stored as
888 a pack, after adding any missing delta bases. Storing the
889 pack from a push can make the push operation complete faster,
890 especially on slow filesystems. If not set, the value of
891 `transfer.unpackLimit` is used instead.
894 Enable multipart/mixed attachments as the default for
895 'format-patch'. The value can also be a double quoted string
896 which will enable attachments as the default and set the
897 value as the boundary. See the --attach option in
898 linkgit:git-format-patch[1].
901 A boolean which can enable or disable sequence numbers in patch
902 subjects. It defaults to "auto" which enables it only if there
903 is more than one patch. It can be enabled or disabled for all
904 messages by setting it to "true" or "false". See --numbered
905 option in linkgit:git-format-patch[1].
908 Additional email headers to include in a patch to be submitted
909 by mail. See linkgit:git-format-patch[1].
913 Additional recipients to include in a patch to be submitted
914 by mail. See the --to and --cc options in
915 linkgit:git-format-patch[1].
917 format.subjectprefix::
918 The default for format-patch is to output files with the '[PATCH]'
919 subject prefix. Use this variable to change that prefix.
922 The default for format-patch is to output a signature containing
923 the git version number. Use this variable to change that default.
924 Set this variable to the empty string ("") to suppress
925 signature generation.
928 The default for format-patch is to output files with the suffix
929 `.patch`. Use this variable to change that suffix (make sure to
930 include the dot if you want it).
933 The default pretty format for log/show/whatchanged command,
934 See linkgit:git-log[1], linkgit:git-show[1],
935 linkgit:git-whatchanged[1].
938 The default threading style for 'git format-patch'. Can be
939 a boolean value, or `shallow` or `deep`. `shallow` threading
940 makes every mail a reply to the head of the series,
941 where the head is chosen from the cover letter, the
942 `\--in-reply-to`, and the first patch mail, in this order.
943 `deep` threading makes every mail a reply to the previous one.
944 A true boolean value is the same as `shallow`, and a false
945 value disables threading.
948 A boolean value which lets you enable the `-s/--signoff` option of
949 format-patch by default. *Note:* Adding the Signed-off-by: line to a
950 patch should be a conscious act and means that you certify you have
951 the rights to submit this work under the same open source license.
952 Please see the 'SubmittingPatches' document for further discussion.
954 filter.<driver>.clean::
955 The command which is used to convert the content of a worktree
956 file to a blob upon checkin. See linkgit:gitattributes[5] for
959 filter.<driver>.smudge::
960 The command which is used to convert the content of a blob
961 object to a worktree file upon checkout. See
962 linkgit:gitattributes[5] for details.
964 gc.aggressiveWindow::
965 The window size parameter used in the delta compression
966 algorithm used by 'git gc --aggressive'. This defaults
970 When there are approximately more than this many loose
971 objects in the repository, `git gc --auto` will pack them.
972 Some Porcelain commands use this command to perform a
973 light-weight garbage collection from time to time. The
974 default value is 6700. Setting this to 0 disables it.
977 When there are more than this many packs that are not
978 marked with `*.keep` file in the repository, `git gc
979 --auto` consolidates them into one larger pack. The
980 default value is 50. Setting this to 0 disables it.
983 Running `git pack-refs` in a repository renders it
984 unclonable by Git versions prior to 1.5.1.2 over dumb
985 transports such as HTTP. This variable determines whether
986 'git gc' runs `git pack-refs`. This can be set to `notbare`
987 to enable it within all non-bare repos or it can be set to a
988 boolean value. The default is `true`.
991 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
992 Override the grace period with this config variable. The value
993 "now" may be used to disable this grace period and always prune
994 unreachable objects immediately.
997 gc.<pattern>.reflogexpire::
998 'git reflog expire' removes reflog entries older than
999 this time; defaults to 90 days. With "<pattern>" (e.g.
1000 "refs/stash") in the middle the setting applies only to
1001 the refs that match the <pattern>.
1003 gc.reflogexpireunreachable::
1004 gc.<ref>.reflogexpireunreachable::
1005 'git reflog expire' removes reflog entries older than
1006 this time and are not reachable from the current tip;
1007 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")
1008 in the middle, the setting applies only to the refs that
1009 match the <pattern>.
1012 Records of conflicted merge you resolved earlier are
1013 kept for this many days when 'git rerere gc' is run.
1014 The default is 60 days. See linkgit:git-rerere[1].
1016 gc.rerereunresolved::
1017 Records of conflicted merge you have not resolved are
1018 kept for this many days when 'git rerere gc' is run.
1019 The default is 15 days. See linkgit:git-rerere[1].
1021 gitcvs.commitmsgannotation::
1022 Append this string to each commit message. Set to empty string
1023 to disable this feature. Defaults to "via git-CVS emulator".
1026 Whether the CVS server interface is enabled for this repository.
1027 See linkgit:git-cvsserver[1].
1030 Path to a log file where the CVS server interface well... logs
1031 various stuff. See linkgit:git-cvsserver[1].
1033 gitcvs.usecrlfattr::
1034 If true, the server will look up the end-of-line conversion
1035 attributes for files to determine the '-k' modes to use. If
1036 the attributes force git to treat a file as text,
1037 the '-k' mode will be left blank so CVS clients will
1038 treat it as text. If they suppress text conversion, the file
1039 will be set with '-kb' mode, which suppresses any newline munging
1040 the client might otherwise do. If the attributes do not allow
1041 the file type to be determined, then 'gitcvs.allbinary' is
1042 used. See linkgit:gitattributes[5].
1045 This is used if 'gitcvs.usecrlfattr' does not resolve
1046 the correct '-kb' mode to use. If true, all
1047 unresolved files are sent to the client in
1048 mode '-kb'. This causes the client to treat them
1049 as binary files, which suppresses any newline munging it
1050 otherwise might do. Alternatively, if it is set to "guess",
1051 then the contents of the file are examined to decide if
1052 it is binary, similar to 'core.autocrlf'.
1055 Database used by git-cvsserver to cache revision information
1056 derived from the git repository. The exact meaning depends on the
1057 used database driver, for SQLite (which is the default driver) this
1058 is a filename. Supports variable substitution (see
1059 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1060 Default: '%Ggitcvs.%m.sqlite'
1063 Used Perl DBI driver. You can specify any available driver
1064 for this here, but it might not work. git-cvsserver is tested
1065 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1066 reported *not* to work with 'DBD::mysql'. Experimental feature.
1067 May not contain double colons (`:`). Default: 'SQLite'.
1068 See linkgit:git-cvsserver[1].
1070 gitcvs.dbuser, gitcvs.dbpass::
1071 Database user and password. Only useful if setting 'gitcvs.dbdriver',
1072 since SQLite has no concept of database users and/or passwords.
1073 'gitcvs.dbuser' supports variable substitution (see
1074 linkgit:git-cvsserver[1] for details).
1076 gitcvs.dbTableNamePrefix::
1077 Database table name prefix. Prepended to the names of any
1078 database tables used, allowing a single database to be used
1079 for several repositories. Supports variable substitution (see
1080 linkgit:git-cvsserver[1] for details). Any non-alphabetic
1081 characters will be replaced with underscores.
1083 All gitcvs variables except for 'gitcvs.usecrlfattr' and
1084 'gitcvs.allbinary' can also be specified as
1085 'gitcvs.<access_method>.<varname>' (where 'access_method'
1086 is one of "ext" and "pserver") to make them apply only for the given
1090 gitweb.description::
1093 See linkgit:gitweb[1] for description.
1101 gitweb.remote_heads::
1104 See linkgit:gitweb.conf[5] for description.
1107 If set to true, enable '-n' option by default.
1109 grep.extendedRegexp::
1110 If set to true, enable '--extended-regexp' option by default.
1112 gui.commitmsgwidth::
1113 Defines how wide the commit message window is in the
1114 linkgit:git-gui[1]. "75" is the default.
1117 Specifies how many context lines should be used in calls to diff
1118 made by the linkgit:git-gui[1]. The default is "5".
1121 Specifies the default encoding to use for displaying of
1122 file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1123 It can be overridden by setting the 'encoding' attribute
1124 for relevant files (see linkgit:gitattributes[5]).
1125 If this option is not set, the tools default to the
1128 gui.matchtrackingbranch::
1129 Determines if new branches created with linkgit:git-gui[1] should
1130 default to tracking remote branches with matching names or
1131 not. Default: "false".
1133 gui.newbranchtemplate::
1134 Is used as suggested name when creating new branches using the
1137 gui.pruneduringfetch::
1138 "true" if linkgit:git-gui[1] should prune remote-tracking branches when
1139 performing a fetch. The default value is "false".
1142 Determines if linkgit:git-gui[1] should trust the file modification
1143 timestamp or not. By default the timestamps are not trusted.
1145 gui.spellingdictionary::
1146 Specifies the dictionary used for spell checking commit messages in
1147 the linkgit:git-gui[1]. When set to "none" spell checking is turned
1151 If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1152 location detection. It makes blame significantly faster on huge
1153 repositories at the expense of less thorough copy detection.
1155 gui.copyblamethreshold::
1156 Specifies the threshold to use in 'git gui blame' original location
1157 detection, measured in alphanumeric characters. See the
1158 linkgit:git-blame[1] manual for more information on copy detection.
1160 gui.blamehistoryctx::
1161 Specifies the radius of history context in days to show in
1162 linkgit:gitk[1] for the selected commit, when the `Show History
1163 Context` menu item is invoked from 'git gui blame'. If this
1164 variable is set to zero, the whole history is shown.
1166 guitool.<name>.cmd::
1167 Specifies the shell command line to execute when the corresponding item
1168 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1169 mandatory for every tool. The command is executed from the root of
1170 the working directory, and in the environment it receives the name of
1171 the tool as 'GIT_GUITOOL', the name of the currently selected file as
1172 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1173 the head is detached, 'CUR_BRANCH' is empty).
1175 guitool.<name>.needsfile::
1176 Run the tool only if a diff is selected in the GUI. It guarantees
1177 that 'FILENAME' is not empty.
1179 guitool.<name>.noconsole::
1180 Run the command silently, without creating a window to display its
1183 guitool.<name>.norescan::
1184 Don't rescan the working directory for changes after the tool
1187 guitool.<name>.confirm::
1188 Show a confirmation dialog before actually running the tool.
1190 guitool.<name>.argprompt::
1191 Request a string argument from the user, and pass it to the tool
1192 through the 'ARGS' environment variable. Since requesting an
1193 argument implies confirmation, the 'confirm' option has no effect
1194 if this is enabled. If the option is set to 'true', 'yes', or '1',
1195 the dialog uses a built-in generic prompt; otherwise the exact
1196 value of the variable is used.
1198 guitool.<name>.revprompt::
1199 Request a single valid revision from the user, and set the
1200 'REVISION' environment variable. In other aspects this option
1201 is similar to 'argprompt', and can be used together with it.
1203 guitool.<name>.revunmerged::
1204 Show only unmerged branches in the 'revprompt' subdialog.
1205 This is useful for tools similar to merge or rebase, but not
1206 for things like checkout or reset.
1208 guitool.<name>.title::
1209 Specifies the title to use for the prompt dialog. The default
1212 guitool.<name>.prompt::
1213 Specifies the general prompt string to display at the top of
1214 the dialog, before subsections for 'argprompt' and 'revprompt'.
1215 The default value includes the actual command.
1218 Specify the browser that will be used to display help in the
1219 'web' format. See linkgit:git-help[1].
1222 Override the default help format used by linkgit:git-help[1].
1223 Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1224 the default. 'web' and 'html' are the same.
1227 Automatically correct and execute mistyped commands after
1228 waiting for the given number of deciseconds (0.1 sec). If more
1229 than one command can be deduced from the entered text, nothing
1230 will be executed. If the value of this option is negative,
1231 the corrected command will be executed immediately. If the
1232 value is 0 - the command will be just shown but not executed.
1233 This is the default.
1236 Override the HTTP proxy, normally configured using the 'http_proxy'
1237 environment variable (see linkgit:curl[1]). This can be overridden
1238 on a per-remote basis; see remote.<name>.proxy
1241 File containing previously stored cookie lines which should be used
1242 in the git http session, if they match the server. The file format
1243 of the file to read cookies from should be plain HTTP headers or
1244 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
1245 NOTE that the file specified with http.cookiefile is only used as
1246 input. No cookies will be stored in the file.
1249 Whether to verify the SSL certificate when fetching or pushing
1250 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1254 File containing the SSL certificate when fetching or pushing
1255 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1259 File containing the SSL private key when fetching or pushing
1260 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1263 http.sslCertPasswordProtected::
1264 Enable git's password prompt for the SSL certificate. Otherwise
1265 OpenSSL will prompt the user, possibly many times, if the
1266 certificate or private key is encrypted. Can be overridden by the
1267 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1270 File containing the certificates to verify the peer with when
1271 fetching or pushing over HTTPS. Can be overridden by the
1272 'GIT_SSL_CAINFO' environment variable.
1275 Path containing files with the CA certificates to verify the peer
1276 with when fetching or pushing over HTTPS. Can be overridden
1277 by the 'GIT_SSL_CAPATH' environment variable.
1280 How many HTTP requests to launch in parallel. Can be overridden
1281 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1284 The number of curl sessions (counted across slots) to be kept across
1285 requests. They will not be ended with curl_easy_cleanup() until
1286 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1287 value will be capped at 1. Defaults to 1.
1290 Maximum size in bytes of the buffer used by smart HTTP
1291 transports when POSTing data to the remote system.
1292 For requests larger than this buffer size, HTTP/1.1 and
1293 Transfer-Encoding: chunked is used to avoid creating a
1294 massive pack file locally. Default is 1 MiB, which is
1295 sufficient for most requests.
1297 http.lowSpeedLimit, http.lowSpeedTime::
1298 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1299 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1300 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1301 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1304 A boolean which disables using of EPSV ftp command by curl.
1305 This can helpful with some "poor" ftp servers which don't
1306 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1307 environment variable. Default is false (curl will use EPSV).
1310 The HTTP USER_AGENT string presented to an HTTP server. The default
1311 value represents the version of the client git such as git/1.7.1.
1312 This option allows you to override this value to a more common value
1313 such as Mozilla/4.0. This may be necessary, for instance, if
1314 connecting through a firewall that restricts HTTP connections to a set
1315 of common USER_AGENT strings (but not including those like git/1.7.1).
1316 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1318 i18n.commitEncoding::
1319 Character encoding the commit messages are stored in; git itself
1320 does not care per se, but this information is necessary e.g. when
1321 importing commits from emails or in the gitk graphical history
1322 browser (and possibly at other places in the future or in other
1323 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1325 i18n.logOutputEncoding::
1326 Character encoding the commit messages are converted to when
1327 running 'git log' and friends.
1330 The configuration variables in the 'imap' section are described
1331 in linkgit:git-imap-send[1].
1334 Specify the directory from which templates will be copied.
1335 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1338 Specify the program that will be used to browse your working
1339 repository in gitweb. See linkgit:git-instaweb[1].
1342 The HTTP daemon command-line to start gitweb on your working
1343 repository. See linkgit:git-instaweb[1].
1346 If true the web server started by linkgit:git-instaweb[1] will
1347 be bound to the local IP (127.0.0.1).
1349 instaweb.modulepath::
1350 The default module path for linkgit:git-instaweb[1] to use
1351 instead of /usr/lib/apache2/modules. Only used if httpd
1355 The port number to bind the gitweb httpd to. See
1356 linkgit:git-instaweb[1].
1358 interactive.singlekey::
1359 In interactive commands, allow the user to provide one-letter
1360 input with a single key (i.e., without hitting enter).
1361 Currently this is used by the `\--patch` mode of
1362 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],
1363 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this
1364 setting is silently ignored if portable keystroke input
1368 If true, makes linkgit:git-log[1], linkgit:git-show[1], and
1369 linkgit:git-whatchanged[1] assume `\--abbrev-commit`. You may
1370 override this option with `\--no-abbrev-commit`.
1373 Set the default date-time mode for the 'log' command.
1374 Setting a value for log.date is similar to using 'git log''s
1375 `\--date` option. Possible values are `relative`, `local`,
1376 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1380 Print out the ref names of any commits that are shown by the log
1381 command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1382 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1383 specified, the full ref name (including prefix) will be printed.
1384 This is the same as the log commands '--decorate' option.
1387 If true, the initial commit will be shown as a big creation event.
1388 This is equivalent to a diff against an empty tree.
1389 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1390 normally hide the root commit will now show it. True by default.
1393 The location of an augmenting mailmap file. The default
1394 mailmap, located in the root of the repository, is loaded
1395 first, then the mailmap file pointed to by this variable.
1396 The location of the mailmap file may be in a repository
1397 subdirectory, or somewhere outside of the repository itself.
1398 See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1401 Specify the programs that may be used to display help in the
1402 'man' format. See linkgit:git-help[1].
1405 Specify the command to invoke the specified man viewer. The
1406 specified command is evaluated in shell with the man page
1407 passed as argument. (See linkgit:git-help[1].)
1410 Override the path for the given tool that may be used to
1411 display help in the 'man' format. See linkgit:git-help[1].
1413 include::merge-config.txt[]
1415 mergetool.<tool>.path::
1416 Override the path for the given tool. This is useful in case
1417 your tool is not in the PATH.
1419 mergetool.<tool>.cmd::
1420 Specify the command to invoke the specified merge tool. The
1421 specified command is evaluated in shell with the following
1422 variables available: 'BASE' is the name of a temporary file
1423 containing the common base of the files to be merged, if available;
1424 'LOCAL' is the name of a temporary file containing the contents of
1425 the file on the current branch; 'REMOTE' is the name of a temporary
1426 file containing the contents of the file from the branch being
1427 merged; 'MERGED' contains the name of the file to which the merge
1428 tool should write the results of a successful merge.
1430 mergetool.<tool>.trustExitCode::
1431 For a custom merge command, specify whether the exit code of
1432 the merge command can be used to determine whether the merge was
1433 successful. If this is not set to true then the merge target file
1434 timestamp is checked and the merge assumed to have been successful
1435 if the file has been updated, otherwise the user is prompted to
1436 indicate the success of the merge.
1438 mergetool.keepBackup::
1439 After performing a merge, the original file with conflict markers
1440 can be saved as a file with a `.orig` extension. If this variable
1441 is set to `false` then this file is not preserved. Defaults to
1442 `true` (i.e. keep the backup files).
1444 mergetool.keepTemporaries::
1445 When invoking a custom merge tool, git uses a set of temporary
1446 files to pass to the tool. If the tool returns an error and this
1447 variable is set to `true`, then these temporary files will be
1448 preserved, otherwise they will be removed after the tool has
1449 exited. Defaults to `false`.
1452 Prompt before each invocation of the merge resolution program.
1455 The (fully qualified) refname from which to show notes when
1456 showing commit messages. The value of this variable can be set
1457 to a glob, in which case notes from all matching refs will be
1458 shown. You may also specify this configuration variable
1459 several times. A warning will be issued for refs that do not
1460 exist, but a glob that does not match any refs is silently
1463 This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1464 environment variable, which must be a colon separated list of refs or
1467 The effective value of "core.notesRef" (possibly overridden by
1468 GIT_NOTES_REF) is also implicitly added to the list of refs to be
1471 notes.rewrite.<command>::
1472 When rewriting commits with <command> (currently `amend` or
1473 `rebase`) and this variable is set to `true`, git
1474 automatically copies your notes from the original to the
1475 rewritten commit. Defaults to `true`, but see
1476 "notes.rewriteRef" below.
1479 When copying notes during a rewrite (see the
1480 "notes.rewrite.<command>" option), determines what to do if
1481 the target commit already has a note. Must be one of
1482 `overwrite`, `concatenate`, or `ignore`. Defaults to
1485 This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1486 environment variable.
1489 When copying notes during a rewrite, specifies the (fully
1490 qualified) ref whose notes should be copied. The ref may be a
1491 glob, in which case notes in all matching refs will be copied.
1492 You may also specify this configuration several times.
1494 Does not have a default value; you must configure this variable to
1495 enable note rewriting. Set it to `refs/notes/commits` to enable
1496 rewriting for the default commit notes.
1498 This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1499 environment variable, which must be a colon separated list of refs or
1503 The size of the window used by linkgit:git-pack-objects[1] when no
1504 window size is given on the command line. Defaults to 10.
1507 The maximum delta depth used by linkgit:git-pack-objects[1] when no
1508 maximum depth is given on the command line. Defaults to 50.
1511 The window memory size limit used by linkgit:git-pack-objects[1]
1512 when no limit is given on the command line. The value can be
1513 suffixed with "k", "m", or "g". Defaults to 0, meaning no
1517 An integer -1..9, indicating the compression level for objects
1518 in a pack file. -1 is the zlib default. 0 means no
1519 compression, and 1..9 are various speed/size tradeoffs, 9 being
1520 slowest. If not set, defaults to core.compression. If that is
1521 not set, defaults to -1, the zlib default, which is "a default
1522 compromise between speed and compression (currently equivalent
1525 Note that changing the compression level will not automatically recompress
1526 all existing objects. You can force recompression by passing the -F option
1527 to linkgit:git-repack[1].
1529 pack.deltaCacheSize::
1530 The maximum memory in bytes used for caching deltas in
1531 linkgit:git-pack-objects[1] before writing them out to a pack.
1532 This cache is used to speed up the writing object phase by not
1533 having to recompute the final delta result once the best match
1534 for all objects is found. Repacking large repositories on machines
1535 which are tight with memory might be badly impacted by this though,
1536 especially if this cache pushes the system into swapping.
1537 A value of 0 means no limit. The smallest size of 1 byte may be
1538 used to virtually disable this cache. Defaults to 256 MiB.
1540 pack.deltaCacheLimit::
1541 The maximum size of a delta, that is cached in
1542 linkgit:git-pack-objects[1]. This cache is used to speed up the
1543 writing object phase by not having to recompute the final delta
1544 result once the best match for all objects is found. Defaults to 1000.
1547 Specifies the number of threads to spawn when searching for best
1548 delta matches. This requires that linkgit:git-pack-objects[1]
1549 be compiled with pthreads otherwise this option is ignored with a
1550 warning. This is meant to reduce packing time on multiprocessor
1551 machines. The required amount of memory for the delta search window
1552 is however multiplied by the number of threads.
1553 Specifying 0 will cause git to auto-detect the number of CPU's
1554 and set the number of threads accordingly.
1557 Specify the default pack index version. Valid values are 1 for
1558 legacy pack index used by Git versions prior to 1.5.2, and 2 for
1559 the new pack index with capabilities for packs larger than 4 GB
1560 as well as proper protection against the repacking of corrupted
1561 packs. Version 2 is the default. Note that version 2 is enforced
1562 and this config option ignored whenever the corresponding pack is
1565 If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1566 cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1567 that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1568 other side may give you a repository that cannot be accessed with your
1569 older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1570 you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1571 the `{asterisk}.idx` file.
1573 pack.packSizeLimit::
1574 The maximum size of a pack. This setting only affects
1575 packing to a file when repacking, i.e. the git:// protocol
1576 is unaffected. It can be overridden by the `\--max-pack-size`
1577 option of linkgit:git-repack[1]. The minimum size allowed is
1578 limited to 1 MiB. The default is unlimited.
1579 Common unit suffixes of 'k', 'm', or 'g' are
1583 If the value is boolean, turns on or off pagination of the
1584 output of a particular git subcommand when writing to a tty.
1585 Otherwise, turns on pagination for the subcommand using the
1586 pager specified by the value of `pager.<cmd>`. If `\--paginate`
1587 or `\--no-pager` is specified on the command line, it takes
1588 precedence over this option. To disable pagination for all
1589 commands, set `core.pager` or `GIT_PAGER` to `cat`.
1592 Alias for a --pretty= format string, as specified in
1593 linkgit:git-log[1]. Any aliases defined here can be used just
1594 as the built-in pretty formats could. For example,
1595 running `git config pretty.changelog "format:{asterisk} %H %s"`
1596 would cause the invocation `git log --pretty=changelog`
1597 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.
1598 Note that an alias with the same name as a built-in format
1599 will be silently ignored.
1602 When true, rebase branches on top of the fetched branch, instead
1603 of merging the default branch from the default remote when "git
1604 pull" is run. See "branch.<name>.rebase" for setting this on a
1607 *NOTE*: this is a possibly dangerous operation; do *not* use
1608 it unless you understand the implications (see linkgit:git-rebase[1]
1612 The default merge strategy to use when pulling multiple branches
1616 The default merge strategy to use when pulling a single branch.
1619 Defines the action git push should take if no refspec is given
1620 on the command line, no refspec is configured in the remote, and
1621 no refspec is implied by any of the options given on the command
1622 line. Possible values are:
1624 * `nothing` - do not push anything.
1625 * `matching` - push all matching branches.
1626 All branches having the same name in both ends are considered to be
1627 matching. This is the default.
1628 * `upstream` - push the current branch to its upstream branch.
1629 * `tracking` - deprecated synonym for `upstream`.
1630 * `current` - push the current branch to a branch of the same name.
1633 Whether to show a diffstat of what changed upstream since the last
1634 rebase. False by default.
1637 If set to true enable '--autosquash' option by default.
1640 By default, git-receive-pack will run "git-gc --auto" after
1641 receiving data from git-push and updating refs. You can stop
1642 it by setting this variable to false.
1644 receive.fsckObjects::
1645 If it is set to true, git-receive-pack will check all received
1646 objects. It will abort in the case of a malformed object or a
1647 broken link. The result of an abort are only dangling objects.
1648 Defaults to false. If not set, the value of `transfer.fsckObjects`
1651 receive.unpackLimit::
1652 If the number of objects received in a push is below this
1653 limit then the objects will be unpacked into loose object
1654 files. However if the number of received objects equals or
1655 exceeds this limit then the received pack will be stored as
1656 a pack, after adding any missing delta bases. Storing the
1657 pack from a push can make the push operation complete faster,
1658 especially on slow filesystems. If not set, the value of
1659 `transfer.unpackLimit` is used instead.
1661 receive.denyDeletes::
1662 If set to true, git-receive-pack will deny a ref update that deletes
1663 the ref. Use this to prevent such a ref deletion via a push.
1665 receive.denyDeleteCurrent::
1666 If set to true, git-receive-pack will deny a ref update that
1667 deletes the currently checked out branch of a non-bare repository.
1669 receive.denyCurrentBranch::
1670 If set to true or "refuse", git-receive-pack will deny a ref update
1671 to the currently checked out branch of a non-bare repository.
1672 Such a push is potentially dangerous because it brings the HEAD
1673 out of sync with the index and working tree. If set to "warn",
1674 print a warning of such a push to stderr, but allow the push to
1675 proceed. If set to false or "ignore", allow such pushes with no
1676 message. Defaults to "refuse".
1678 receive.denyNonFastForwards::
1679 If set to true, git-receive-pack will deny a ref update which is
1680 not a fast-forward. Use this to prevent such an update via a push,
1681 even if that push is forced. This configuration variable is
1682 set when initializing a shared repository.
1684 receive.updateserverinfo::
1685 If set to true, git-receive-pack will run git-update-server-info
1686 after receiving data from git-push and updating refs.
1689 The URL of a remote repository. See linkgit:git-fetch[1] or
1690 linkgit:git-push[1].
1692 remote.<name>.pushurl::
1693 The push URL of a remote repository. See linkgit:git-push[1].
1695 remote.<name>.proxy::
1696 For remotes that require curl (http, https and ftp), the URL to
1697 the proxy to use for that remote. Set to the empty string to
1698 disable proxying for that remote.
1700 remote.<name>.fetch::
1701 The default set of "refspec" for linkgit:git-fetch[1]. See
1702 linkgit:git-fetch[1].
1704 remote.<name>.push::
1705 The default set of "refspec" for linkgit:git-push[1]. See
1706 linkgit:git-push[1].
1708 remote.<name>.mirror::
1709 If true, pushing to this remote will automatically behave
1710 as if the `\--mirror` option was given on the command line.
1712 remote.<name>.skipDefaultUpdate::
1713 If true, this remote will be skipped by default when updating
1714 using linkgit:git-fetch[1] or the `update` subcommand of
1715 linkgit:git-remote[1].
1717 remote.<name>.skipFetchAll::
1718 If true, this remote will be skipped by default when updating
1719 using linkgit:git-fetch[1] or the `update` subcommand of
1720 linkgit:git-remote[1].
1722 remote.<name>.receivepack::
1723 The default program to execute on the remote side when pushing. See
1724 option \--receive-pack of linkgit:git-push[1].
1726 remote.<name>.uploadpack::
1727 The default program to execute on the remote side when fetching. See
1728 option \--upload-pack of linkgit:git-fetch-pack[1].
1730 remote.<name>.tagopt::
1731 Setting this value to \--no-tags disables automatic tag following when
1732 fetching from remote <name>. Setting it to \--tags will fetch every
1733 tag from remote <name>, even if they are not reachable from remote
1734 branch heads. Passing these flags directly to linkgit:git-fetch[1] can
1735 override this setting. See options \--tags and \--no-tags of
1736 linkgit:git-fetch[1].
1739 Setting this to a value <vcs> will cause git to interact with
1740 the remote with the git-remote-<vcs> helper.
1743 The list of remotes which are fetched by "git remote update
1744 <group>". See linkgit:git-remote[1].
1746 repack.usedeltabaseoffset::
1747 By default, linkgit:git-repack[1] creates packs that use
1748 delta-base offset. If you need to share your repository with
1749 git older than version 1.4.4, either directly or via a dumb
1750 protocol such as http, then you need to set this option to
1751 "false" and repack. Access from old git versions over the
1752 native protocol are unaffected by this option.
1755 When set to true, `git-rerere` updates the index with the
1756 resulting contents after it cleanly resolves conflicts using
1757 previously recorded resolution. Defaults to false.
1760 Activate recording of resolved conflicts, so that identical
1761 conflict hunks can be resolved automatically, should they
1762 be encountered again. linkgit:git-rerere[1] command is by
1763 default enabled if you create `rr-cache` directory under
1764 `$GIT_DIR`, but can be disabled by setting this option to false.
1766 sendemail.identity::
1767 A configuration identity. When given, causes values in the
1768 'sendemail.<identity>' subsection to take precedence over
1769 values in the 'sendemail' section. The default identity is
1770 the value of 'sendemail.identity'.
1772 sendemail.smtpencryption::
1773 See linkgit:git-send-email[1] for description. Note that this
1774 setting is not subject to the 'identity' mechanism.
1777 Deprecated alias for 'sendemail.smtpencryption = ssl'.
1779 sendemail.<identity>.*::
1780 Identity-specific versions of the 'sendemail.*' parameters
1781 found below, taking precedence over those when the this
1782 identity is selected, through command-line or
1783 'sendemail.identity'.
1785 sendemail.aliasesfile::
1786 sendemail.aliasfiletype::
1790 sendemail.chainreplyto::
1792 sendemail.envelopesender::
1794 sendemail.multiedit::
1795 sendemail.signedoffbycc::
1796 sendemail.smtppass::
1797 sendemail.suppresscc::
1798 sendemail.suppressfrom::
1800 sendemail.smtpdomain::
1801 sendemail.smtpserver::
1802 sendemail.smtpserverport::
1803 sendemail.smtpserveroption::
1804 sendemail.smtpuser::
1806 sendemail.validate::
1807 See linkgit:git-send-email[1] for description.
1809 sendemail.signedoffcc::
1810 Deprecated alias for 'sendemail.signedoffbycc'.
1812 showbranch.default::
1813 The default set of branches for linkgit:git-show-branch[1].
1814 See linkgit:git-show-branch[1].
1816 status.relativePaths::
1817 By default, linkgit:git-status[1] shows paths relative to the
1818 current directory. Setting this variable to `false` shows paths
1819 relative to the repository root (this was the default for git
1822 status.showUntrackedFiles::
1823 By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1824 files which are not currently tracked by Git. Directories which
1825 contain only untracked files, are shown with the directory name
1826 only. Showing untracked files means that Git needs to lstat() all
1827 all the files in the whole repository, which might be slow on some
1828 systems. So, this variable controls how the commands displays
1829 the untracked files. Possible values are:
1832 * `no` - Show no untracked files.
1833 * `normal` - Show untracked files and directories.
1834 * `all` - Show also individual files in untracked directories.
1837 If this variable is not specified, it defaults to 'normal'.
1838 This variable can be overridden with the -u|--untracked-files option
1839 of linkgit:git-status[1] and linkgit:git-commit[1].
1841 status.submodulesummary::
1843 If this is set to a non zero number or true (identical to -1 or an
1844 unlimited number), the submodule summary will be enabled and a
1845 summary of commits for modified submodules will be shown (see
1846 --summary-limit option of linkgit:git-submodule[1]).
1848 submodule.<name>.path::
1849 submodule.<name>.url::
1850 submodule.<name>.update::
1851 The path within this project, URL, and the updating strategy
1852 for a submodule. These variables are initially populated
1853 by 'git submodule init'; edit them to override the
1854 URL and other values found in the `.gitmodules` file. See
1855 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
1857 submodule.<name>.fetchRecurseSubmodules::
1858 This option can be used to control recursive fetching of this
1859 submodule. It can be overridden by using the --[no-]recurse-submodules
1860 command line option to "git fetch" and "git pull".
1861 This setting will override that from in the linkgit:gitmodules[5]
1864 submodule.<name>.ignore::
1865 Defines under what circumstances "git status" and the diff family show
1866 a submodule as modified. When set to "all", it will never be considered
1867 modified, "dirty" will ignore all changes to the submodules work tree and
1868 takes only differences between the HEAD of the submodule and the commit
1869 recorded in the superproject into account. "untracked" will additionally
1870 let submodules with modified tracked files in their work tree show up.
1871 Using "none" (the default when this option is not set) also shows
1872 submodules that have untracked files in their work tree as changed.
1873 This setting overrides any setting made in .gitmodules for this submodule,
1874 both settings can be overridden on the command line by using the
1875 "--ignore-submodules" option.
1878 This variable can be used to restrict the permission bits of
1879 tar archive entries. The default is 0002, which turns off the
1880 world write bit. The special value "user" indicates that the
1881 archiving user's umask will be used instead. See umask(2) and
1882 linkgit:git-archive[1].
1884 transfer.fsckObjects::
1885 When `fetch.fsckObjects` or `receive.fsckObjects` are
1886 not set, the value of this variable is used instead.
1889 transfer.unpackLimit::
1890 When `fetch.unpackLimit` or `receive.unpackLimit` are
1891 not set, the value of this variable is used instead.
1892 The default value is 100.
1894 url.<base>.insteadOf::
1895 Any URL that starts with this value will be rewritten to
1896 start, instead, with <base>. In cases where some site serves a
1897 large number of repositories, and serves them with multiple
1898 access methods, and some users need to use different access
1899 methods, this feature allows people to specify any of the
1900 equivalent URLs and have git automatically rewrite the URL to
1901 the best alternative for the particular user, even for a
1902 never-before-seen repository on the site. When more than one
1903 insteadOf strings match a given URL, the longest match is used.
1905 url.<base>.pushInsteadOf::
1906 Any URL that starts with this value will not be pushed to;
1907 instead, it will be rewritten to start with <base>, and the
1908 resulting URL will be pushed to. In cases where some site serves
1909 a large number of repositories, and serves them with multiple
1910 access methods, some of which do not allow push, this feature
1911 allows people to specify a pull-only URL and have git
1912 automatically use an appropriate URL to push, even for a
1913 never-before-seen repository on the site. When more than one
1914 pushInsteadOf strings match a given URL, the longest match is
1915 used. If a remote has an explicit pushurl, git will ignore this
1916 setting for that remote.
1919 Your email address to be recorded in any newly created commits.
1920 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1921 'EMAIL' environment variables. See linkgit:git-commit-tree[1].
1924 Your full name to be recorded in any newly created commits.
1925 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1926 environment variables. See linkgit:git-commit-tree[1].
1929 If linkgit:git-tag[1] is not selecting the key you want it to
1930 automatically when creating a signed tag, you can override the
1931 default selection with this variable. This option is passed
1932 unchanged to gpg's --local-user parameter, so you may specify a key
1933 using any method that gpg supports.
1936 Specify a web browser that may be used by some commands.
1937 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]