0e711374dd99e5be07e17bae1b37c81e9062fd66
1 CONFIGURATION FILE
2 ------------------
4 The git configuration file contains a number of variables that affect
5 the git command's behavior. `.git/config` file for each repository
6 is used to store the information for that repository, and
7 `$HOME/.gitconfig` is used to store per user information to give
8 fallback values for `.git/config` file. The file `/etc/gitconfig`
9 can be used to store system-wide defaults.
11 They can be used by both the git plumbing
12 and the porcelains. The variables are divided into sections, where
13 in the fully qualified variable name the variable itself is the last
14 dot-separated segment and the section name is everything before the last
15 dot. The variable names are case-insensitive and only alphanumeric
16 characters are allowed. Some variables may appear multiple times.
18 Syntax
19 ~~~~~~
21 The syntax is fairly flexible and permissive; whitespaces are mostly
22 ignored. The '#' and ';' characters begin comments to the end of line,
23 blank lines are ignored.
25 The file consists of sections and variables. A section begins with
26 the name of the section in square brackets and continues until the next
27 section begins. Section names are not case sensitive. Only alphanumeric
28 characters, '`-`' and '`.`' are allowed in section names. Each variable
29 must belong to some section, which means that there must be section
30 header before 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 example below:
36 --------
37 [section "subsection"]
39 --------
41 Subsection names can contain any characters except newline (doublequote
42 '`"`' and backslash have to be escaped as '`\"`' and '`\\`',
43 respectively) and are case sensitive. Section header cannot span multiple
44 lines. Variables may belong directly to a section or to a given subsection.
45 You can have `[section]` if you have `[section "subsection"]`, but you
46 don't need to.
48 There is also (case insensitive) alternative `[section.subsection]` syntax.
49 In this syntax subsection names follow the same restrictions as for section
50 name.
52 All the other lines are recognized as setting variables, in the form
53 'name = value'. If there is no equal sign on the line, the entire line
54 is taken as 'name' and the variable is recognized as boolean "true".
55 The variable names are case-insensitive and only alphanumeric
56 characters and '`-`' are allowed. There can be more than one value
57 for a given variable; we say then that variable is multivalued.
59 Leading and trailing whitespace in a variable value is discarded.
60 Internal whitespace within a variable value is retained verbatim.
62 The values following the equals sign in variable assign are all either
63 a string, an integer, or a boolean. Boolean values may be given as yes/no,
64 0/1 or true/false. Case is not significant in boolean values, when
65 converting value to the canonical form using '--bool' type specifier;
66 `git-config` will ensure that the output is "true" or "false".
68 String values may be entirely or partially enclosed in double quotes.
69 You need to enclose variable value in double quotes if you want to
70 preserve leading or trailing whitespace, or if variable value contains
71 beginning of comment characters (if it contains '#' or ';').
72 Double quote '`"`' and backslash '`\`' characters in variable value must
73 be escaped: use '`\"`' for '`"`' and '`\\`' for '`\`'.
75 The following escape sequences (beside '`\"`' and '`\\`') are recognized:
76 '`\n`' for newline character (NL), '`\t`' for horizontal tabulation (HT, TAB)
77 and '`\b`' for backspace (BS). No other char escape sequence, nor octal
78 char sequences are valid.
80 Variable value ending in a '`\`' is continued on the next line in the
81 customary UNIX fashion.
83 Some variables may require special value format.
85 Example
86 ~~~~~~~
88 # Core variables
89 [core]
90 ; Don't trust file modes
91 filemode = false
93 # Our diff algorithm
94 [diff]
95 external = "/usr/local/bin/gnu-diff -u"
96 renames = true
98 [branch "devel"]
99 remote = origin
100 merge = refs/heads/devel
102 # Proxy settings
103 [core]
104 gitProxy="ssh" for "kernel.org"
105 gitProxy=default-proxy ; for the rest
107 Variables
108 ~~~~~~~~~
110 Note that this list is non-comprehensive and not necessarily complete.
111 For command-specific variables, you will find a more detailed description
112 in the appropriate manual page. You will find a description of non-core
113 porcelain configuration variables in the respective porcelain documentation.
115 core.fileMode::
116 If false, the executable bit differences between the index and
117 the working copy are ignored; useful on broken filesystems like FAT.
118 See gitlink:git-update-index[1]. True by default.
120 core.quotepath::
121 The commands that output paths (e.g. `ls-files`,
122 `diff`), when not given the `-z` option, will quote
123 "unusual" characters in the pathname by enclosing the
124 pathname in a double-quote pair and with backslashes the
125 same way strings in C source code are quoted. If this
126 variable is set to false, the bytes higher than 0x80 are
127 not quoted but output as verbatim. Note that double
128 quote, backslash and control characters are always
129 quoted without `-z` regardless of the setting of this
130 variable.
132 core.autocrlf::
133 If true, makes git convert `CRLF` at the end of lines in text files to
134 `LF` when reading from the filesystem, and convert in reverse when
135 writing to the filesystem. The variable can be set to
136 'input', in which case the conversion happens only while
137 reading from the filesystem but files are written out with
138 `LF` at the end of lines. Currently, which paths to consider
139 "text" (i.e. be subjected to the autocrlf mechanism) is
140 decided purely based on the contents.
142 core.symlinks::
143 If false, symbolic links are checked out as small plain files that
144 contain the link text. gitlink:git-update-index[1] and
145 gitlink:git-add[1] will not change the recorded type to regular
146 file. Useful on filesystems like FAT that do not support
147 symbolic links. True by default.
149 core.gitProxy::
150 A "proxy command" to execute (as 'command host port') instead
151 of establishing direct connection to the remote server when
152 using the git protocol for fetching. If the variable value is
153 in the "COMMAND for DOMAIN" format, the command is applied only
154 on hostnames ending with the specified domain string. This variable
155 may be set multiple times and is matched in the given order;
156 the first match wins.
157 +
158 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
159 (which always applies universally, without the special "for"
160 handling).
162 core.ignoreStat::
163 The working copy files are assumed to stay unchanged until you
164 mark them otherwise manually - Git will not detect the file changes
165 by lstat() calls. This is useful on systems where those are very
166 slow, such as Microsoft Windows. See gitlink:git-update-index[1].
167 False by default.
169 core.preferSymlinkRefs::
170 Instead of the default "symref" format for HEAD
171 and other symbolic reference files, use symbolic links.
172 This is sometimes needed to work with old scripts that
173 expect HEAD to be a symbolic link.
175 core.bare::
176 If true this repository is assumed to be 'bare' and has no
177 working directory associated with it. If this is the case a
178 number of commands that require a working directory will be
179 disabled, such as gitlink:git-add[1] or gitlink:git-merge[1].
180 +
181 This setting is automatically guessed by gitlink:git-clone[1] or
182 gitlink:git-init[1] when the repository was created. By default a
183 repository that ends in "/.git" is assumed to be not bare (bare =
184 false), while all other repositories are assumed to be bare (bare
185 = true).
187 core.worktree::
188 Set the path to the working tree. The value will not be
189 used in combination with repositories found automatically in
190 a .git directory (i.e. $GIT_DIR is not set).
191 This can be overridden by the GIT_WORK_TREE environment
192 variable and the '--work-tree' command line option.
194 core.logAllRefUpdates::
195 Enable the reflog. Updates to a ref <ref> is logged to the file
196 "$GIT_DIR/logs/<ref>", by appending the new and old
197 SHA1, the date/time and the reason of the update, but
198 only when the file exists. If this configuration
199 variable is set to true, missing "$GIT_DIR/logs/<ref>"
200 file is automatically created for branch heads.
201 +
202 This information can be used to determine what commit
203 was the tip of a branch "2 days ago".
204 +
205 This value is true by default in a repository that has
206 a working directory associated with it, and false by
207 default in a bare repository.
209 core.repositoryFormatVersion::
210 Internal variable identifying the repository format and layout
211 version.
213 core.sharedRepository::
214 When 'group' (or 'true'), the repository is made shareable between
215 several users in a group (making sure all the files and objects are
216 group-writable). When 'all' (or 'world' or 'everybody'), the
217 repository will be readable by all users, additionally to being
218 group-shareable. When 'umask' (or 'false'), git will use permissions
219 reported by umask(2). See gitlink:git-init[1]. False by default.
221 core.warnAmbiguousRefs::
222 If true, git will warn you if the ref name you passed it is ambiguous
223 and might match multiple refs in the .git/refs/ tree. True by default.
225 core.compression::
226 An integer -1..9, indicating a default compression level.
227 -1 is the zlib default. 0 means no compression,
228 and 1..9 are various speed/size tradeoffs, 9 being slowest.
230 core.loosecompression::
231 An integer -1..9, indicating the compression level for objects that
232 are not in a pack file. -1 is the zlib default. 0 means no
233 compression, and 1..9 are various speed/size tradeoffs, 9 being
234 slowest. If not set, defaults to core.compression. If that is
235 not set, defaults to 0 (best speed).
237 core.packedGitWindowSize::
238 Number of bytes of a pack file to map into memory in a
239 single mapping operation. Larger window sizes may allow
240 your system to process a smaller number of large pack files
241 more quickly. Smaller window sizes will negatively affect
242 performance due to increased calls to the operating system's
243 memory manager, but may improve performance when accessing
244 a large number of large pack files.
245 +
246 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
247 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
248 be reasonable for all users/operating systems. You probably do
249 not need to adjust this value.
250 +
251 Common unit suffixes of 'k', 'm', or 'g' are supported.
253 core.packedGitLimit::
254 Maximum number of bytes to map simultaneously into memory
255 from pack files. If Git needs to access more than this many
256 bytes at once to complete an operation it will unmap existing
257 regions to reclaim virtual address space within the process.
258 +
259 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
260 This should be reasonable for all users/operating systems, except on
261 the largest projects. You probably do not need to adjust this value.
262 +
263 Common unit suffixes of 'k', 'm', or 'g' are supported.
265 core.deltaBaseCacheLimit::
266 Maximum number of bytes to reserve for caching base objects
267 that multiple deltafied objects reference. By storing the
268 entire decompressed base objects in a cache Git is able
269 to avoid unpacking and decompressing frequently used base
270 objects multiple times.
271 +
272 Default is 16 MiB on all platforms. This should be reasonable
273 for all users/operating systems, except on the largest projects.
274 You probably do not need to adjust this value.
275 +
276 Common unit suffixes of 'k', 'm', or 'g' are supported.
278 core.excludesfile::
279 In addition to '.gitignore' (per-directory) and
280 '.git/info/exclude', git looks into this file for patterns
281 of files which are not meant to be tracked. See
282 gitlink:gitignore[5].
284 core.editor::
285 Commands such as `commit` and `tag` that lets you edit
286 messages by launching an editor uses the value of this
287 variable when it is set, and the environment variable
288 `GIT_EDITOR` is not set. The order of preference is
289 `GIT_EDITOR` environment, `core.editor`, `VISUAL` and
290 `EDITOR` environment variables and then finally `vi`.
292 core.pager::
293 The command that git will use to paginate output. Can be overridden
294 with the `GIT_PAGER` environment variable.
296 core.whitespace::
297 A comma separated list of common whitespace problems to
298 notice. `git diff` will use `color.diff.whitespace` to
299 highlight them, and `git apply --whitespace=error` will
300 consider them as errors:
301 +
302 * `trailing-space` treats trailing whitespaces at the end of the line
303 as an error (enabled by default).
304 * `space-before-tab` treats a space character that appears immediately
305 before a tab character in the initial indent part of the line as an
306 error (enabled by default).
307 * `indent-with-non-tab` treats a line that is indented with 8 or more
308 space characters that can be replaced with tab characters.
310 alias.*::
311 Command aliases for the gitlink:git[1] command wrapper - e.g.
312 after defining "alias.last = cat-file commit HEAD", the invocation
313 "git last" is equivalent to "git cat-file commit HEAD". To avoid
314 confusion and troubles with script usage, aliases that
315 hide existing git commands are ignored. Arguments are split by
316 spaces, the usual shell quoting and escaping is supported.
317 quote pair and a backslash can be used to quote them.
318 +
319 If the alias expansion is prefixed with an exclamation point,
320 it will be treated as a shell command. For example, defining
321 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
322 "git new" is equivalent to running the shell command
323 "gitk --all --not ORIG_HEAD".
325 apply.whitespace::
326 Tells `git-apply` how to handle whitespaces, in the same way
327 as the '--whitespace' option. See gitlink:git-apply[1].
329 branch.autosetupmerge::
330 Tells `git-branch` and `git-checkout` to setup new branches
331 so that gitlink:git-pull[1] will appropriately merge from that
332 remote branch. Note that even if this option is not set,
333 this behavior can be chosen per-branch using the `--track`
334 and `--no-track` options. This option defaults to false.
336 branch.<name>.remote::
337 When in branch <name>, it tells `git fetch` which remote to fetch.
338 If this option is not given, `git fetch` defaults to remote "origin".
340 branch.<name>.merge::
341 When in branch <name>, it tells `git fetch` the default
342 refspec to be marked for merging in FETCH_HEAD. The value is
343 handled like the remote part of a refspec, and must match a
344 ref which is fetched from the remote given by
345 "branch.<name>.remote".
346 The merge information is used by `git pull` (which at first calls
347 `git fetch`) to lookup the default branch for merging. Without
348 this option, `git pull` defaults to merge the first refspec fetched.
349 Specify multiple values to get an octopus merge.
350 If you wish to setup `git pull` so that it merges into <name> from
351 another branch in the local repository, you can point
352 branch.<name>.merge to the desired branch, and use the special setting
353 `.` (a period) for branch.<name>.remote.
355 branch.<name>.mergeoptions::
356 Sets default options for merging into branch <name>. The syntax and
357 supported options are equal to that of gitlink:git-merge[1], but
358 option values containing whitespace characters are currently not
359 supported.
361 clean.requireForce::
362 A boolean to make git-clean do nothing unless given -f or -n. Defaults
363 to false.
365 color.branch::
366 A boolean to enable/disable color in the output of
367 gitlink:git-branch[1]. May be set to `true` (or `always`),
368 `false` (or `never`) or `auto`, in which case colors are used
369 only when the output is to a terminal. Defaults to false.
371 color.branch.<slot>::
372 Use customized color for branch coloration. `<slot>` is one of
373 `current` (the current branch), `local` (a local branch),
374 `remote` (a tracking branch in refs/remotes/), `plain` (other
375 refs).
376 +
377 The value for these configuration variables is a list of colors (at most
378 two) and attributes (at most one), separated by spaces. The colors
379 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
380 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
381 `blink` and `reverse`. The first color given is the foreground; the
382 second is the background. The position of the attribute, if any,
383 doesn't matter.
385 color.diff::
386 When true (or `always`), always use colors in patch.
387 When false (or `never`), never. When set to `auto`, use
388 colors only when the output is to the terminal.
390 color.diff.<slot>::
391 Use customized color for diff colorization. `<slot>` specifies
392 which part of the patch to use the specified color, and is one
393 of `plain` (context text), `meta` (metainformation), `frag`
394 (hunk header), `old` (removed lines), `new` (added lines),
395 `commit` (commit headers), or `whitespace` (highlighting
396 whitespace errors). The values of these variables may be specified as
397 in color.branch.<slot>.
399 color.pager::
400 A boolean to enable/disable colored output when the pager is in
401 use (default is true).
403 color.status::
404 A boolean to enable/disable color in the output of
405 gitlink:git-status[1]. May be set to `true` (or `always`),
406 `false` (or `never`) or `auto`, in which case colors are used
407 only when the output is to a terminal. Defaults to false.
409 color.status.<slot>::
410 Use customized color for status colorization. `<slot>` is
411 one of `header` (the header text of the status message),
412 `added` or `updated` (files which are added but not committed),
413 `changed` (files which are changed but not added in the index),
414 or `untracked` (files which are not tracked by git). The values of
415 these variables may be specified as in color.branch.<slot>.
417 commit.template::
418 Specify a file to use as the template for new commit messages.
420 diff.autorefreshindex::
421 When using `git diff` to compare with work tree
422 files, do not consider stat-only change as changed.
423 Instead, silently run `git update-index --refresh` to
424 update the cached stat information for paths whose
425 contents in the work tree match the contents in the
426 index. This option defaults to true. Note that this
427 affects only `git diff` Porcelain, and not lower level
428 `diff` commands, such as `git diff-files`.
430 diff.renameLimit::
431 The number of files to consider when performing the copy/rename
432 detection; equivalent to the git diff option '-l'.
434 diff.renames::
435 Tells git to detect renames. If set to any boolean value, it
436 will enable basic rename detection. If set to "copies" or
437 "copy", it will detect copies, as well.
439 fetch.unpackLimit::
440 If the number of objects fetched over the git native
441 transfer is below this
442 limit, then the objects will be unpacked into loose object
443 files. However if the number of received objects equals or
444 exceeds this limit then the received pack will be stored as
445 a pack, after adding any missing delta bases. Storing the
446 pack from a push can make the push operation complete faster,
447 especially on slow filesystems.
449 format.headers::
450 Additional email headers to include in a patch to be submitted
451 by mail. See gitlink:git-format-patch[1].
453 format.suffix::
454 The default for format-patch is to output files with the suffix
455 `.patch`. Use this variable to change that suffix (make sure to
456 include the dot if you want it).
458 gc.aggressiveWindow::
459 The window size parameter used in the delta compression
460 algorithm used by 'git gc --aggressive'. This defaults
461 to 10.
463 gc.auto::
464 When there are approximately more than this many loose
465 objects in the repository, `git gc --auto` will pack them.
466 Some Porcelain commands use this command to perform a
467 light-weight garbage collection from time to time. Setting
468 this to 0 disables it.
470 gc.autopacklimit::
471 When there are more than this many packs that are not
472 marked with `*.keep` file in the repository, `git gc
473 --auto` consolidates them into one larger pack. Setting
474 this to 0 disables this.
476 gc.packrefs::
477 `git gc` does not run `git pack-refs` in a bare repository by
478 default so that older dumb-transport clients can still fetch
479 from the repository. Setting this to `true` lets `git
480 gc` to run `git pack-refs`. Setting this to `false` tells
481 `git gc` never to run `git pack-refs`. The default setting is
482 `notbare`. Enable it only when you know you do not have to
483 support such clients. The default setting will change to `true`
484 at some stage, and setting this to `false` will continue to
485 prevent `git pack-refs` from being run from `git gc`.
487 gc.reflogexpire::
488 `git reflog expire` removes reflog entries older than
489 this time; defaults to 90 days.
491 gc.reflogexpireunreachable::
492 `git reflog expire` removes reflog entries older than
493 this time and are not reachable from the current tip;
494 defaults to 30 days.
496 gc.rerereresolved::
497 Records of conflicted merge you resolved earlier are
498 kept for this many days when `git rerere gc` is run.
499 The default is 60 days. See gitlink:git-rerere[1].
501 gc.rerereunresolved::
502 Records of conflicted merge you have not resolved are
503 kept for this many days when `git rerere gc` is run.
504 The default is 15 days. See gitlink:git-rerere[1].
506 rerere.enabled::
507 Activate recording of resolved conflicts, so that identical
508 conflict hunks can be resolved automatically, should they
509 be encountered again. See gitlink:git-rerere[1].
511 gitcvs.enabled::
512 Whether the CVS server interface is enabled for this repository.
513 See gitlink:git-cvsserver[1].
515 gitcvs.logfile::
516 Path to a log file where the CVS server interface well... logs
517 various stuff. See gitlink:git-cvsserver[1].
519 gitcvs.allbinary::
520 If true, all files are sent to the client in mode '-kb'. This
521 causes the client to treat all files as binary files which suppresses
522 any newline munging it otherwise might do. A work-around for the
523 fact that there is no way yet to set single files to mode '-kb'.
525 gitcvs.dbname::
526 Database used by git-cvsserver to cache revision information
527 derived from the git repository. The exact meaning depends on the
528 used database driver, for SQLite (which is the default driver) this
529 is a filename. Supports variable substitution (see
530 gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
531 Default: '%Ggitcvs.%m.sqlite'
533 gitcvs.dbdriver::
534 Used Perl DBI driver. You can specify any available driver
535 for this here, but it might not work. git-cvsserver is tested
536 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
537 reported *not* to work with 'DBD::mysql'. Experimental feature.
538 May not contain double colons (`:`). Default: 'SQLite'.
539 See gitlink:git-cvsserver[1].
541 gitcvs.dbuser, gitcvs.dbpass::
542 Database user and password. Only useful if setting 'gitcvs.dbdriver',
543 since SQLite has no concept of database users and/or passwords.
544 'gitcvs.dbuser' supports variable substitution (see
545 gitlink:git-cvsserver[1] for details).
547 All gitcvs variables except for 'gitcvs.allbinary' can also be
548 specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
549 is one of "ext" and "pserver") to make them apply only for the given
550 access method.
552 http.sslVerify::
553 Whether to verify the SSL certificate when fetching or pushing
554 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
555 variable.
557 http.sslCert::
558 File containing the SSL certificate when fetching or pushing
559 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
560 variable.
562 http.sslKey::
563 File containing the SSL private key when fetching or pushing
564 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
565 variable.
567 http.sslCAInfo::
568 File containing the certificates to verify the peer with when
569 fetching or pushing over HTTPS. Can be overridden by the
570 'GIT_SSL_CAINFO' environment variable.
572 http.sslCAPath::
573 Path containing files with the CA certificates to verify the peer
574 with when fetching or pushing over HTTPS. Can be overridden
575 by the 'GIT_SSL_CAPATH' environment variable.
577 http.maxRequests::
578 How many HTTP requests to launch in parallel. Can be overridden
579 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
581 http.lowSpeedLimit, http.lowSpeedTime::
582 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
583 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
584 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
585 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
587 http.noEPSV::
588 A boolean which disables using of EPSV ftp command by curl.
589 This can helpful with some "poor" ftp servers which don't
590 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
591 environment variable. Default is false (curl will use EPSV).
593 i18n.commitEncoding::
594 Character encoding the commit messages are stored in; git itself
595 does not care per se, but this information is necessary e.g. when
596 importing commits from emails or in the gitk graphical history
597 browser (and possibly at other places in the future or in other
598 porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
600 i18n.logOutputEncoding::
601 Character encoding the commit messages are converted to when
602 running `git-log` and friends.
604 log.showroot::
605 If true, the initial commit will be shown as a big creation event.
606 This is equivalent to a diff against an empty tree.
607 Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
608 normally hide the root commit will now show it. True by default.
610 merge.summary::
611 Whether to include summaries of merged commits in newly created
612 merge commit messages. False by default.
614 merge.tool::
615 Controls which merge resolution program is used by
616 gitlink:git-mergetool[1]. Valid values are: "kdiff3", "tkdiff",
617 "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
619 merge.verbosity::
620 Controls the amount of output shown by the recursive merge
621 strategy. Level 0 outputs nothing except a final error
622 message if conflicts were detected. Level 1 outputs only
623 conflicts, 2 outputs conflicts and file changes. Level 5 and
624 above outputs debugging information. The default is level 2.
625 Can be overridden by 'GIT_MERGE_VERBOSITY' environment variable.
627 merge.<driver>.name::
628 Defines a human readable name for a custom low-level
629 merge driver. See gitlink:gitattributes[5] for details.
631 merge.<driver>.driver::
632 Defines the command that implements a custom low-level
633 merge driver. See gitlink:gitattributes[5] for details.
635 merge.<driver>.recursive::
636 Names a low-level merge driver to be used when
637 performing an internal merge between common ancestors.
638 See gitlink:gitattributes[5] for details.
640 pack.window::
641 The size of the window used by gitlink:git-pack-objects[1] when no
642 window size is given on the command line. Defaults to 10.
644 pack.depth::
645 The maximum delta depth used by gitlink:git-pack-objects[1] when no
646 maximum depth is given on the command line. Defaults to 50.
648 pack.windowMemory::
649 The window memory size limit used by gitlink:git-pack-objects[1]
650 when no limit is given on the command line. The value can be
651 suffixed with "k", "m", or "g". Defaults to 0, meaning no
652 limit.
654 pack.compression::
655 An integer -1..9, indicating the compression level for objects
656 in a pack file. -1 is the zlib default. 0 means no
657 compression, and 1..9 are various speed/size tradeoffs, 9 being
658 slowest. If not set, defaults to core.compression. If that is
659 not set, defaults to -1.
661 pack.deltaCacheSize::
662 The maximum memory in bytes used for caching deltas in
663 gitlink:git-pack-objects[1].
664 A value of 0 means no limit. Defaults to 0.
666 pack.deltaCacheLimit::
667 The maximum size of a delta, that is cached in
668 gitlink:git-pack-objects[1]. Defaults to 1000.
670 pack.threads::
671 Specifies the number of threads to spawn when searching for best
672 delta matches. This requires that gitlink:git-pack-objects[1]
673 be compiled with pthreads otherwise this option is ignored with a
674 warning. This is meant to reduce packing time on multiprocessor
675 machines. The required amount of memory for the delta search window
676 is however multiplied by the number of threads.
678 pull.octopus::
679 The default merge strategy to use when pulling multiple branches
680 at once.
682 pull.twohead::
683 The default merge strategy to use when pulling a single branch.
685 remote.<name>.url::
686 The URL of a remote repository. See gitlink:git-fetch[1] or
687 gitlink:git-push[1].
689 remote.<name>.fetch::
690 The default set of "refspec" for gitlink:git-fetch[1]. See
691 gitlink:git-fetch[1].
693 remote.<name>.push::
694 The default set of "refspec" for gitlink:git-push[1]. See
695 gitlink:git-push[1].
697 remote.<name>.skipDefaultUpdate::
698 If true, this remote will be skipped by default when updating
699 using the remote subcommand of gitlink:git-remote[1].
701 remote.<name>.receivepack::
702 The default program to execute on the remote side when pushing. See
703 option \--exec of gitlink:git-push[1].
705 remote.<name>.uploadpack::
706 The default program to execute on the remote side when fetching. See
707 option \--exec of gitlink:git-fetch-pack[1].
709 remote.<name>.tagopt::
710 Setting this value to --no-tags disables automatic tag following when fetching
711 from remote <name>
713 remotes.<group>::
714 The list of remotes which are fetched by "git remote update
715 <group>". See gitlink:git-remote[1].
717 repack.usedeltabaseoffset::
718 Allow gitlink:git-repack[1] to create packs that uses
719 delta-base offset. Defaults to false.
721 show.difftree::
722 The default gitlink:git-diff-tree[1] arguments to be used
723 for gitlink:git-show[1].
725 showbranch.default::
726 The default set of branches for gitlink:git-show-branch[1].
727 See gitlink:git-show-branch[1].
729 tar.umask::
730 This variable can be used to restrict the permission bits of
731 tar archive entries. The default is 0002, which turns off the
732 world write bit. The special value "user" indicates that the
733 archiving user's umask will be used instead. See umask(2) and
734 gitlink:git-archive[1].
736 user.email::
737 Your email address to be recorded in any newly created commits.
738 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
739 'EMAIL' environment variables. See gitlink:git-commit-tree[1].
741 user.name::
742 Your full name to be recorded in any newly created commits.
743 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
744 environment variables. See gitlink:git-commit-tree[1].
746 user.signingkey::
747 If gitlink:git-tag[1] is not selecting the key you want it to
748 automatically when creating a signed tag, you can override the
749 default selection with this variable. This option is passed
750 unchanged to gpg's --local-user parameter, so you may specify a key
751 using any method that gpg supports.
753 whatchanged.difftree::
754 The default gitlink:git-diff-tree[1] arguments to be used
755 for gitlink:git-whatchanged[1].
757 imap::
758 The configuration variables in the 'imap' section are described
759 in gitlink:git-imap-send[1].
761 receive.unpackLimit::
762 If the number of objects received in a push is below this
763 limit then the objects will be unpacked into loose object
764 files. However if the number of received objects equals or
765 exceeds this limit then the received pack will be stored as
766 a pack, after adding any missing delta bases. Storing the
767 pack from a push can make the push operation complete faster,
768 especially on slow filesystems.
770 receive.denyNonFastForwards::
771 If set to true, git-receive-pack will deny a ref update which is
772 not a fast forward. Use this to prevent such an update via a push,
773 even if that push is forced. This configuration variable is
774 set when initializing a shared repository.
776 transfer.unpackLimit::
777 When `fetch.unpackLimit` or `receive.unpackLimit` are
778 not set, the value of this variable is used instead.