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 case insensitive alternative `[section.subsection]` syntax.
49 In this syntax, subsection names follow the same restrictions as for section
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.
91 ; Don't trust file modes
96 external = /usr/local/bin/diff-wrapper
101 merge = refs/heads/devel
105 gitProxy="ssh" for "kernel.org"
106 gitProxy=default-proxy ; for the rest
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.
117 When set to 'true', display the given optional help message.
118 When set to 'false', do not display. The configuration variables
123 Advice shown when linkgit:git-push[1] refuses
124 non-fast-forward refs. Default: true.
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.
132 If false, the executable bit differences between the index and
133 the working copy are ignored; useful on broken filesystems like FAT.
134 See linkgit:git-update-index[1]. True by default.
136 core.ignoreCygwinFSTricks::
137 This option is only used by Cygwin implementation of Git. If false,
138 the Cygwin stat() and lstat() functions are used. This may be useful
139 if your repository consists of a few separate directories joined in
140 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
141 whenever it is possible and falls back to Cygwin functions only to
142 handle symbol links. The native mode is more than twice faster than
143 normal Cygwin l/stat() functions. True by default, unless core.filemode
144 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
145 POSIX emulation is required to support core.filemode.
148 If false, the ctime differences between the index and the
149 working copy are ignored; useful when the inode change time
150 is regularly modified by something outside Git (file system
151 crawlers and some backup systems).
152 See linkgit:git-update-index[1]. True by default.
155 The commands that output paths (e.g. 'ls-files',
156 'diff'), when not given the `-z` option, will quote
157 "unusual" characters in the pathname by enclosing the
158 pathname in a double-quote pair and with backslashes the
159 same way strings in C source code are quoted. If this
160 variable is set to false, the bytes higher than 0x80 are
161 not quoted but output as verbatim. Note that double
162 quote, backslash and control characters are always
163 quoted without `-z` regardless of the setting of this
167 If true, makes git convert `CRLF` at the end of lines in text files to
168 `LF` when reading from the filesystem, and convert in reverse when
169 writing to the filesystem. The variable can be set to
170 'input', in which case the conversion happens only while
171 reading from the filesystem but files are written out with
172 `LF` at the end of lines. Currently, which paths to consider
173 "text" (i.e. be subjected to the autocrlf mechanism) is
174 decided purely based on the contents.
177 If true, makes git check if converting `CRLF` as controlled by
178 `core.autocrlf` is reversible. Git will verify if a command
179 modifies a file in the work tree either directly or indirectly.
180 For example, committing a file followed by checking out the
181 same file should yield the original file in the work tree. If
182 this is not the case for the current setting of
183 `core.autocrlf`, git will reject the file. The variable can
184 be set to "warn", in which case git will only warn about an
185 irreversible conversion but continue the operation.
187 CRLF conversion bears a slight chance of corrupting data.
188 autocrlf=true will convert CRLF to LF during commit and LF to
189 CRLF during checkout. A file that contains a mixture of LF and
190 CRLF before the commit cannot be recreated by git. For text
191 files this is the right thing to do: it corrects line endings
192 such that we have only LF line endings in the repository.
193 But for binary files that are accidentally classified as text the
194 conversion can corrupt data.
196 If you recognize such corruption early you can easily fix it by
197 setting the conversion type explicitly in .gitattributes. Right
198 after committing you still have the original file in your work
199 tree and this file is not yet corrupted. You can explicitly tell
200 git that this file is binary and git will handle the file
203 Unfortunately, the desired effect of cleaning up text files with
204 mixed line endings and the undesired effect of corrupting binary
205 files cannot be distinguished. In both cases CRLFs are removed
206 in an irreversible way. For text files this is the right thing
207 to do because CRLFs are line endings, while for binary files
208 converting CRLFs corrupts data.
210 Note, this safety check does not mean that a checkout will generate a
211 file identical to the original file for a different setting of
212 `core.autocrlf`, but only for the current one. For example, a text
213 file with `LF` would be accepted with `core.autocrlf=input` and could
214 later be checked out with `core.autocrlf=true`, in which case the
215 resulting file would contain `CRLF`, although the original file
216 contained `LF`. However, in both work trees the line endings would be
217 consistent, that is either all `LF` or all `CRLF`, but never mixed. A
218 file with mixed line endings would be reported by the `core.safecrlf`
222 If false, symbolic links are checked out as small plain files that
223 contain the link text. linkgit:git-update-index[1] and
224 linkgit:git-add[1] will not change the recorded type to regular
225 file. Useful on filesystems like FAT that do not support
226 symbolic links. True by default.
229 A "proxy command" to execute (as 'command host port') instead
230 of establishing direct connection to the remote server when
231 using the git protocol for fetching. If the variable value is
232 in the "COMMAND for DOMAIN" format, the command is applied only
233 on hostnames ending with the specified domain string. This variable
234 may be set multiple times and is matched in the given order;
235 the first match wins.
237 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
238 (which always applies universally, without the special "for"
241 The special string `none` can be used as the proxy command to
242 specify that no proxy be used for a given domain pattern.
243 This is useful for excluding servers inside a firewall from
244 proxy use, while defaulting to a common proxy for external domains.
247 If true, commands which modify both the working tree and the index
248 will mark the updated paths with the "assume unchanged" bit in the
249 index. These marked files are then assumed to stay unchanged in the
250 working copy, until you mark them otherwise manually - Git will not
251 detect the file changes by lstat() calls. This is useful on systems
252 where those are very slow, such as Microsoft Windows.
253 See linkgit:git-update-index[1].
256 core.preferSymlinkRefs::
257 Instead of the default "symref" format for HEAD
258 and other symbolic reference files, use symbolic links.
259 This is sometimes needed to work with old scripts that
260 expect HEAD to be a symbolic link.
263 If true this repository is assumed to be 'bare' and has no
264 working directory associated with it. If this is the case a
265 number of commands that require a working directory will be
266 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
268 This setting is automatically guessed by linkgit:git-clone[1] or
269 linkgit:git-init[1] when the repository was created. By default a
270 repository that ends in "/.git" is assumed to be not bare (bare =
271 false), while all other repositories are assumed to be bare (bare
275 Set the path to the working tree. The value will not be
276 used in combination with repositories found automatically in
277 a .git directory (i.e. $GIT_DIR is not set).
278 This can be overridden by the GIT_WORK_TREE environment
279 variable and the '--work-tree' command line option. It can be
280 a absolute path or relative path to the directory specified by
281 --git-dir or GIT_DIR.
282 Note: If --git-dir or GIT_DIR are specified but none of
283 --work-tree, GIT_WORK_TREE and core.worktree is specified,
284 the current working directory is regarded as the top directory
285 of your working tree.
287 core.logAllRefUpdates::
288 Enable the reflog. Updates to a ref <ref> is logged to the file
289 "$GIT_DIR/logs/<ref>", by appending the new and old
290 SHA1, the date/time and the reason of the update, but
291 only when the file exists. If this configuration
292 variable is set to true, missing "$GIT_DIR/logs/<ref>"
293 file is automatically created for branch heads.
295 This information can be used to determine what commit
296 was the tip of a branch "2 days ago".
298 This value is true by default in a repository that has
299 a working directory associated with it, and false by
300 default in a bare repository.
302 core.repositoryFormatVersion::
303 Internal variable identifying the repository format and layout
306 core.sharedRepository::
307 When 'group' (or 'true'), the repository is made shareable between
308 several users in a group (making sure all the files and objects are
309 group-writable). When 'all' (or 'world' or 'everybody'), the
310 repository will be readable by all users, additionally to being
311 group-shareable. When 'umask' (or 'false'), git will use permissions
312 reported by umask(2). When '0xxx', where '0xxx' is an octal number,
313 files in the repository will have this mode value. '0xxx' will override
314 user's umask value (whereas the other options will only override
315 requested parts of the user's umask value). Examples: '0660' will make
316 the repo read/write-able for the owner and group, but inaccessible to
317 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
318 repository that is group-readable but not group-writable.
319 See linkgit:git-init[1]. False by default.
321 core.warnAmbiguousRefs::
322 If true, git will warn you if the ref name you passed it is ambiguous
323 and might match multiple refs in the .git/refs/ tree. True by default.
326 An integer -1..9, indicating a default compression level.
327 -1 is the zlib default. 0 means no compression,
328 and 1..9 are various speed/size tradeoffs, 9 being slowest.
329 If set, this provides a default to other compression variables,
330 such as 'core.loosecompression' and 'pack.compression'.
332 core.loosecompression::
333 An integer -1..9, indicating the compression level for objects that
334 are not in a pack file. -1 is the zlib default. 0 means no
335 compression, and 1..9 are various speed/size tradeoffs, 9 being
336 slowest. If not set, defaults to core.compression. If that is
337 not set, defaults to 1 (best speed).
339 core.packedGitWindowSize::
340 Number of bytes of a pack file to map into memory in a
341 single mapping operation. Larger window sizes may allow
342 your system to process a smaller number of large pack files
343 more quickly. Smaller window sizes will negatively affect
344 performance due to increased calls to the operating system's
345 memory manager, but may improve performance when accessing
346 a large number of large pack files.
348 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
349 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
350 be reasonable for all users/operating systems. You probably do
351 not need to adjust this value.
353 Common unit suffixes of 'k', 'm', or 'g' are supported.
355 core.packedGitLimit::
356 Maximum number of bytes to map simultaneously into memory
357 from pack files. If Git needs to access more than this many
358 bytes at once to complete an operation it will unmap existing
359 regions to reclaim virtual address space within the process.
361 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
362 This should be reasonable for all users/operating systems, except on
363 the largest projects. You probably do not need to adjust this value.
365 Common unit suffixes of 'k', 'm', or 'g' are supported.
367 core.deltaBaseCacheLimit::
368 Maximum number of bytes to reserve for caching base objects
369 that multiple deltafied objects reference. By storing the
370 entire decompressed base objects in a cache Git is able
371 to avoid unpacking and decompressing frequently used base
372 objects multiple times.
374 Default is 16 MiB on all platforms. This should be reasonable
375 for all users/operating systems, except on the largest projects.
376 You probably do not need to adjust this value.
378 Common unit suffixes of 'k', 'm', or 'g' are supported.
381 In addition to '.gitignore' (per-directory) and
382 '.git/info/exclude', git looks into this file for patterns
383 of files which are not meant to be tracked. See
384 linkgit:gitignore[5].
387 Commands such as `commit` and `tag` that lets you edit
388 messages by launching an editor uses the value of this
389 variable when it is set, and the environment variable
390 `GIT_EDITOR` is not set. See linkgit:git-var[1].
393 The command that git will use to paginate output. Can
394 be overridden with the `GIT_PAGER` environment
395 variable. Note that git sets the `LESS` environment
396 variable to `FRSX` if it is unset when it runs the
397 pager. One can change these settings by setting the
398 `LESS` variable to some other value. Alternately,
399 these settings can be overridden on a project or
400 global basis by setting the `core.pager` option.
401 Setting `core.pager` has no affect on the `LESS`
402 environment variable behaviour above, so if you want
403 to override git's default settings this way, you need
404 to be explicit. For example, to disable the S option
405 in a backward compatible manner, set `core.pager`
406 to `less -+$LESS -FRX`. This will be passed to the
407 shell by git, which will translate the final command to
408 `LESS=FRSX less -+FRSX -FRX`.
411 A comma separated list of common whitespace problems to
412 notice. 'git-diff' will use `color.diff.whitespace` to
413 highlight them, and 'git-apply --whitespace=error' will
414 consider them as errors. You can prefix `-` to disable
415 any of them (e.g. `-trailing-space`):
417 * `blank-at-eol` treats trailing whitespaces at the end of the line
418 as an error (enabled by default).
419 * `space-before-tab` treats a space character that appears immediately
420 before a tab character in the initial indent part of the line as an
421 error (enabled by default).
422 * `indent-with-non-tab` treats a line that is indented with 8 or more
423 space characters as an error (not enabled by default).
424 * `blank-at-eof` treats blank lines added at the end of file as an error
425 (enabled by default).
426 * `trailing-space` is a short-hand to cover both `blank-at-eol` and
428 * `cr-at-eol` treats a carriage-return at the end of line as
429 part of the line terminator, i.e. with it, `trailing-space`
430 does not trigger if the character before such a carriage-return
431 is not a whitespace (not enabled by default).
433 core.fsyncobjectfiles::
434 This boolean will enable 'fsync()' when writing object files.
436 This is a total waste of time and effort on a filesystem that orders
437 data writes properly, but can be useful for filesystems that do not use
438 journalling (traditional UNIX filesystems) or that only journal metadata
439 and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
442 Enable parallel index preload for operations like 'git diff'
444 This can speed up operations like 'git diff' and 'git status' especially
445 on filesystems like NFS that have weak caching semantics and thus
446 relatively high IO latencies. With this set to 'true', git will do the
447 index comparison to the filesystem data in parallel, allowing
451 You can set this to 'link', in which case a hardlink followed by
452 a delete of the source are used to make sure that object creation
453 will not overwrite existing objects.
455 On some file system/operating system combinations, this is unreliable.
456 Set this config setting to 'rename' there; However, This will remove the
457 check that makes sure that existing object files will not get overwritten.
460 Tells 'git-add' to continue adding files when some files cannot be
461 added due to indexing errors. Equivalent to the '--ignore-errors'
462 option of linkgit:git-add[1].
465 Command aliases for the linkgit:git[1] command wrapper - e.g.
466 after defining "alias.last = cat-file commit HEAD", the invocation
467 "git last" is equivalent to "git cat-file commit HEAD". To avoid
468 confusion and troubles with script usage, aliases that
469 hide existing git commands are ignored. Arguments are split by
470 spaces, the usual shell quoting and escaping is supported.
471 quote pair and a backslash can be used to quote them.
473 If the alias expansion is prefixed with an exclamation point,
474 it will be treated as a shell command. For example, defining
475 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
476 "git new" is equivalent to running the shell command
477 "gitk --all --not ORIG_HEAD". Note that shell commands will be
478 executed from the top-level directory of a repository, which may
479 not necessarily be the current directory.
481 apply.ignorewhitespace::
482 When set to 'change', tells 'git-apply' to ignore changes in
483 whitespace, in the same way as the '--ignore-space-change'
485 When set to one of: no, none, never, false tells 'git-apply' to
486 respect all whitespace differences.
487 See linkgit:git-apply[1].
490 Tells 'git-apply' how to handle whitespaces, in the same way
491 as the '--whitespace' option. See linkgit:git-apply[1].
493 branch.autosetupmerge::
494 Tells 'git-branch' and 'git-checkout' to setup new branches
495 so that linkgit:git-pull[1] will appropriately merge from the
496 starting point branch. Note that even if this option is not set,
497 this behavior can be chosen per-branch using the `--track`
498 and `--no-track` options. The valid settings are: `false` -- no
499 automatic setup is done; `true` -- automatic setup is done when the
500 starting point is a remote branch; `always` -- automatic setup is
501 done when the starting point is either a local branch or remote
502 branch. This option defaults to true.
504 branch.autosetuprebase::
505 When a new branch is created with 'git-branch' or 'git-checkout'
506 that tracks another branch, this variable tells git to set
507 up pull to rebase instead of merge (see "branch.<name>.rebase").
508 When `never`, rebase is never automatically set to true.
509 When `local`, rebase is set to true for tracked branches of
510 other local branches.
511 When `remote`, rebase is set to true for tracked branches of
513 When `always`, rebase will be set to true for all tracking
515 See "branch.autosetupmerge" for details on how to set up a
516 branch to track another branch.
517 This option defaults to never.
519 branch.<name>.remote::
520 When in branch <name>, it tells 'git-fetch' and 'git-push' which
521 remote to fetch from/push to. It defaults to `origin` if no remote is
522 configured. `origin` is also used if you are not on any branch.
524 branch.<name>.merge::
525 Defines, together with branch.<name>.remote, the upstream branch
526 for the given branch. It tells 'git-fetch'/'git-pull' which
527 branch to merge and can also affect 'git-push' (see push.default).
528 When in branch <name>, it tells 'git-fetch' the default
529 refspec to be marked for merging in FETCH_HEAD. The value is
530 handled like the remote part of a refspec, and must match a
531 ref which is fetched from the remote given by
532 "branch.<name>.remote".
533 The merge information is used by 'git-pull' (which at first calls
534 'git-fetch') to lookup the default branch for merging. Without
535 this option, 'git-pull' defaults to merge the first refspec fetched.
536 Specify multiple values to get an octopus merge.
537 If you wish to setup 'git-pull' so that it merges into <name> from
538 another branch in the local repository, you can point
539 branch.<name>.merge to the desired branch, and use the special setting
540 `.` (a period) for branch.<name>.remote.
542 branch.<name>.mergeoptions::
543 Sets default options for merging into branch <name>. The syntax and
544 supported options are the same as those of linkgit:git-merge[1], but
545 option values containing whitespace characters are currently not
548 branch.<name>.rebase::
549 When true, rebase the branch <name> on top of the fetched branch,
550 instead of merging the default branch from the default remote when
552 *NOTE*: this is a possibly dangerous operation; do *not* use
553 it unless you understand the implications (see linkgit:git-rebase[1]
557 Specify the command to invoke the specified browser. The
558 specified command is evaluated in shell with the URLs passed
559 as arguments. (See linkgit:git-web--browse[1].)
561 browser.<tool>.path::
562 Override the path for the given tool that may be used to
563 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
564 working repository in gitweb (see linkgit:git-instaweb[1]).
567 A boolean to make git-clean do nothing unless given -f
568 or -n. Defaults to true.
571 A boolean to enable/disable color in the output of
572 linkgit:git-branch[1]. May be set to `always`,
573 `false` (or `never`) or `auto` (or `true`), in which case colors are used
574 only when the output is to a terminal. Defaults to false.
576 color.branch.<slot>::
577 Use customized color for branch coloration. `<slot>` is one of
578 `current` (the current branch), `local` (a local branch),
579 `remote` (a tracking branch in refs/remotes/), `plain` (other
582 The value for these configuration variables is a list of colors (at most
583 two) and attributes (at most one), separated by spaces. The colors
584 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
585 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
586 `blink` and `reverse`. The first color given is the foreground; the
587 second is the background. The position of the attribute, if any,
591 When set to `always`, always use colors in patch.
592 When false (or `never`), never. When set to `true` or `auto`, use
593 colors only when the output is to the terminal. Defaults to false.
596 Use customized color for diff colorization. `<slot>` specifies
597 which part of the patch to use the specified color, and is one
598 of `plain` (context text), `meta` (metainformation), `frag`
599 (hunk header), `old` (removed lines), `new` (added lines),
600 `commit` (commit headers), or `whitespace` (highlighting
601 whitespace errors). The values of these variables may be specified as
602 in color.branch.<slot>.
605 When set to `always`, always highlight matches. When `false` (or
606 `never`), never. When set to `true` or `auto`, use color only
607 when the output is written to the terminal. Defaults to `false`.
609 color.grep.external::
610 The string value of this variable is passed to an external 'grep'
611 command as a command line option if match highlighting is turned
612 on. If set to an empty string, no option is passed at all,
613 turning off coloring for external 'grep' calls; this is the default.
614 For GNU grep, set it to `--color=always` to highlight matches even
615 when a pager is used.
618 Use customized color for matches. The value of this variable
619 may be specified as in color.branch.<slot>. It is passed using
620 the environment variables 'GREP_COLOR' and 'GREP_COLORS' when
621 calling an external 'grep'.
624 When set to `always`, always use colors for interactive prompts
625 and displays (such as those used by "git-add --interactive").
626 When false (or `never`), never. When set to `true` or `auto`, use
627 colors only when the output is to the terminal. Defaults to false.
629 color.interactive.<slot>::
630 Use customized color for 'git-add --interactive'
631 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
632 four distinct types of normal output from interactive
633 commands. The values of these variables may be specified as
634 in color.branch.<slot>.
637 A boolean to enable/disable colored output when the pager is in
638 use (default is true).
641 A boolean to enable/disable color in the output of
642 linkgit:git-show-branch[1]. May be set to `always`,
643 `false` (or `never`) or `auto` (or `true`), in which case colors are used
644 only when the output is to a terminal. Defaults to false.
647 A boolean to enable/disable color in the output of
648 linkgit:git-status[1]. May be set to `always`,
649 `false` (or `never`) or `auto` (or `true`), in which case colors are used
650 only when the output is to a terminal. Defaults to false.
652 color.status.<slot>::
653 Use customized color for status colorization. `<slot>` is
654 one of `header` (the header text of the status message),
655 `added` or `updated` (files which are added but not committed),
656 `changed` (files which are changed but not added in the index),
657 `untracked` (files which are not tracked by git), or
658 `nobranch` (the color the 'no branch' warning is shown in, defaulting
659 to red). The values of these variables may be specified as in
663 When set to `always`, always use colors in all git commands which
664 are capable of colored output. When false (or `never`), never. When
665 set to `true` or `auto`, use colors only when the output is to the
666 terminal. When more specific variables of color.* are set, they always
667 take precedence over this setting. Defaults to false.
670 Specify a file to use as the template for new commit messages.
672 diff.autorefreshindex::
673 When using 'git-diff' to compare with work tree
674 files, do not consider stat-only change as changed.
675 Instead, silently run `git update-index --refresh` to
676 update the cached stat information for paths whose
677 contents in the work tree match the contents in the
678 index. This option defaults to true. Note that this
679 affects only 'git-diff' Porcelain, and not lower level
680 'diff' commands, such as 'git-diff-files'.
683 If this config variable is set, diff generation is not
684 performed using the internal diff machinery, but using the
685 given command. Can be overridden with the `GIT_EXTERNAL_DIFF'
686 environment variable. The command is called with parameters
687 as described under "git Diffs" in linkgit:git[1]. Note: if
688 you want to use an external diff program only on a subset of
689 your files, you might want to use linkgit:gitattributes[5] instead.
691 diff.mnemonicprefix::
692 If set, 'git-diff' uses a prefix pair that is different from the
693 standard "a/" and "b/" depending on what is being compared. When
694 this configuration is in effect, reverse diff output also swaps
695 the order of the prefixes:
697 compares the (i)ndex and the (w)ork tree;
699 compares a (c)ommit and the (w)ork tree;
700 'git diff --cached';;
701 compares a (c)ommit and the (i)ndex;
702 'git-diff HEAD:file1 file2';;
703 compares an (o)bject and a (w)ork tree entity;
704 'git diff --no-index a b';;
705 compares two non-git things (1) and (2).
708 The number of files to consider when performing the copy/rename
709 detection; equivalent to the 'git-diff' option '-l'.
712 Tells git to detect renames. If set to any boolean value, it
713 will enable basic rename detection. If set to "copies" or
714 "copy", it will detect copies, as well.
716 diff.suppressBlankEmpty::
717 A boolean to inhibit the standard behavior of printing a space
718 before each empty output line. Defaults to false.
721 Controls which diff tool is used. `diff.tool` overrides
722 `merge.tool` when used by linkgit:git-difftool[1] and has
723 the same valid values as `merge.tool` minus "tortoisemerge"
726 difftool.<tool>.path::
727 Override the path for the given tool. This is useful in case
728 your tool is not in the PATH.
730 difftool.<tool>.cmd::
731 Specify the command to invoke the specified diff tool.
732 The specified command is evaluated in shell with the following
733 variables available: 'LOCAL' is set to the name of the temporary
734 file containing the contents of the diff pre-image and 'REMOTE'
735 is set to the name of the temporary file containing the contents
736 of the diff post-image.
739 Prompt before each invocation of the diff tool.
742 A POSIX Extended Regular Expression used to determine what is a "word"
743 when performing word-by-word difference calculations. Character
744 sequences that match the regular expression are "words", all other
745 characters are *ignorable* whitespace.
748 If the number of objects fetched over the git native
749 transfer is below this
750 limit, then the objects will be unpacked into loose object
751 files. However if the number of received objects equals or
752 exceeds this limit then the received pack will be stored as
753 a pack, after adding any missing delta bases. Storing the
754 pack from a push can make the push operation complete faster,
755 especially on slow filesystems. If not set, the value of
756 `transfer.unpackLimit` is used instead.
759 Enable multipart/mixed attachments as the default for
760 'format-patch'. The value can also be a double quoted string
761 which will enable attachments as the default and set the
762 value as the boundary. See the --attach option in
763 linkgit:git-format-patch[1].
766 A boolean which can enable or disable sequence numbers in patch
767 subjects. It defaults to "auto" which enables it only if there
768 is more than one patch. It can be enabled or disabled for all
769 messages by setting it to "true" or "false". See --numbered
770 option in linkgit:git-format-patch[1].
773 Additional email headers to include in a patch to be submitted
774 by mail. See linkgit:git-format-patch[1].
777 Additional "Cc:" headers to include in a patch to be submitted
778 by mail. See the --cc option in linkgit:git-format-patch[1].
780 format.subjectprefix::
781 The default for format-patch is to output files with the '[PATCH]'
782 subject prefix. Use this variable to change that prefix.
785 The default for format-patch is to output files with the suffix
786 `.patch`. Use this variable to change that suffix (make sure to
787 include the dot if you want it).
790 The default pretty format for log/show/whatchanged command,
791 See linkgit:git-log[1], linkgit:git-show[1],
792 linkgit:git-whatchanged[1].
795 The default threading style for 'git-format-patch'. Can be
796 either a boolean value, `shallow` or `deep`. `shallow`
797 threading makes every mail a reply to the head of the series,
798 where the head is chosen from the cover letter, the
799 `\--in-reply-to`, and the first patch mail, in this order.
800 `deep` threading makes every mail a reply to the previous one.
801 A true boolean value is the same as `shallow`, and a false
802 value disables threading.
805 A boolean value which lets you enable the `-s/--signoff` option of
806 format-patch by default. *Note:* Adding the Signed-off-by: line to a
807 patch should be a conscious act and means that you certify you have
808 the rights to submit this work under the same open source license.
809 Please see the 'SubmittingPatches' document for further discussion.
811 gc.aggressiveWindow::
812 The window size parameter used in the delta compression
813 algorithm used by 'git-gc --aggressive'. This defaults
817 When there are approximately more than this many loose
818 objects in the repository, `git gc --auto` will pack them.
819 Some Porcelain commands use this command to perform a
820 light-weight garbage collection from time to time. The
821 default value is 6700. Setting this to 0 disables it.
824 When there are more than this many packs that are not
825 marked with `*.keep` file in the repository, `git gc
826 --auto` consolidates them into one larger pack. The
827 default value is 50. Setting this to 0 disables it.
830 'git-gc' does not run `git pack-refs` in a bare repository by
831 default so that older dumb-transport clients can still fetch
832 from the repository. Setting this to `true` lets 'git-gc'
833 to run `git pack-refs`. Setting this to `false` tells
834 'git-gc' never to run `git pack-refs`. The default setting is
835 `notbare`. Enable it only when you know you do not have to
836 support such clients. The default setting will change to `true`
837 at some stage, and setting this to `false` will continue to
838 prevent `git pack-refs` from being run from 'git-gc'.
841 When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'.
842 Override the grace period with this config variable. The value
843 "now" may be used to disable this grace period and always prune
844 unreachable objects immediately.
847 'git-reflog expire' removes reflog entries older than
848 this time; defaults to 90 days.
850 gc.reflogexpireunreachable::
851 'git-reflog expire' removes reflog entries older than
852 this time and are not reachable from the current tip;
856 Records of conflicted merge you resolved earlier are
857 kept for this many days when 'git-rerere gc' is run.
858 The default is 60 days. See linkgit:git-rerere[1].
860 gc.rerereunresolved::
861 Records of conflicted merge you have not resolved are
862 kept for this many days when 'git-rerere gc' is run.
863 The default is 15 days. See linkgit:git-rerere[1].
865 gitcvs.commitmsgannotation::
866 Append this string to each commit message. Set to empty string
867 to disable this feature. Defaults to "via git-CVS emulator".
870 Whether the CVS server interface is enabled for this repository.
871 See linkgit:git-cvsserver[1].
874 Path to a log file where the CVS server interface well... logs
875 various stuff. See linkgit:git-cvsserver[1].
878 If true, the server will look up the `crlf` attribute for
879 files to determine the '-k' modes to use. If `crlf` is set,
880 the '-k' mode will be left blank, so cvs clients will
881 treat it as text. If `crlf` is explicitly unset, the file
882 will be set with '-kb' mode, which suppresses any newline munging
883 the client might otherwise do. If `crlf` is not specified,
884 then 'gitcvs.allbinary' is used. See linkgit:gitattributes[5].
887 This is used if 'gitcvs.usecrlfattr' does not resolve
888 the correct '-kb' mode to use. If true, all
889 unresolved files are sent to the client in
890 mode '-kb'. This causes the client to treat them
891 as binary files, which suppresses any newline munging it
892 otherwise might do. Alternatively, if it is set to "guess",
893 then the contents of the file are examined to decide if
894 it is binary, similar to 'core.autocrlf'.
897 Database used by git-cvsserver to cache revision information
898 derived from the git repository. The exact meaning depends on the
899 used database driver, for SQLite (which is the default driver) this
900 is a filename. Supports variable substitution (see
901 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
902 Default: '%Ggitcvs.%m.sqlite'
905 Used Perl DBI driver. You can specify any available driver
906 for this here, but it might not work. git-cvsserver is tested
907 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
908 reported *not* to work with 'DBD::mysql'. Experimental feature.
909 May not contain double colons (`:`). Default: 'SQLite'.
910 See linkgit:git-cvsserver[1].
912 gitcvs.dbuser, gitcvs.dbpass::
913 Database user and password. Only useful if setting 'gitcvs.dbdriver',
914 since SQLite has no concept of database users and/or passwords.
915 'gitcvs.dbuser' supports variable substitution (see
916 linkgit:git-cvsserver[1] for details).
918 gitcvs.dbTableNamePrefix::
919 Database table name prefix. Prepended to the names of any
920 database tables used, allowing a single database to be used
921 for several repositories. Supports variable substitution (see
922 linkgit:git-cvsserver[1] for details). Any non-alphabetic
923 characters will be replaced with underscores.
925 All gitcvs variables except for 'gitcvs.usecrlfattr' and
926 'gitcvs.allbinary' can also be specified as
927 'gitcvs.<access_method>.<varname>' (where 'access_method'
928 is one of "ext" and "pserver") to make them apply only for the given
932 Defines how wide the commit message window is in the
933 linkgit:git-gui[1]. "75" is the default.
936 Specifies how many context lines should be used in calls to diff
937 made by the linkgit:git-gui[1]. The default is "5".
940 Specifies the default encoding to use for displaying of
941 file contents in linkgit:git-gui[1] and linkgit:gitk[1].
942 It can be overridden by setting the 'encoding' attribute
943 for relevant files (see linkgit:gitattributes[5]).
944 If this option is not set, the tools default to the
947 gui.matchtrackingbranch::
948 Determines if new branches created with linkgit:git-gui[1] should
949 default to tracking remote branches with matching names or
950 not. Default: "false".
952 gui.newbranchtemplate::
953 Is used as suggested name when creating new branches using the
956 gui.pruneduringfetch::
957 "true" if linkgit:git-gui[1] should prune tracking branches when
958 performing a fetch. The default value is "false".
961 Determines if linkgit:git-gui[1] should trust the file modification
962 timestamp or not. By default the timestamps are not trusted.
964 gui.spellingdictionary::
965 Specifies the dictionary used for spell checking commit messages in
966 the linkgit:git-gui[1]. When set to "none" spell checking is turned
970 If true, 'git gui blame' uses '-C' instead of '-C -C' for original
971 location detection. It makes blame significantly faster on huge
972 repositories at the expense of less thorough copy detection.
974 gui.copyblamethreshold::
975 Specifies the threshold to use in 'git gui blame' original location
976 detection, measured in alphanumeric characters. See the
977 linkgit:git-blame[1] manual for more information on copy detection.
979 gui.blamehistoryctx::
980 Specifies the radius of history context in days to show in
981 linkgit:gitk[1] for the selected commit, when the `Show History
982 Context` menu item is invoked from 'git gui blame'. If this
983 variable is set to zero, the whole history is shown.
986 Specifies the shell command line to execute when the corresponding item
987 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
988 mandatory for every tool. The command is executed from the root of
989 the working directory, and in the environment it receives the name of
990 the tool as 'GIT_GUITOOL', the name of the currently selected file as
991 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
992 the head is detached, 'CUR_BRANCH' is empty).
994 guitool.<name>.needsfile::
995 Run the tool only if a diff is selected in the GUI. It guarantees
996 that 'FILENAME' is not empty.
998 guitool.<name>.noconsole::
999 Run the command silently, without creating a window to display its
1002 guitool.<name>.norescan::
1003 Don't rescan the working directory for changes after the tool
1006 guitool.<name>.confirm::
1007 Show a confirmation dialog before actually running the tool.
1009 guitool.<name>.argprompt::
1010 Request a string argument from the user, and pass it to the tool
1011 through the 'ARGS' environment variable. Since requesting an
1012 argument implies confirmation, the 'confirm' option has no effect
1013 if this is enabled. If the option is set to 'true', 'yes', or '1',
1014 the dialog uses a built-in generic prompt; otherwise the exact
1015 value of the variable is used.
1017 guitool.<name>.revprompt::
1018 Request a single valid revision from the user, and set the
1019 'REVISION' environment variable. In other aspects this option
1020 is similar to 'argprompt', and can be used together with it.
1022 guitool.<name>.revunmerged::
1023 Show only unmerged branches in the 'revprompt' subdialog.
1024 This is useful for tools similar to merge or rebase, but not
1025 for things like checkout or reset.
1027 guitool.<name>.title::
1028 Specifies the title to use for the prompt dialog. The default
1031 guitool.<name>.prompt::
1032 Specifies the general prompt string to display at the top of
1033 the dialog, before subsections for 'argprompt' and 'revprompt'.
1034 The default value includes the actual command.
1037 Specify the browser that will be used to display help in the
1038 'web' format. See linkgit:git-help[1].
1041 Override the default help format used by linkgit:git-help[1].
1042 Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1043 the default. 'web' and 'html' are the same.
1046 Automatically correct and execute mistyped commands after
1047 waiting for the given number of deciseconds (0.1 sec). If more
1048 than one command can be deduced from the entered text, nothing
1049 will be executed. If the value of this option is negative,
1050 the corrected command will be executed immediately. If the
1051 value is 0 - the command will be just shown but not executed.
1052 This is the default.
1055 Override the HTTP proxy, normally configured using the 'http_proxy'
1056 environment variable (see linkgit:curl[1]). This can be overridden
1057 on a per-remote basis; see remote.<name>.proxy
1060 Whether to verify the SSL certificate when fetching or pushing
1061 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1065 File containing the SSL certificate when fetching or pushing
1066 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1070 File containing the SSL private key when fetching or pushing
1071 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1074 http.sslCertPasswordProtected::
1075 Enable git's password prompt for the SSL certificate. Otherwise
1076 OpenSSL will prompt the user, possibly many times, if the
1077 certificate or private key is encrypted. Can be overridden by the
1078 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1081 File containing the certificates to verify the peer with when
1082 fetching or pushing over HTTPS. Can be overridden by the
1083 'GIT_SSL_CAINFO' environment variable.
1086 Path containing files with the CA certificates to verify the peer
1087 with when fetching or pushing over HTTPS. Can be overridden
1088 by the 'GIT_SSL_CAPATH' environment variable.
1091 How many HTTP requests to launch in parallel. Can be overridden
1092 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1094 http.lowSpeedLimit, http.lowSpeedTime::
1095 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1096 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1097 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1098 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1101 A boolean which disables using of EPSV ftp command by curl.
1102 This can helpful with some "poor" ftp servers which don't
1103 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1104 environment variable. Default is false (curl will use EPSV).
1106 i18n.commitEncoding::
1107 Character encoding the commit messages are stored in; git itself
1108 does not care per se, but this information is necessary e.g. when
1109 importing commits from emails or in the gitk graphical history
1110 browser (and possibly at other places in the future or in other
1111 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1113 i18n.logOutputEncoding::
1114 Character encoding the commit messages are converted to when
1115 running 'git-log' and friends.
1118 The configuration variables in the 'imap' section are described
1119 in linkgit:git-imap-send[1].
1122 Specify the program that will be used to browse your working
1123 repository in gitweb. See linkgit:git-instaweb[1].
1126 The HTTP daemon command-line to start gitweb on your working
1127 repository. See linkgit:git-instaweb[1].
1130 If true the web server started by linkgit:git-instaweb[1] will
1131 be bound to the local IP (127.0.0.1).
1133 instaweb.modulepath::
1134 The module path for an apache httpd used by linkgit:git-instaweb[1].
1137 The port number to bind the gitweb httpd to. See
1138 linkgit:git-instaweb[1].
1140 interactive.singlekey::
1141 In interactive commands, allow the user to provide one-letter
1142 input with a single key (i.e., without hitting enter).
1143 Currently this is used only by the `\--patch` mode of
1144 linkgit:git-add[1]. Note that this setting is silently
1145 ignored if portable keystroke input is not available.
1148 Set default date-time mode for the log command. Setting log.date
1149 value is similar to using 'git-log'\'s --date option. The value is one of the
1150 following alternatives: {relative,local,default,iso,rfc,short}.
1151 See linkgit:git-log[1].
1154 If true, the initial commit will be shown as a big creation event.
1155 This is equivalent to a diff against an empty tree.
1156 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1157 normally hide the root commit will now show it. True by default.
1160 The location of an augmenting mailmap file. The default
1161 mailmap, located in the root of the repository, is loaded
1162 first, then the mailmap file pointed to by this variable.
1163 The location of the mailmap file may be in a repository
1164 subdirectory, or somewhere outside of the repository itself.
1165 See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1168 Specify the programs that may be used to display help in the
1169 'man' format. See linkgit:git-help[1].
1172 Specify the command to invoke the specified man viewer. The
1173 specified command is evaluated in shell with the man page
1174 passed as argument. (See linkgit:git-help[1].)
1177 Override the path for the given tool that may be used to
1178 display help in the 'man' format. See linkgit:git-help[1].
1180 include::merge-config.txt[]
1182 mergetool.<tool>.path::
1183 Override the path for the given tool. This is useful in case
1184 your tool is not in the PATH.
1186 mergetool.<tool>.cmd::
1187 Specify the command to invoke the specified merge tool. The
1188 specified command is evaluated in shell with the following
1189 variables available: 'BASE' is the name of a temporary file
1190 containing the common base of the files to be merged, if available;
1191 'LOCAL' is the name of a temporary file containing the contents of
1192 the file on the current branch; 'REMOTE' is the name of a temporary
1193 file containing the contents of the file from the branch being
1194 merged; 'MERGED' contains the name of the file to which the merge
1195 tool should write the results of a successful merge.
1197 mergetool.<tool>.trustExitCode::
1198 For a custom merge command, specify whether the exit code of
1199 the merge command can be used to determine whether the merge was
1200 successful. If this is not set to true then the merge target file
1201 timestamp is checked and the merge assumed to have been successful
1202 if the file has been updated, otherwise the user is prompted to
1203 indicate the success of the merge.
1205 mergetool.keepBackup::
1206 After performing a merge, the original file with conflict markers
1207 can be saved as a file with a `.orig` extension. If this variable
1208 is set to `false` then this file is not preserved. Defaults to
1209 `true` (i.e. keep the backup files).
1211 mergetool.keepTemporaries::
1212 When invoking a custom merge tool, git uses a set of temporary
1213 files to pass to the tool. If the tool returns an error and this
1214 variable is set to `true`, then these temporary files will be
1215 preserved, otherwise they will be removed after the tool has
1216 exited. Defaults to `false`.
1219 Prompt before each invocation of the merge resolution program.
1222 The size of the window used by linkgit:git-pack-objects[1] when no
1223 window size is given on the command line. Defaults to 10.
1226 The maximum delta depth used by linkgit:git-pack-objects[1] when no
1227 maximum depth is given on the command line. Defaults to 50.
1230 The window memory size limit used by linkgit:git-pack-objects[1]
1231 when no limit is given on the command line. The value can be
1232 suffixed with "k", "m", or "g". Defaults to 0, meaning no
1236 An integer -1..9, indicating the compression level for objects
1237 in a pack file. -1 is the zlib default. 0 means no
1238 compression, and 1..9 are various speed/size tradeoffs, 9 being
1239 slowest. If not set, defaults to core.compression. If that is
1240 not set, defaults to -1, the zlib default, which is "a default
1241 compromise between speed and compression (currently equivalent
1244 pack.deltaCacheSize::
1245 The maximum memory in bytes used for caching deltas in
1246 linkgit:git-pack-objects[1] before writing them out to a pack.
1247 This cache is used to speed up the writing object phase by not
1248 having to recompute the final delta result once the best match
1249 for all objects is found. Repacking large repositories on machines
1250 which are tight with memory might be badly impacted by this though,
1251 especially if this cache pushes the system into swapping.
1252 A value of 0 means no limit. The smallest size of 1 byte may be
1253 used to virtually disable this cache. Defaults to 256 MiB.
1255 pack.deltaCacheLimit::
1256 The maximum size of a delta, that is cached in
1257 linkgit:git-pack-objects[1]. This cache is used to speed up the
1258 writing object phase by not having to recompute the final delta
1259 result once the best match for all objects is found. Defaults to 1000.
1262 Specifies the number of threads to spawn when searching for best
1263 delta matches. This requires that linkgit:git-pack-objects[1]
1264 be compiled with pthreads otherwise this option is ignored with a
1265 warning. This is meant to reduce packing time on multiprocessor
1266 machines. The required amount of memory for the delta search window
1267 is however multiplied by the number of threads.
1268 Specifying 0 will cause git to auto-detect the number of CPU's
1269 and set the number of threads accordingly.
1272 Specify the default pack index version. Valid values are 1 for
1273 legacy pack index used by Git versions prior to 1.5.2, and 2 for
1274 the new pack index with capabilities for packs larger than 4 GB
1275 as well as proper protection against the repacking of corrupted
1276 packs. Version 2 is the default. Note that version 2 is enforced
1277 and this config option ignored whenever the corresponding pack is
1280 If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1281 cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1282 that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1283 other side may give you a repository that cannot be accessed with your
1284 older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1285 you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1286 the `{asterisk}.idx` file.
1288 pack.packSizeLimit::
1289 The default maximum size of a pack. This setting only affects
1290 packing to a file, i.e. the git:// protocol is unaffected. It
1291 can be overridden by the `\--max-pack-size` option of
1292 linkgit:git-repack[1].
1295 Allows turning on or off pagination of the output of a
1296 particular git subcommand when writing to a tty. If
1297 `\--paginate` or `\--no-pager` is specified on the command line,
1298 it takes precedence over this option. To disable pagination for
1299 all commands, set `core.pager` or `GIT_PAGER` to `cat`.
1302 The default merge strategy to use when pulling multiple branches
1306 The default merge strategy to use when pulling a single branch.
1309 Defines the action git push should take if no refspec is given
1310 on the command line, no refspec is configured in the remote, and
1311 no refspec is implied by any of the options given on the command
1312 line. Possible values are:
1314 * `nothing` do not push anything.
1315 * `matching` push all matching branches.
1316 All branches having the same name in both ends are considered to be
1317 matching. This is the default.
1318 * `tracking` push the current branch to its upstream branch.
1319 * `current` push the current branch to a branch of the same name.
1322 Whether to show a diffstat of what changed upstream since the last
1323 rebase. False by default.
1326 By default, git-receive-pack will run "git-gc --auto" after
1327 receiving data from git-push and updating refs. You can stop
1328 it by setting this variable to false.
1330 receive.fsckObjects::
1331 If it is set to true, git-receive-pack will check all received
1332 objects. It will abort in the case of a malformed object or a
1333 broken link. The result of an abort are only dangling objects.
1336 receive.unpackLimit::
1337 If the number of objects received in a push is below this
1338 limit then the objects will be unpacked into loose object
1339 files. However if the number of received objects equals or
1340 exceeds this limit then the received pack will be stored as
1341 a pack, after adding any missing delta bases. Storing the
1342 pack from a push can make the push operation complete faster,
1343 especially on slow filesystems. If not set, the value of
1344 `transfer.unpackLimit` is used instead.
1346 receive.denyDeletes::
1347 If set to true, git-receive-pack will deny a ref update that deletes
1348 the ref. Use this to prevent such a ref deletion via a push.
1350 receive.denyCurrentBranch::
1351 If set to true or "refuse", receive-pack will deny a ref update
1352 to the currently checked out branch of a non-bare repository.
1353 Such a push is potentially dangerous because it brings the HEAD
1354 out of sync with the index and working tree. If set to "warn",
1355 print a warning of such a push to stderr, but allow the push to
1356 proceed. If set to false or "ignore", allow such pushes with no
1357 message. Defaults to "warn".
1359 receive.denyNonFastForwards::
1360 If set to true, git-receive-pack will deny a ref update which is
1361 not a fast-forward. Use this to prevent such an update via a push,
1362 even if that push is forced. This configuration variable is
1363 set when initializing a shared repository.
1365 receive.updateserverinfo::
1366 If set to true, git-receive-pack will run git-update-server-info
1367 after receiving data from git-push and updating refs.
1370 The URL of a remote repository. See linkgit:git-fetch[1] or
1371 linkgit:git-push[1].
1373 remote.<name>.pushurl::
1374 The push URL of a remote repository. See linkgit:git-push[1].
1376 remote.<name>.proxy::
1377 For remotes that require curl (http, https and ftp), the URL to
1378 the proxy to use for that remote. Set to the empty string to
1379 disable proxying for that remote.
1381 remote.<name>.fetch::
1382 The default set of "refspec" for linkgit:git-fetch[1]. See
1383 linkgit:git-fetch[1].
1385 remote.<name>.push::
1386 The default set of "refspec" for linkgit:git-push[1]. See
1387 linkgit:git-push[1].
1389 remote.<name>.mirror::
1390 If true, pushing to this remote will automatically behave
1391 as if the `\--mirror` option was given on the command line.
1393 remote.<name>.skipDefaultUpdate::
1394 If true, this remote will be skipped by default when updating
1395 using the update subcommand of linkgit:git-remote[1].
1397 remote.<name>.receivepack::
1398 The default program to execute on the remote side when pushing. See
1399 option \--receive-pack of linkgit:git-push[1].
1401 remote.<name>.uploadpack::
1402 The default program to execute on the remote side when fetching. See
1403 option \--upload-pack of linkgit:git-fetch-pack[1].
1405 remote.<name>.tagopt::
1406 Setting this value to \--no-tags disables automatic tag following when
1407 fetching from remote <name>
1410 The list of remotes which are fetched by "git remote update
1411 <group>". See linkgit:git-remote[1].
1413 repack.usedeltabaseoffset::
1414 By default, linkgit:git-repack[1] creates packs that use
1415 delta-base offset. If you need to share your repository with
1416 git older than version 1.4.4, either directly or via a dumb
1417 protocol such as http, then you need to set this option to
1418 "false" and repack. Access from old git versions over the
1419 native protocol are unaffected by this option.
1422 When set to true, `git-rerere` updates the index with the
1423 resulting contents after it cleanly resolves conflicts using
1424 previously recorded resolution. Defaults to false.
1427 Activate recording of resolved conflicts, so that identical
1428 conflict hunks can be resolved automatically, should they
1429 be encountered again. linkgit:git-rerere[1] command is by
1430 default enabled if you create `rr-cache` directory under
1431 `$GIT_DIR`, but can be disabled by setting this option to false.
1433 sendemail.identity::
1434 A configuration identity. When given, causes values in the
1435 'sendemail.<identity>' subsection to take precedence over
1436 values in the 'sendemail' section. The default identity is
1437 the value of 'sendemail.identity'.
1439 sendemail.smtpencryption::
1440 See linkgit:git-send-email[1] for description. Note that this
1441 setting is not subject to the 'identity' mechanism.
1444 Deprecated alias for 'sendemail.smtpencryption = ssl'.
1446 sendemail.<identity>.*::
1447 Identity-specific versions of the 'sendemail.*' parameters
1448 found below, taking precedence over those when the this
1449 identity is selected, through command-line or
1450 'sendemail.identity'.
1452 sendemail.aliasesfile::
1453 sendemail.aliasfiletype::
1457 sendemail.chainreplyto::
1459 sendemail.envelopesender::
1461 sendemail.multiedit::
1462 sendemail.signedoffbycc::
1463 sendemail.smtppass::
1464 sendemail.suppresscc::
1465 sendemail.suppressfrom::
1467 sendemail.smtpserver::
1468 sendemail.smtpserverport::
1469 sendemail.smtpuser::
1471 sendemail.validate::
1472 See linkgit:git-send-email[1] for description.
1474 sendemail.signedoffcc::
1475 Deprecated alias for 'sendemail.signedoffbycc'.
1477 showbranch.default::
1478 The default set of branches for linkgit:git-show-branch[1].
1479 See linkgit:git-show-branch[1].
1481 status.relativePaths::
1482 By default, linkgit:git-status[1] shows paths relative to the
1483 current directory. Setting this variable to `false` shows paths
1484 relative to the repository root (this was the default for git
1487 status.showUntrackedFiles::
1488 By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1489 files which are not currently tracked by Git. Directories which
1490 contain only untracked files, are shown with the directory name
1491 only. Showing untracked files means that Git needs to lstat() all
1492 all the files in the whole repository, which might be slow on some
1493 systems. So, this variable controls how the commands displays
1494 the untracked files. Possible values are:
1497 - 'no' - Show no untracked files
1498 - 'normal' - Shows untracked files and directories
1499 - 'all' - Shows also individual files in untracked directories.
1502 If this variable is not specified, it defaults to 'normal'.
1503 This variable can be overridden with the -u|--untracked-files option
1504 of linkgit:git-status[1] and linkgit:git-commit[1].
1507 This variable can be used to restrict the permission bits of
1508 tar archive entries. The default is 0002, which turns off the
1509 world write bit. The special value "user" indicates that the
1510 archiving user's umask will be used instead. See umask(2) and
1511 linkgit:git-archive[1].
1513 transfer.unpackLimit::
1514 When `fetch.unpackLimit` or `receive.unpackLimit` are
1515 not set, the value of this variable is used instead.
1516 The default value is 100.
1518 url.<base>.insteadOf::
1519 Any URL that starts with this value will be rewritten to
1520 start, instead, with <base>. In cases where some site serves a
1521 large number of repositories, and serves them with multiple
1522 access methods, and some users need to use different access
1523 methods, this feature allows people to specify any of the
1524 equivalent URLs and have git automatically rewrite the URL to
1525 the best alternative for the particular user, even for a
1526 never-before-seen repository on the site. When more than one
1527 insteadOf strings match a given URL, the longest match is used.
1529 url.<base>.pushInsteadOf::
1530 Any URL that starts with this value will not be pushed to;
1531 instead, it will be rewritten to start with <base>, and the
1532 resulting URL will be pushed to. In cases where some site serves
1533 a large number of repositories, and serves them with multiple
1534 access methods, some of which do not allow push, this feature
1535 allows people to specify a pull-only URL and have git
1536 automatically use an appropriate URL to push, even for a
1537 never-before-seen repository on the site. When more than one
1538 pushInsteadOf strings match a given URL, the longest match is
1539 used. If a remote has an explicit pushurl, git will ignore this
1540 setting for that remote.
1543 Your email address to be recorded in any newly created commits.
1544 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1545 'EMAIL' environment variables. See linkgit:git-commit-tree[1].
1548 Your full name to be recorded in any newly created commits.
1549 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1550 environment variables. See linkgit:git-commit-tree[1].
1553 If linkgit:git-tag[1] is not selecting the key you want it to
1554 automatically when creating a signed tag, you can override the
1555 default selection with this variable. This option is passed
1556 unchanged to gpg's --local-user parameter, so you may specify a key
1557 using any method that gpg supports.
1560 Specify a web browser that may be used by some commands.
1561 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]