# phpman > man > git-config(1) > **TLDR:** Manage custom configuration options for Git repositories. > - Globally set your name or email (this information is required to commit to a repository and will be included in all commits): `git config --global {{user.name|user.email}} "{{Your Name|email@example.com}}"` - List local, global, or system configuration entries and show their file location: `git config --{{local|global|system}} {{-l|--list}} --show-origin` - Set the global value of a given configuration entry (in this case an alias): `git config --global {{alias.unstage}} "reset HEAD --"` - Get the value of a given configuration entry: `git config {{alias.unstage}}` - Use an alias: `git {{unstage}}` - Revert a global configuration entry to its default value: `git config --global --unset {{alias.unstage}}` - Edit the local Git configuration (`.git/config`) in the default editor: `git config {{-e|--edit}}` - Edit the global Git configuration (`~/.gitconfig` by default or `$XDG_CONFIG_HOME/git/config` if such a file exists) in the default editor: `git config --global {{-e|--edit}}` *Source: tldr-pages* --- [GIT-CONFIG(1)](https://www.chedong.com/phpMan.php/man/GIT-CONFIG/1/markdown) Git Manual [GIT-CONFIG(1)](https://www.chedong.com/phpMan.php/man/GIT-CONFIG/1/markdown) ## NAME git-config - Get and set repository or global options ## SYNOPSIS _git_ _config_ [] [--type=] [--fixed-value] [--show-origin] [--show-scope] [-z|--null] name [value [value-pattern]] _git_ _config_ [] [--type=] --add name value _git_ _config_ [] [--type=] [--fixed-value] --replace-all name value [value-pattern] _git_ _config_ [] [--type=] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get name [value-pattern] _git_ _config_ [] [--type=] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get-all name [value-pattern] _git_ _config_ [] [--type=] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] [--name-only] --get-regexp name_regex [value-pattern] _git_ _config_ [] [--type=] [-z|--null] --get-urlmatch name URL _git_ _config_ [] [--fixed-value] --unset name [value-pattern] _git_ _config_ [] [--fixed-value] --unset-all name [value-pattern] _git_ _config_ [] --rename-section old_name new_name _git_ _config_ [] --remove-section name _git_ _config_ [] [--show-origin] [--show-scope] [-z|--null] [--name-only] -l | --list _git_ _config_ [] --get-color name [default] _git_ _config_ [] --get-colorbool name [stdout-is-tty] _git_ _config_ [] -e | --edit ## DESCRIPTION You can query/set/replace/unset options with this command. The name is actually the section and the key separated by a dot, and the value will be escaped. Multiple lines can be added to an option by using the **--add** option. If you want to update or unset an option which can occur on multiple lines, a **value-pattern** (which is an extended regular expression, unless the **--fixed-value** option is given) needs to be given. Only the existing values that match the pattern are updated or unset. If you want to handle the lines that do **not** match the pattern, just prepend a single exclamation mark in front (see also the section called “EXAMPLES”), but note that this only works when the **--fixed-value** option is not in use. The **--type=** option instructs _git_ _config_ to ensure that incoming and outgoing values are canonicalize-able under the given . If no **--type=** is given, no canonicalization will be performed. Callers may unset an existing **--type** specifier with **--no-type**. When reading, the values are read from the system, global and repository local configuration files by default, and options **--system**, **--global**, **--local**, **--worktree** and **--file** **** can be used to tell the command to read from only that location (see the section called “FILES”). When writing, the new value is written to the repository local configuration file by default, and options **--system**, **--global**, **--worktree**, **--file** **** can be used to tell the command to write to that location (you can say **--local** but that is the default). This command will fail with non-zero status upon error. Some exit codes are: • The section or key is invalid (ret=1), • no section or name was provided (ret=2), • the config file is invalid (ret=3), • the config file cannot be written (ret=4), • you try to unset an option which does not exist (ret=5), • you try to unset/set an option for which multiple lines match (ret=5), or • you try to use an invalid regexp (ret=6). On success, the command returns the exit code 0. A list of all available configuration variables can be obtained using the **git** **help** **--config** command. ## OPTIONS ### --replace-all Default behavior is to replace at most one line. This replaces all lines matching the key (and optionally the **value-pattern**). ### --add Adds a new line to the option without altering any existing values. This is the same as providing _^$_ as the **value-pattern** in **--replace-all**. ### --get Get the value for a given key (optionally filtered by a regex matching the value). Returns error code 1 if the key was not found and the last value if multiple key values were found. ### --get-all Like get, but returns all values for a multi-valued key. ### --get-regexp Like --get-all, but interprets the name as a regular expression and writes out the key names. Regular expression matching is currently case-sensitive and done against a canonicalized version of the key in which section and variable names are lowercased, but subsection names are not. --get-urlmatch name URL When given a two-part name section.key, the value for section..key whose part matches the best to the given URL is returned (if no such key exists, the value for section.key is used as a fallback). When given just the section as name, do so for all the keys in the section and list them. Returns error code 1 if no value is found. ### --global For writing options: write to global **~/.gitconfig** file rather than the repository **.git/config**, write to **$XDG**___**CONFIG**___**HOME/git/config** file if this file exists and the **~/.gitconfig** file doesn’t. For reading options: read only from global **~/.gitconfig** and from **$XDG**___**CONFIG**___**HOME/git/config** rather than from all available files. See also the section called “FILES”. ### --system For writing options: write to system-wide **$(prefix)/etc/gitconfig** rather than the repository **.git/config**. For reading options: read only from system-wide **$(prefix)/etc/gitconfig** rather than from all available files. See also the section called “FILES”. ### --local For writing options: write to the repository **.git/config** file. This is the default behavior. For reading options: read only from the repository **.git/config** rather than from all available files. See also the section called “FILES”. ### --worktree Similar to **--local** except that **.git/config.worktree** is read from or written to if **extensions.worktreeConfig** is present. If not it’s the same as **--local**. -f config-file, --file config-file For writing options: write to the specified file rather than the repository **.git/config**. For reading options: read only from the specified file rather than from all available files. See also the section called “FILES”. --blob blob Similar to **--file** but use the given blob instead of a file. E.g. you can use _master:.gitmodules_ to read values from the file _.gitmodules_ in the master branch. See "SPECIFYING REVISIONS" section in [**gitrevisions**(7)](https://www.chedong.com/phpMan.php/man/gitrevisions/7/markdown) for a more complete list of ways to spell blob names. ### --remove-section Remove the given section from the configuration file. ### --rename-section Rename the given section to a new name. ### --unset Remove the line matching the key from config file. ### --unset-all Remove all lines matching the key from config file. ### -l, --list List all variables set in config file, along with their values. ### --fixed-value When used with the **value-pattern** argument, treat **value-pattern** as an exact string instead of a regular expression. This will restrict the name/value pairs that are matched to only those where the value is exactly equal to the **value-pattern**. ### --type _git_ _config_ will ensure that any input or output is valid under the given type constraint(s), and will canonicalize outgoing values in ****'s canonical form. Valid ****'s include: • _bool_: canonicalize values as either "true" or "false". • _int_: canonicalize values as simple decimal numbers. An optional suffix of _k_, _m_, or _g_ will cause the value to be multiplied by 1024, 1048576, or 1073741824 upon input. • _bool-or-int_: canonicalize according to either _bool_ or _int_, as described above. • _path_: canonicalize by adding a leading **~** to the value of **$HOME** and **~user** to the home directory for the specified user. This specifier has no effect when setting the value (but you can use **git** **config** **section.variable** **~/** from the command line to let your shell do the expansion.) • _expiry-date_: canonicalize by converting from a fixed or relative date-string to a timestamp. This specifier has no effect when setting the value. • _color_: When getting a value, canonicalize by converting to an ANSI color escape sequence. When setting a value, a sanity-check is performed to ensure that the given value is canonicalize-able as an ANSI color, but it is written as-is. ### --bool, --int, --bool-or-int, --path, --expiry-date Historical options for selecting a type specifier. Prefer instead **--type** (see above). ### --no-type Un-sets the previously set type specifier (if one was previously set). This option requests that _git_ _config_ not canonicalize the retrieved variable. **--no-type** has no effect without **--type=** or **--**. ### -z, --null For all options that output values and/or keys, always end values with the null character (instead of a newline). Use newline instead as a delimiter between key and value. This allows for secure parsing of the output without getting confused e.g. by values that contain line breaks. ### --name-only Output only the names of config variables for **--list** or **--get-regexp**. ### --show-origin Augment the output of all queried config options with the origin type (file, standard input, blob, command line) and the actual origin (config file path, ref, or blob id if applicable). ### --show-scope Similar to **--show-origin** in that it augments the output of all queried config options with the scope of that value (local, global, system, command). --get-colorbool name [stdout-is-tty] Find the color setting for **name** (e.g. **color.diff**) and output "true" or "false". **stdout-is-tty** should be either "true" or "false", and is taken into account when configuration says "auto". If **stdout-is-tty** is missing, then checks the standard output of the command itself, and exits with status 0 if color is to be used, or exits with status 1 otherwise. When the color setting for **name** is undefined, the command uses **color.ui** as fallback. --get-color name [default] Find the color configured for **name** (e.g. **color.diff.new**) and output it as the ANSI color escape sequence to the standard output. The optional **default** parameter is used instead, if there is no color configured for **name**. **--type=color** **[--default=]** is preferred over **--get-color** (but note that **--get-color** will omit the trailing newline printed by **--type=color**). ### -e, --edit Opens an editor to modify the specified config file; either **--system**, **--global**, or repository (default). --[no-]includes Respect **include.*** directives in config files when looking up values. Defaults to **off** when a specific file is given (e.g., using **--file**, **--global**, etc) and **on** when searching all config files. ### --default When using **--get**, and the requested variable is not found, behave as if were the value assigned to the that variable. ## CONFIGURATION **pager.config** is only respected when listing configuration, i.e., when using **--list** or any of the **--get-*** which may return multiple results. The default is to use a pager. ## FILES If not set explicitly with **--file**, there are four files where _git_ _config_ will search for configuration options: $(prefix)/etc/gitconfig System-wide configuration file. $XDG_CONFIG_HOME/git/config Second user-specific configuration file. If $XDG_CONFIG_HOME is not set or empty, **$HOME/.config/git/config** will be used. Any single-valued variable set in this file will be overwritten by whatever is in **~/.gitconfig**. It is a good idea not to create this file if you sometimes use older versions of Git, as support for this file was added fairly recently. ~/.gitconfig User-specific configuration file. Also called "global" configuration file. $GIT_DIR/config Repository specific configuration file. $GIT_DIR/config.worktree This is optional and is only searched when **extensions.worktreeConfig** is present in $GIT_DIR/config. If no further options are given, all reading options will read all of these files that are available. If the global or the system-wide configuration file are not available they will be ignored. If the repository configuration file is not available or readable, _git_ _config_ will exit with a non-zero error code. However, in neither case will an error message be issued. The files are read in the order given above, with last value found taking precedence over values read earlier. When multiple values are taken then all values of a key from all files will be used. You may override individual configuration parameters when running any git command by using the **-c** option. See [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) for details. All writing options will per default write to the repository specific configuration file. Note that this also affects options like **--replace-all** and **--unset**. _git_ _config_ **will** **only** **ever** **change** **one** **file** **at** **a** **time**. You can override these rules using the **--global**, **--system**, **--local**, **--worktree**, and **--file** command-line options; see the section called “OPTIONS” above. ## ENVIRONMENT GIT_CONFIG_GLOBAL, GIT_CONFIG_SYSTEM Take the configuration from the given files instead from global or system-level configuration. See [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) for details. GIT_CONFIG_NOSYSTEM Whether to skip reading settings from the system-wide $(prefix)/etc/gitconfig file. See [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) for details. See also the section called “FILES”. GIT_CONFIG_COUNT, GIT_CONFIG_KEY_, GIT_CONFIG_VALUE_ If GIT_CONFIG_COUNT is set to a positive number, all environment pairs GIT_CONFIG_KEY_ and GIT_CONFIG_VALUE_ up to that number will be added to the process’s runtime configuration. The config pairs are zero-indexed. Any missing key or value is treated as an error. An empty GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0, namely no pairs are processed. These environment variables will override values in configuration files, but will be overridden by any explicit options passed via **git** **-c**. This is useful for cases where you want to spawn multiple git commands with a common configuration but cannot depend on a configuration file, for example when writing scripts. GIT_CONFIG If no **--file** option is provided to **git** **config**, use the file given by **GIT**___**CONFIG** as if it were provided via **--file**. This variable has no effect on other Git commands, and is mostly for historical compatibility; there is generally no reason to use it instead of the **--file** option. ## EXAMPLES Given a .git/config like this: # # This is the config file, and # a '#' or ';' character indicates # a comment # ; core variables [core] ; Don't trust file modes filemode = false ; Our diff algorithm [diff] external = /usr/local/bin/diff-wrapper renames = true ; Proxy settings [core] gitproxy=proxy-command for kernel.org gitproxy=default-proxy ; for all the rest ; HTTP [http] sslVerify [http ""] sslVerify = false cookieFile = /tmp/cookie.txt you can set the filemode to true with % git config core.filemode true The hypothetical proxy command entries actually have a postfix to discern what URL they apply to. Here is how to change the entry for kernel.org to "ssh". % git config core.gitproxy '"ssh" for kernel.org' 'for kernel.org$' This makes sure that only the key/value pair for kernel.org is replaced. To delete the entry for renames, do % git config --unset diff.renames If you want to delete an entry for a multivar (like core.gitproxy above), you have to provide a regex matching the value of exactly one line. To query the value for a given key, do % git config --get core.filemode or % git config core.filemode or, to query a multivar: % git config --get core.gitproxy "for kernel.org$" If you want to know all the values for a multivar, do: % git config --get-all core.gitproxy If you like to live dangerously, you can replace **all** core.gitproxy by a new one with % git config --replace-all core.gitproxy ssh However, if you really only want to replace the line for the default proxy, i.e. the one without a "for ..." postfix, do something like this: % git config core.gitproxy ssh '! for ' To actually match only values with an exclamation mark, you have to % git config section.key value '[!]' To add a new proxy, without altering any of the existing ones, use % git config --add core.gitproxy '"proxy-command" for example.com' An example to use customized color from the configuration in your script: #!/bin/sh WS=$(git config --get-color color.diff.whitespace "blue reverse") RESET=$(git config --get-color "" "reset") echo "${WS}your whitespace color or blue reverse${RESET}" For URLs in ****, **http.sslVerify** is set to false, while it is set to **true** for all others: % git config --type=bool --get-urlmatch http.sslverify true % git config --type=bool --get-urlmatch http.sslverify false % git config --get-urlmatch http http.cookieFile /tmp/cookie.txt http.sslverify false ## CONFIGURATION FILE The Git configuration file contains a number of variables that affect the Git commands' behavior. The files **.git/config** and optionally **config.worktree** (see the "CONFIGURATION FILE" section of [**git-worktree**(1)](https://www.chedong.com/phpMan.php/man/git-worktree/1/markdown)) in each repository are used to store the configuration for that repository, and **$HOME/.gitconfig** is used to store a per-user configuration as fallback values for the **.git/config** file. The file **/etc/gitconfig** can be used to store a system-wide default configuration. The configuration variables are used by both the Git plumbing and the porcelains. The variables are divided into sections, wherein the fully qualified variable name of the variable itself is the last dot-separated segment and the section name is everything before the last dot. The variable names are case-insensitive, allow only alphanumeric characters and **-**, and must start with an alphabetic character. Some variables may appear multiple times; we say then that the variable is multivalued. ### Syntax The syntax is fairly flexible and permissive; whitespaces are mostly ignored. The _#_ and _;_ characters begin comments to the end of line, blank lines are ignored. The file consists of sections and variables. A section begins with the name of the section in square brackets and continues until the next section begins. Section names are case-insensitive. Only alphanumeric characters, **-** and **.** are allowed in section names. Each variable must belong to some section, which means that there must be a section header before the first setting of a variable. Sections can be further divided into subsections. To begin a subsection put its name in double quotes, separated by space from the section name, in the section header, like in the example below: [section "subsection"] Subsection names are case sensitive and can contain any characters except newline and the null byte. Doublequote **"** and backslash can be included by escaping them as **\"** and **\\**, respectively. Backslashes preceding other characters are dropped when reading; for example, **\t** is read as **t** and **\0** is read as **0**. Section headers cannot span multiple lines. Variables may belong directly to a section or to a given subsection. You can have **[section]** if you have **[section** **"subsection"]**, but you don’t need to. There is also a deprecated **[section.subsection]** syntax. With this syntax, the subsection name is converted to lower-case and is also compared case sensitively. These subsection names follow the same restrictions as section names. All the other lines (and the remainder of the line after the section header) are recognized as setting variables, in the form _name_ _=_ _value_ (or just _name_, which is a short-hand to say that the variable is the boolean "true"). The variable names are case-insensitive, allow only alphanumeric characters and **-**, and must start with an alphabetic character. A line that defines a value can be continued to the next line by ending it with a **\**; the backslash and the end-of-line are stripped. Leading whitespaces after _name_ _=_, the remainder of the line after the first comment character _#_ or _;_, and trailing whitespaces of the line are discarded unless they are enclosed in double quotes. Internal whitespaces within the value are retained verbatim. Inside double quotes, double quote **"** and backslash **\** characters must be escaped: use **\"** for **"** and **\\** for **\**. The following escape sequences (beside **\"** and **\\**) are recognized: **\n** for newline character (NL), **\t** for horizontal tabulation (HT, TAB) and **\b** for backspace (BS). Other char escape sequences (including octal escape sequences) are invalid. ### Includes The **include** and **includeIf** sections allow you to include config directives from another source. These sections behave identically to each other with the exception that **includeIf** sections may be ignored if their condition does not evaluate to true; see "Conditional includes" below. You can include a config file from another by setting the special **include.path** (or **includeIf.*.path**) variable to the name of the file to be included. The variable takes a pathname as its value, and is subject to tilde expansion. These variables can be given multiple times. The contents of the included file are inserted immediately, as if they had been found at the location of the include directive. If the value of the variable is a relative path, the path is considered to be relative to the configuration file in which the include directive was found. See below for examples. ### Conditional includes You can include a config file from another conditionally by setting a **includeIf..path** variable to the name of the file to be included. The condition starts with a keyword followed by a colon and some data whose format and meaning depends on the keyword. Supported keywords are: ### gitdir The data that follows the keyword **gitdir:** is used as a glob pattern. If the location of the .git directory matches the pattern, the include condition is met. The .git location may be auto-discovered, or come from **$GIT**___**DIR** environment variable. If the repository is auto discovered via a .git file (e.g. from submodules, or a linked worktree), the .git location would be the final location where the .git directory is, not where the .git file is. The pattern can contain standard globbing wildcards and two additional ones, ****/** and **/****, that can match multiple path components. Please refer to [**gitignore**(5)](https://www.chedong.com/phpMan.php/man/gitignore/5/markdown) for details. For convenience: • If the pattern starts with **~/**, **~** will be substituted with the content of the environment variable **HOME**. • If the pattern starts with **./**, it is replaced with the directory containing the current config file. • If the pattern does not start with either **~/**, **./** or **/**, ****/** will be automatically prepended. For example, the pattern **foo/bar** becomes ****/foo/bar** and would match **/any/path/to/foo/bar**. • If the pattern ends with **/**, ****** will be automatically added. For example, the pattern **foo/** becomes **foo/****. In other words, it matches "foo" and everything inside, recursively. ### gitdir/i This is the same as **gitdir** except that matching is done case-insensitively (e.g. on case-insensitive file systems) ### onbranch The data that follows the keyword **onbranch:** is taken to be a pattern with standard globbing wildcards and two additional ones, ****/** and **/****, that can match multiple path components. If we are in a worktree where the name of the branch that is currently checked out matches the pattern, the include condition is met. If the pattern ends with **/**, ****** will be automatically added. For example, the pattern **foo/** becomes **foo/****. In other words, it matches all branches that begin with **foo/**. This is useful if your branches are organized hierarchically and you would like to apply a configuration to all the branches in that hierarchy. A few more notes on matching via **gitdir** and **gitdir/i**: • Symlinks in **$GIT**___**DIR** are not resolved before matching. • Both the symlink & realpath versions of paths will be matched outside of **$GIT**___**DIR**. E.g. if ~/git is a symlink to /mnt/storage/git, both **gitdir:~/git** and **gitdir:/mnt/storage/git** will match. This was not the case in the initial release of this feature in v2.13.0, which only matched the realpath version. Configuration that wants to be compatible with the initial release of this feature needs to either specify only the realpath version, or both versions. • Note that "../" is not special and will match literally, which is unlikely what you want. ### Example # Core variables [core] ; Don't trust file modes filemode = false # Our diff algorithm [diff] external = /usr/local/bin/diff-wrapper renames = true [branch "devel"] remote = origin merge = refs/heads/devel # Proxy settings [core] gitProxy="ssh" for "kernel.org" gitProxy=default-proxy ; for the rest [include] path = /path/to/foo.inc ; include by absolute path path = foo.inc ; find "foo.inc" relative to the current file path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory ; include if $GIT_DIR is /path/to/foo/.git [includeIf "gitdir:/path/to/foo/.git"] path = /path/to/foo.inc ; include for all repositories inside /path/to/group [includeIf "gitdir:/path/to/group/"] path = /path/to/foo.inc ; include for all repositories inside $HOME/to/group [includeIf "gitdir:~/to/group/"] path = /path/to/foo.inc ; relative paths are always relative to the including ; file (if the condition is true); their location is not ; affected by the condition [includeIf "gitdir:/path/to/group/"] path = foo.inc ; include only if we are in a worktree where foo-branch is ; currently checked out [includeIf "onbranch:foo-branch"] path = foo.inc ### Values Values of many variables are treated as a simple string, but there are variables that take values of specific types and there are rules as to how to spell them. boolean When a variable is said to take a boolean value, many synonyms are accepted for _true_ and _false_; these are all case-insensitive. true Boolean true literals are **yes**, **on**, **true**, and **1**. Also, a variable defined without **=** **** is taken as true. false Boolean false literals are **no**, **off**, **false**, **0** and the empty string. When converting a value to its canonical form using the **--type=bool** type specifier, _git_ _config_ will ensure that the output is "true" or "false" (spelled in lowercase). integer The value for many variables that specify various sizes can be suffixed with **k**, **M**,... to mean "scale the number by 1024", "by 1024x1024", etc. color The value for a variable that takes a color is a list of colors (at most two, one for foreground and one for background) and attributes (as many as you want), separated by spaces. The basic colors accepted are **normal**, **black**, **red**, **green**, **yellow**, **blue**, **magenta**, **cyan** and **white**. The first color given is the foreground; the second is the background. All the basic colors except **normal** have a bright variant that can be specified by prefixing the color with **bright**, like **brightred**. Colors may also be given as numbers between 0 and 255; these use ANSI 256-color mode (but note that not all terminals may support this). If your terminal supports it, you may also specify 24-bit RGB values as hex, like **#ff0ab3**. The accepted attributes are **bold**, **dim**, **ul**, **blink**, **reverse**, **italic**, and **strike** (for crossed-out or "strikethrough" letters). The position of any attributes with respect to the colors (before, after, or in between), doesn’t matter. Specific attributes may be turned off by prefixing them with **no** or **no-** (e.g., **noreverse**, **no-ul**, etc). An empty color string produces no color effect at all. This can be used to avoid coloring specific elements without disabling color entirely. For git’s pre-defined color slots, the attributes are meant to be reset at the beginning of each item in the colored output. So setting **color.decorate.branch** to **black** will paint that branch name in a plain **black**, even if the previous thing on the same output line (e.g. opening parenthesis before the list of branch names in **log** **--decorate** output) is set to be painted with **bold** or some other attribute. However, custom log formats may do more complicated and layered coloring, and the negated forms may be useful there. pathname A variable that takes a pathname value can be given a string that begins with "**~/**" or "**~user/**", and the usual tilde expansion happens to such a string: **~/** is expanded to the value of **$HOME**, and **~user/** to the specified user’s home directory. If a path starts with **%(prefix)/**, the remainder is interpreted as a path relative to Git’s "runtime prefix", i.e. relative to the location where Git itself was installed. For example, **%(prefix)/bin/** refers to the directory in which the Git executable itself lives. If Git was compiled without runtime prefix support, the compiled-in prefix will be substituted instead. In the unlikely event that a literal path needs to be specified that should _not_ be expanded, it needs to be prefixed by **./**, like so: **./%(prefix)/bin**. ### Variables Note that this list is non-comprehensive and not necessarily complete. For command-specific variables, you will find a more detailed description in the appropriate manual page. Other git-related tools may and do use their own variables. When inventing new variables for use in your own tool, make sure their names do not conflict with those that are used by Git itself and other popular tools, and describe them in your documentation. advice.* These variables control various optional help messages designed to aid new users. All _advice.*_ variables default to _true_, and you can tell Git that you do not need help by setting these to _false_: fetchShowForcedUpdates Advice shown when [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown) takes a long time to calculate forced updates after ref updates, or to warn that the check is disabled. pushUpdateRejected Set this variable to _false_ if you want to disable _pushNonFFCurrent_, _pushNonFFMatching_, _pushAlreadyExists_, _pushFetchFirst_, _pushNeedsForce_, and _pushRefNeedsUpdate_ simultaneously. pushNonFFCurrent Advice shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) fails due to a non-fast-forward update to the current branch. pushNonFFMatching Advice shown when you ran [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) and pushed _matching_ _refs_ explicitly (i.e. you used _:_, or specified a refspec that isn’t your current branch) and it resulted in a non-fast-forward error. pushAlreadyExists Shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) rejects an update that does not qualify for fast-forwarding (e.g., a tag.) pushFetchFirst Shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) rejects an update that tries to overwrite a remote ref that points at an object we do not have. pushNeedsForce Shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) rejects an update that tries to overwrite a remote ref that points at an object that is not a commit-ish, or make the remote ref point at an object that is not a commit-ish. pushUnqualifiedRefname Shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) gives up trying to guess based on the source and destination refs what remote ref namespace the source belongs in, but where we can still suggest that the user push to either refs/heads/* or refs/tags/* based on the type of the source object. pushRefNeedsUpdate Shown when [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown) rejects a forced update of a branch when its remote-tracking ref has updates that we do not have locally. skippedCherryPicks Shown when [**git-rebase**(1)](https://www.chedong.com/phpMan.php/man/git-rebase/1/markdown) skips a commit that has already been cherry-picked onto the upstream branch. statusAheadBehind Shown when [**git-status**(1)](https://www.chedong.com/phpMan.php/man/git-status/1/markdown) computes the ahead/behind counts for a local ref compared to its remote tracking ref, and that calculation takes longer than expected. Will not appear if **status.aheadBehind** is false or the option **--no-ahead-behind** is given. statusHints Show directions on how to proceed from the current state in the output of **git-** [**status**(1)](https://www.chedong.com/phpMan.php/man/status/1/markdown), in the template shown when writing commit messages in [**git-commit**(1)](https://www.chedong.com/phpMan.php/man/git-commit/1/markdown), and in the help message shown by [**git-switch**(1)](https://www.chedong.com/phpMan.php/man/git-switch/1/markdown) or [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown) when switching branch. statusUoption Advise to consider using the **-u** option to [**git-status**(1)](https://www.chedong.com/phpMan.php/man/git-status/1/markdown) when the command takes more than 2 seconds to enumerate untracked files. commitBeforeMerge Advice shown when [**git-merge**(1)](https://www.chedong.com/phpMan.php/man/git-merge/1/markdown) refuses to merge to avoid overwriting local changes. resetQuiet Advice to consider using the **--quiet** option to [**git-reset**(1)](https://www.chedong.com/phpMan.php/man/git-reset/1/markdown) when the command takes more than 2 seconds to enumerate unstaged changes after reset. resolveConflict Advice shown by various commands when conflicts prevent the operation from being performed. sequencerInUse Advice shown when a sequencer command is already in progress. implicitIdentity Advice on how to set your identity configuration when your information is guessed from the system username and domain name. detachedHead Advice shown when you used [**git-switch**(1)](https://www.chedong.com/phpMan.php/man/git-switch/1/markdown) or [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown) to move to the detach HEAD state, to instruct how to create a local branch after the fact. checkoutAmbiguousRemoteBranchName Advice shown when the argument to [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown) and [**git-switch**(1)](https://www.chedong.com/phpMan.php/man/git-switch/1/markdown) ambiguously resolves to a remote tracking branch on more than one remote in situations where an unambiguous argument would have otherwise caused a remote-tracking branch to be checked out. See the **checkout.defaultRemote** configuration variable for how to set a given remote to used by default in some situations where this advice would be printed. amWorkDir Advice that shows the location of the patch file when [**git-am**(1)](https://www.chedong.com/phpMan.php/man/git-am/1/markdown) fails to apply it. rmHints In case of failure in the output of [**git-rm**(1)](https://www.chedong.com/phpMan.php/man/git-rm/1/markdown), show directions on how to proceed from the current state. addEmbeddedRepo Advice on what to do when you’ve accidentally added one git repo inside of another. ignoredHook Advice shown if a hook is ignored because the hook is not set as executable. waitingForEditor Print a message to the terminal whenever Git is waiting for editor input from the user. nestedTag Advice shown if a user attempts to recursively tag a tag object. submoduleAlternateErrorStrategyDie Advice shown when a submodule.alternateErrorStrategy option configured to "die" causes a fatal error. addIgnoredFile Advice shown if a user attempts to add an ignored file to the index. addEmptyPathspec Advice shown if a user runs the add command without providing the pathspec parameter. updateSparsePath Advice shown when either [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown) or [**git-rm**(1)](https://www.chedong.com/phpMan.php/man/git-rm/1/markdown) is asked to update index entries outside the current sparse checkout. core.fileMode Tells Git if the executable bit of files in the working tree is to be honored. Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown) or [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary. A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to _true_ when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to _false_. See [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown). The default is true (when core.filemode is not specified in the config file). core.hideDotFiles (Windows-only) If true, mark newly-created directories and files whose name starts with a dot as hidden. If _dotGitOnly_, only the **.git/** directory is hidden, but no other files starting with a dot. The default mode is _dotGitOnly_. core.ignoreCase Internal variable which enables various workarounds to enable Git to work better on filesystems that are not case sensitive, like APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing finds "makefile" when Git expects "Makefile", Git will assume it is really the same file, and continue to remember it as "Makefile". The default is false, except [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown) or [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown) will probe and set core.ignoreCase true if appropriate when the repository is created. Git relies on the proper configuration of this variable for your operating and file system. Modifying this value may result in unexpected behavior. core.precomposeUnicode This option is only used by Mac OS implementation of Git. When core.precomposeUnicode=true, Git reverts the unicode decomposition of filenames done by Mac OS. This is useful when sharing a repository between Mac OS and Linux or Windows. (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). When false, file names are handled fully transparent by Git, which is backward compatible with older versions of Git. core.protectHFS If set to true, do not allow checkout of paths that would be considered equivalent to **.git** on an HFS+ filesystem. Defaults to **true** on Mac OS, and **false** elsewhere. core.protectNTFS If set to true, do not allow checkout of paths that would cause problems with the NTFS filesystem, e.g. conflict with 8.3 "short" names. Defaults to **true** on Windows, and **false** elsewhere. core.fsmonitor If set, the value of this variable is used as a command which will identify all files that may have changed since the requested date/time. This information is used to speed up git by avoiding unnecessary processing of files that have not changed. See the "fsmonitor-watchman" section of [**githooks**(5)](https://www.chedong.com/phpMan.php/man/githooks/5/markdown). core.fsmonitorHookVersion Sets the version of hook that is to be used when calling fsmonitor. There are currently versions 1 and 2. When this is not set, version 2 will be tried first and if it fails then version 1 will be tried. Version 1 uses a timestamp as input to determine which files have changes since that time but some monitors like watchman have race conditions when used with a timestamp. Version 2 uses an opaque string so that the monitor can return something that can be used to determine what files have changed without race conditions. core.trustctime If false, the ctime differences between the index and the working tree are ignored; useful when the inode change time is regularly modified by something outside Git (file system crawlers and some backup systems). See [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown). True by default. core.splitIndex If true, the split-index feature of the index will be used. See [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown). False by default. core.untrackedCache Determines what to do about the untracked cache feature of the index. It will be kept, if this variable is unset or set to **keep**. It will automatically be added if set to **true**. And it will automatically be removed, if set to **false**. Before setting it to **true**, you should check that mtime is working properly on your system. See [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown). **keep** by default, unless **feature.manyFiles** is enabled which sets this setting to **true** by default. core.checkStat When missing or is set to **default**, many fields in the stat structure are checked to detect if a file has been modified since Git looked at it. When this configuration variable is set to **minimal**, sub-second part of mtime and ctime, the uid and gid of the owner of the file, the inode number (and the device number, if Git was compiled to use it), are excluded from the check among these fields, leaving only the whole-second part of mtime (and ctime, if **core.trustCtime** is set) and the filesize to be checked. There are implementations of Git that do not leave usable values in some fields (e.g. JGit); by excluding these fields from the comparison, the **minimal** mode may help interoperability when the same repository is used by these other systems at the same time. core.quotePath Commands that output paths (e.g. _ls-files_, _diff_), will quote "unusual" characters in the pathname by enclosing the pathname in double-quotes and escaping those characters with backslashes in the same way C escapes control characters (e.g. **\t** for TAB, **\n** for LF, **\\** for backslash) or bytes with values larger than 0x80 (e.g. octal **\302\265** for "micro" in UTF-8). If this variable is set to false, bytes higher than 0x80 are not considered "unusual" any more. Double-quotes, backslash and control characters are always escaped regardless of the setting of this variable. A simple space character is not considered "unusual". Many commands can output pathnames completely verbatim using the **-z** option. The default value is true. core.eol Sets the line ending type to use in the working directory for files that are marked as text (either by having the **text** attribute set, or by having **text=auto** and Git auto-detecting the contents as text). Alternatives are _lf_, _crlf_ and _native_, which uses the platform’s native line ending. The default value is **native**. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for more information on end-of-line conversion. Note that this value is ignored if **core.autocrlf** is set to **true** or **input**. core.safecrlf If true, makes Git check if converting **CRLF** is reversible when end-of-line conversion is active. Git will verify if a command modifies a file in the work tree either directly or indirectly. For example, committing a file followed by checking out the same file should yield the original file in the work tree. If this is not the case for the current setting of **core.autocrlf**, Git will reject the file. The variable can be set to "warn", in which case Git will only warn about an irreversible conversion but continue the operation. CRLF conversion bears a slight chance of corrupting data. When it is enabled, Git will convert CRLF to LF during commit and LF to CRLF during checkout. A file that contains a mixture of LF and CRLF before the commit cannot be recreated by Git. For text files this is the right thing to do: it corrects line endings such that we have only LF line endings in the repository. But for binary files that are accidentally classified as text the conversion can corrupt data. If you recognize such corruption early you can easily fix it by setting the conversion type explicitly in .gitattributes. Right after committing you still have the original file in your work tree and this file is not yet corrupted. You can explicitly tell Git that this file is binary and Git will handle the file appropriately. Unfortunately, the desired effect of cleaning up text files with mixed line endings and the undesired effect of corrupting binary files cannot be distinguished. In both cases CRLFs are removed in an irreversible way. For text files this is the right thing to do because CRLFs are line endings, while for binary files converting CRLFs corrupts data. Note, this safety check does not mean that a checkout will generate a file identical to the original file for a different setting of **core.eol** and **core.autocrlf**, but only for the current one. For example, a text file with **LF** would be accepted with **core.eol=lf** and could later be checked out with **core.eol=crlf**, in which case the resulting file would contain **CRLF**, although the original file contained **LF**. However, in both work trees the line endings would be consistent, that is either all **LF** or all **CRLF**, but never mixed. A file with mixed line endings would be reported by the **core.safecrlf** mechanism. core.autocrlf Setting this variable to "true" is the same as setting the **text** attribute to "auto" on all files and core.eol to "crlf". Set to true if you want to have **CRLF** line endings in your working directory and the repository has LF line endings. This variable can be set to _input_, in which case no output conversion is performed. core.checkRoundtripEncoding A comma and/or whitespace separated list of encodings that Git performs UTF-8 round trip checks on if they are used in an **working-tree-encoding** attribute (see [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown)). The default value is **SHIFT-JIS**. core.symlinks If false, symbolic links are checked out as small plain files that contain the link text. [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown) and [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown) will not change the recorded type to regular file. Useful on filesystems like FAT that do not support symbolic links. The default is true, except [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown) or [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown) will probe and set core.symlinks false if appropriate when the repository is created. core.gitProxy A "proxy command" to execute (as _command_ _host_ _port_) instead of establishing direct connection to the remote server when using the Git protocol for fetching. If the variable value is in the "COMMAND for DOMAIN" format, the command is applied only on hostnames ending with the specified domain string. This variable may be set multiple times and is matched in the given order; the first match wins. Can be overridden by the **GIT**___**PROXY**___**COMMAND** environment variable (which always applies universally, without the special "for" handling). The special string **none** can be used as the proxy command to specify that no proxy be used for a given domain pattern. This is useful for excluding servers inside a firewall from proxy use, while defaulting to a common proxy for external domains. core.sshCommand If this variable is set, **git** **fetch** and **git** **push** will use the specified command instead of **ssh** when they need to connect to a remote system. The command is in the same form as the **GIT**___**SSH**___**COMMAND** environment variable and is overridden when the environment variable is set. core.ignoreStat If true, Git will avoid using lstat() calls to detect if files have changed by setting the "assume-unchanged" bit for those tracked files which it has updated identically in both the index and working tree. When files are modified outside of Git, the user will need to stage the modified files explicitly (e.g. see _Examples_ section in [**git-update-index**(1)](https://www.chedong.com/phpMan.php/man/git-update-index/1/markdown)). Git will not normally detect changes to those files. This is useful on systems where lstat() calls are very slow, such as CIFS/Microsoft Windows. False by default. core.preferSymlinkRefs Instead of the default "symref" format for HEAD and other symbolic reference files, use symbolic links. This is sometimes needed to work with old scripts that expect HEAD to be a symbolic link. core.alternateRefsCommand When advertising tips of available history from an alternate, use the shell to execute the specified command instead of [**git-for-each-ref**(1)](https://www.chedong.com/phpMan.php/man/git-for-each-ref/1/markdown). The first argument is the absolute path of the alternate. Output must contain one hex object id per line (i.e., the same as produced by **git** **for-each-ref** **--format='%(objectname)'**). Note that you cannot generally put **git** **for-each-ref** directly into the config value, as it does not take a repository path as an argument (but you can wrap the command above in a shell script). core.alternateRefsPrefixes When listing references from an alternate, list only references that begin with the given prefix. Prefixes match as if they were given as arguments to [**git-for-each-ref**(1)](https://www.chedong.com/phpMan.php/man/git-for-each-ref/1/markdown). To list multiple prefixes, separate them with whitespace. If **core.alternateRefsCommand** is set, setting **core.alternateRefsPrefixes** has no effect. core.bare If true this repository is assumed to be _bare_ and has no working directory associated with it. If this is the case a number of commands that require a working directory will be disabled, such as [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown) or [**git-merge**(1)](https://www.chedong.com/phpMan.php/man/git-merge/1/markdown). This setting is automatically guessed by [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown) or [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown) when the repository was created. By default a repository that ends in "/.git" is assumed to be not bare (bare = false), while all other repositories are assumed to be bare (bare = true). core.worktree Set the path to the root of the working tree. If **GIT**___**COMMON**___**DIR** environment variable is set, core.worktree is ignored and not used for determining the root of working tree. This can be overridden by the **GIT**___**WORK**___**TREE** environment variable and the **--work-tree** command-line option. The value can be an absolute path or relative to the path to the .git directory, which is either specified by --git-dir or GIT_DIR, or automatically discovered. If --git-dir or GIT_DIR is specified but none of --work-tree, GIT_WORK_TREE and core.worktree is specified, the current working directory is regarded as the top level of your working tree. Note that this variable is honored even when set in a configuration file in a ".git" subdirectory of a directory and its value differs from the latter directory (e.g. "/path/to/.git/config" has core.worktree set to "/different/path"), which is most likely a misconfiguration. Running Git commands in the "/path/to" directory will still use "/different/path" as the root of the work tree and can cause confusion unless you know what you are doing (e.g. you are creating a read-only snapshot of the same index to a location different from the repository’s usual working tree). core.logAllRefUpdates Enable the reflog. Updates to a ref is logged to the file "**$GIT**___**DIR/logs/**", by appending the new and old SHA-1, the date/time and the reason of the update, but only when the file exists. If this configuration variable is set to **true**, missing "**$GIT**___**DIR/logs/**" file is automatically created for branch heads (i.e. under **refs/heads/**), remote refs (i.e. under **refs/remotes/**), note refs (i.e. under **refs/notes/**), and the symbolic ref **HEAD**. If it is set to **always**, then a missing reflog is automatically created for any ref under **refs/**. This information can be used to determine what commit was the tip of a branch "2 days ago". This value is true by default in a repository that has a working directory associated with it, and false by default in a bare repository. core.repositoryFormatVersion Internal variable identifying the repository format and layout version. core.sharedRepository When _group_ (or _true_), the repository is made shareable between several users in a group (making sure all the files and objects are group-writable). When _all_ (or _world_ or _everybody_), the repository will be readable by all users, additionally to being group-shareable. When _umask_ (or _false_), Git will use permissions reported by [umask(2)](https://www.chedong.com/phpMan.php/man/umask/2/markdown). When _0xxx_, where _0xxx_ is an octal number, files in the repository will have this mode value. _0xxx_ will override user’s umask value (whereas the other options will only override requested parts of the user’s umask value). Examples: _0660_ will make the repo read/write-able for the owner and group, but inaccessible to others (equivalent to _group_ unless umask is e.g. _0022_). _0640_ is a repository that is group-readable but not group-writable. See [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown). False by default. core.warnAmbiguousRefs If true, Git will warn you if the ref name you passed it is ambiguous and might match multiple refs in the repository. True by default. core.compression An integer -1..9, indicating a default compression level. -1 is the zlib default. 0 means no compression, and 1..9 are various speed/size tradeoffs, 9 being slowest. If set, this provides a default to other compression variables, such as **core.looseCompression** and **pack.compression**. core.looseCompression An integer -1..9, indicating the compression level for objects that are not in a pack file. -1 is the zlib default. 0 means no compression, and 1..9 are various speed/size tradeoffs, 9 being slowest. If not set, defaults to core.compression. If that is not set, defaults to 1 (best speed). core.packedGitWindowSize Number of bytes of a pack file to map into memory in a single mapping operation. Larger window sizes may allow your system to process a smaller number of large pack files more quickly. Smaller window sizes will negatively affect performance due to increased calls to the operating system’s memory manager, but may improve performance when accessing a large number of large pack files. Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should be reasonable for all users/operating systems. You probably do not need to adjust this value. Common unit suffixes of _k_, _m_, or _g_ are supported. core.packedGitLimit Maximum number of bytes to map simultaneously into memory from pack files. If Git needs to access more than this many bytes at once to complete an operation it will unmap existing regions to reclaim virtual address space within the process. Default is 256 MiB on 32 bit platforms and 32 TiB (effectively unlimited) on 64 bit platforms. This should be reasonable for all users/operating systems, except on the largest projects. You probably do not need to adjust this value. Common unit suffixes of _k_, _m_, or _g_ are supported. core.deltaBaseCacheLimit Maximum number of bytes per thread to reserve for caching base objects that may be referenced by multiple deltified objects. By storing the entire decompressed base objects in a cache Git is able to avoid unpacking and decompressing frequently used base objects multiple times. Default is 96 MiB on all platforms. This should be reasonable for all users/operating systems, except on the largest projects. You probably do not need to adjust this value. Common unit suffixes of _k_, _m_, or _g_ are supported. core.bigFileThreshold Files larger than this size are stored deflated, without attempting delta compression. Storing large files without delta compression avoids excessive memory usage, at the slight expense of increased disk usage. Additionally files larger than this size are always treated as binary. Default is 512 MiB on all platforms. This should be reasonable for most projects as source code and other text files can still be delta compressed, but larger binary media files won’t be. Common unit suffixes of _k_, _m_, or _g_ are supported. core.excludesFile Specifies the pathname to the file that contains patterns to describe paths that are not meant to be tracked, in addition to **.gitignore** (per-directory) and **.git/info/exclude**. Defaults to **$XDG**___**CONFIG**___**HOME/git/ignore**. If **$XDG**___**CONFIG**___**HOME** is either not set or empty, **$HOME/.config/git/ignore** is used instead. See [**gitignore**(5)](https://www.chedong.com/phpMan.php/man/gitignore/5/markdown). core.askPass Some commands (e.g. svn and http interfaces) that interactively ask for a password can be told to use an external program given via the value of this variable. Can be overridden by the **GIT**___**ASKPASS** environment variable. If not set, fall back to the value of the **SSH**___**ASKPASS** environment variable or, failing that, a simple password prompt. The external program shall be given a suitable prompt as command-line argument and write the password on its STDOUT. core.attributesFile In addition to **.gitattributes** (per-directory) and **.git/info/attributes**, Git looks into this file for attributes (see [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown)). Path expansions are made the same way as for **core.excludesFile**. Its default value is **$XDG**___**CONFIG**___**HOME/git/attributes**. If **$XDG**___**CONFIG**___**HOME** is either not set or empty, **$HOME/.config/git/attributes** is used instead. core.hooksPath By default Git will look for your hooks in the **$GIT**___**DIR/hooks** directory. Set this to different path, e.g. **/etc/git/hooks**, and Git will try to find your hooks in that directory, e.g. **/etc/git/hooks/pre-receive** instead of in **$GIT**___**DIR/hooks/pre-receive**. The path can be either absolute or relative. A relative path is taken as relative to the directory where the hooks are run (see the "DESCRIPTION" section of [**githooks**(5)](https://www.chedong.com/phpMan.php/man/githooks/5/markdown)). This configuration variable is useful in cases where you’d like to centrally configure your Git hooks instead of configuring them on a per-repository basis, or as a more flexible and centralized alternative to having an **init.templateDir** where you’ve changed default hooks. core.editor Commands such as **commit** and **tag** that let you edit messages by launching an editor use the value of this variable when it is set, and the environment variable **GIT**___**EDITOR** is not set. See [**git-var**(1)](https://www.chedong.com/phpMan.php/man/git-var/1/markdown). core.commentChar Commands such as **commit** and **tag** that let you edit messages consider a line that begins with this character commented, and removes them after the editor returns (default _#_). If set to "auto", **git-commit** would select a character that is not the beginning character of any line in existing commit messages. core.filesRefLockTimeout The length of time, in milliseconds, to retry when trying to lock an individual reference. Value 0 means not to retry at all; -1 means to try indefinitely. Default is 100 (i.e., retry for 100ms). core.packedRefsTimeout The length of time, in milliseconds, to retry when trying to lock the **packed-refs** file. Value 0 means not to retry at all; -1 means to try indefinitely. Default is 1000 (i.e., retry for 1 second). core.pager Text viewer for use by Git commands (e.g., _less_). The value is meant to be interpreted by the shell. The order of preference is the **$GIT**___**PAGER** environment variable, then **core.pager** configuration, then **$PAGER**, and then the default chosen at compile time (usually _less_). When the **LESS** environment variable is unset, Git sets it to **FRX** (if **LESS** environment variable is set, Git does not change it at all). If you want to selectively override Git’s default setting for **LESS**, you can set **core.pager** to e.g. **less** **-S**. This will be passed to the shell by Git, which will translate the final command to **LESS=FRX** **less** **-S**. The environment does not set the **S** option but the command line does, instructing less to truncate long lines. Similarly, setting **core.pager** to **less** **-+F** will deactivate the **F** option specified by the environment from the command-line, deactivating the "quit if one screen" behavior of **less**. One can specifically activate some flags for particular commands: for example, setting **pager.blame** to **less** **-S** enables line truncation only for **git** **blame**. Likewise, when the **LV** environment variable is unset, Git sets it to **-c**. You can override this setting by exporting **LV** with another value or setting **core.pager** to **lv** **+c**. core.whitespace A comma separated list of common whitespace problems to notice. _git_ _diff_ will use **color.diff.whitespace** to highlight them, and _git_ _apply_ _--whitespace=error_ will consider them as errors. You can prefix **-** to disable any of them (e.g. **-trailing-space**): • **blank-at-eol** treats trailing whitespaces at the end of the line as an error (enabled by default). • **space-before-tab** treats a space character that appears immediately before a tab character in the initial indent part of the line as an error (enabled by default). • **indent-with-non-tab** treats a line that is indented with space characters instead of the equivalent tabs as an error (not enabled by default). • **tab-in-indent** treats a tab character in the initial indent part of the line as an error (not enabled by default). • **blank-at-eof** treats blank lines added at the end of file as an error (enabled by default). • **trailing-space** is a short-hand to cover both **blank-at-eol** and **blank-at-eof**. • **cr-at-eol** treats a carriage-return at the end of line as part of the line terminator, i.e. with it, **trailing-space** does not trigger if the character before such a carriage-return is not a whitespace (not enabled by default). • **tabwidth=** tells how many character positions a tab occupies; this is relevant for **indent-with-non-tab** and when Git fixes **tab-in-indent** errors. The default tab width is 8. Allowed values are 1 to 63. core.fsyncObjectFiles This boolean will enable _fsync()_ when writing object files. This is a total waste of time and effort on a filesystem that orders data writes properly, but can be useful for filesystems that do not use journalling (traditional UNIX filesystems) or that only journal metadata and not file contents (OS X’s HFS+, or Linux ext3 with "data=writeback"). core.preloadIndex Enable parallel index preload for operations like _git_ _diff_ This can speed up operations like _git_ _diff_ and _git_ _status_ especially on filesystems like NFS that have weak caching semantics and thus relatively high IO latencies. When enabled, Git will do the index comparison to the filesystem data in parallel, allowing overlapping IO’s. Defaults to true. core.unsetenvvars Windows-only: comma-separated list of environment variables' names that need to be unset before spawning any other process. Defaults to **PERL5LIB** to account for the fact that Git for Windows insists on using its own Perl interpreter. core.restrictinheritedhandles Windows-only: override whether spawned processes inherit only standard file handles (**stdin**, **stdout** and **stderr**) or all handles. Can be **auto**, **true** or **false**. Defaults to **auto**, which means **true** on Windows 7 and later, and **false** on older Windows versions. core.createObject You can set this to _link_, in which case a hardlink followed by a delete of the source are used to make sure that object creation will not overwrite existing objects. On some file system/operating system combinations, this is unreliable. Set this config setting to _rename_ there; However, This will remove the check that makes sure that existing object files will not get overwritten. core.notesRef When showing commit messages, also show notes which are stored in the given ref. The ref must be fully qualified. If the given ref does not exist, it is not an error but means that no notes should be printed. This setting defaults to "refs/notes/commits", and it can be overridden by the **GIT**___**NOTES**___**REF** environment variable. See [**git-notes**(1)](https://www.chedong.com/phpMan.php/man/git-notes/1/markdown). core.commitGraph If true, then git will read the commit-graph file (if it exists) to parse the graph structure of commits. Defaults to true. See [**git-commit-graph**(1)](https://www.chedong.com/phpMan.php/man/git-commit-graph/1/markdown) for more information. core.useReplaceRefs If set to **false**, behave as if the **--no-replace-objects** option was given on the command line. See [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) and [**git-replace**(1)](https://www.chedong.com/phpMan.php/man/git-replace/1/markdown) for more information. core.multiPackIndex Use the multi-pack-index file to track multiple packfiles using a single index. See **git-** [**multi-pack-index**(1)](https://www.chedong.com/phpMan.php/man/multi-pack-index/1/markdown) for more information. Defaults to true. core.sparseCheckout Enable "sparse checkout" feature. See [**git-sparse-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-sparse-checkout/1/markdown) for more information. core.sparseCheckoutCone Enables the "cone mode" of the sparse checkout feature. When the sparse-checkout file contains a limited set of patterns, then this mode provides significant performance advantages. See [**git-sparse-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-sparse-checkout/1/markdown) for more information. core.abbrev Set the length object names are abbreviated to. If unspecified or set to "auto", an appropriate value is computed based on the approximate number of packed objects in your repository, which hopefully is enough for abbreviated object names to stay unique for some time. If set to "no", no abbreviation is made and the object names are shown in their full length. The minimum length is 4. add.ignoreErrors, add.ignore-errors (deprecated) Tells _git_ _add_ to continue adding files when some files cannot be added due to indexing errors. Equivalent to the **--ignore-errors** option of [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown). **add.ignore-errors** is deprecated, as it does not follow the usual naming convention for configuration variables. add.interactive.useBuiltin [EXPERIMENTAL] Set to **true** to use the experimental built-in implementation of the interactive version of [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown) instead of the Perl script version. Is **false** by default. alias.* Command aliases for the [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown) command wrapper - e.g. after defining **alias.last** **=** **cat-file** **commit** **HEAD**, the invocation **git** **last** is equivalent to **git** **cat-file** **commit** **HEAD**. To avoid confusion and troubles with script usage, aliases that hide existing Git commands are ignored. Arguments are split by spaces, the usual shell quoting and escaping is supported. A quote pair or a backslash can be used to quote them. Note that the first word of an alias does not necessarily have to be a command. It can be a command-line option that will be passed into the invocation of **git**. In particular, this is useful when used with **-c** to pass in one-time configurations or **-p** to force pagination. For example, **loud-rebase** **=** **-c** **commit.verbose=true** **rebase** can be defined such that running **git** **loud-rebase** would be equivalent to **git** **-c** **commit.verbose=true** **rebase**. Also, **ps** **=** **-p** **status** would be a helpful alias since **git** **ps** would paginate the output of **git** **status** where the original command does not. If the alias expansion is prefixed with an exclamation point, it will be treated as a shell command. For example, defining **alias.new** **=** **!gitk** **--all** **--not** **ORIG**___**HEAD**, the invocation **git** **new** is equivalent to running the shell command **gitk** **--all** **--not** **ORIG**___**HEAD**. Note that shell commands will be executed from the top-level directory of a repository, which may not necessarily be the current directory. **GIT**___**PREFIX** is set as returned by running **git** **rev-parse** **--show-prefix** from the original current directory. See **git-rev-** [**parse**(1)](https://www.chedong.com/phpMan.php/man/parse/1/markdown). am.keepcr If true, git-am will call git-mailsplit for patches in mbox format with parameter **--keep-cr**. In this case git-mailsplit will not remove **\r** from lines ending with **\r\n**. Can be overridden by giving **--no-keep-cr** from the command line. See [**git-am**(1)](https://www.chedong.com/phpMan.php/man/git-am/1/markdown), **git-** [**mailsplit**(1)](https://www.chedong.com/phpMan.php/man/mailsplit/1/markdown). am.threeWay By default, **git** **am** will fail if the patch does not apply cleanly. When set to true, this setting tells **git** **am** to fall back on 3-way merge if the patch records the identity of blobs it is supposed to apply to and we have those blobs available locally (equivalent to giving the **--3way** option from the command line). Defaults to **false**. See [**git-am**(1)](https://www.chedong.com/phpMan.php/man/git-am/1/markdown). apply.ignoreWhitespace When set to _change_, tells _git_ _apply_ to ignore changes in whitespace, in the same way as the **--ignore-space-change** option. When set to one of: no, none, never, false tells _git_ _apply_ to respect all whitespace differences. See [**git-apply**(1)](https://www.chedong.com/phpMan.php/man/git-apply/1/markdown). apply.whitespace Tells _git_ _apply_ how to handle whitespaces, in the same way as the **--whitespace** option. See [**git-apply**(1)](https://www.chedong.com/phpMan.php/man/git-apply/1/markdown). blame.blankBoundary Show blank commit object name for boundary commits in [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). This option defaults to false. blame.coloring This determines the coloring scheme to be applied to blame output. It can be _repeatedLines_, _highlightRecent_, or _none_ which is the default. blame.date Specifies the format used to output dates in [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). If unset the iso format is used. For supported values, see the discussion of the **--date** option at [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown). blame.showEmail Show the author email instead of author name in [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). This option defaults to false. blame.showRoot Do not treat root commits as boundaries in [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). This option defaults to false. blame.ignoreRevsFile Ignore revisions listed in the file, one unabbreviated object name per line, in **git-** [**blame**(1)](https://www.chedong.com/phpMan.php/man/blame/1/markdown). Whitespace and comments beginning with **#** are ignored. This option may be repeated multiple times. Empty file names will reset the list of ignored revisions. This option will be handled before the command line option **--ignore-revs-file**. blame.markUnblamableLines Mark lines that were changed by an ignored revision that we could not attribute to another commit with a _*_ in the output of [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). blame.markIgnoredLines Mark lines that were changed by an ignored revision that we attributed to another commit with a _?_ in the output of [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown). branch.autoSetupMerge Tells _git_ _branch_, _git_ _switch_ and _git_ _checkout_ to set up new branches so that [**git-pull**(1)](https://www.chedong.com/phpMan.php/man/git-pull/1/markdown) will appropriately merge from the starting point branch. Note that even if this option is not set, this behavior can be chosen per-branch using the **--track** and **--no-track** options. The valid settings are: **false** — no automatic setup is done; **true** — automatic setup is done when the starting point is a remote-tracking branch; **always** — automatic setup is done when the starting point is either a local branch or remote-tracking branch. This option defaults to true. branch.autoSetupRebase When a new branch is created with _git_ _branch_, _git_ _switch_ or _git_ _checkout_ that tracks another branch, this variable tells Git to set up pull to rebase instead of merge (see "branch..rebase"). When **never**, rebase is never automatically set to true. When **local**, rebase is set to true for tracked branches of other local branches. When **remote**, rebase is set to true for tracked branches of remote-tracking branches. When **always**, rebase will be set to true for all tracking branches. See "branch.autoSetupMerge" for details on how to set up a branch to track another branch. This option defaults to never. branch.sort This variable controls the sort ordering of branches when displayed by [**git-branch**(1)](https://www.chedong.com/phpMan.php/man/git-branch/1/markdown). Without the "--sort=" option provided, the value of this variable will be used as the default. See [**git-for-each-ref**(1)](https://www.chedong.com/phpMan.php/man/git-for-each-ref/1/markdown) field names for valid values. branch..remote When on branch , it tells _git_ _fetch_ and _git_ _push_ which remote to fetch from/push to. The remote to push to may be overridden with **remote.pushDefault** (for all branches). The remote to push to, for the current branch, may be further overridden by **branch..pushRemote**. If no remote is configured, or if you are not on any branch, it defaults to **origin** for fetching and **remote.pushDefault** for pushing. Additionally, **.** (a period) is the current local repository (a dot-repository), see **branch..merge**'s final note below. branch..pushRemote When on branch , it overrides **branch..remote** for pushing. It also overrides **remote.pushDefault** for pushing from branch . When you pull from one place (e.g. your upstream) and push to another place (e.g. your own publishing repository), you would want to set **remote.pushDefault** to specify the remote to push to for all branches, and use this option to override it for a specific branch. branch..merge Defines, together with branch..remote, the upstream branch for the given branch. It tells _git_ _fetch_/_git_ _pull_/_git_ _rebase_ which branch to merge and can also affect _git_ _push_ (see push.default). When in branch , it tells _git_ _fetch_ the default refspec to be marked for merging in FETCH_HEAD. The value is handled like the remote part of a refspec, and must match a ref which is fetched from the remote given by "branch..remote". The merge information is used by _git_ _pull_ (which at first calls _git_ _fetch_) to lookup the default branch for merging. Without this option, _git_ _pull_ defaults to merge the first refspec fetched. Specify multiple values to get an octopus merge. If you wish to setup _git_ _pull_ so that it merges into from another branch in the local repository, you can point branch..merge to the desired branch, and use the relative path setting **.** (a period) for branch..remote. branch..mergeOptions Sets default options for merging into branch . The syntax and supported options are the same as those of [**git-merge**(1)](https://www.chedong.com/phpMan.php/man/git-merge/1/markdown), but option values containing whitespace characters are currently not supported. branch..rebase When true, rebase the branch on top of the fetched branch, instead of merging the default branch from the default remote when "git pull" is run. See "pull.rebase" for doing this in a non branch-specific manner. When **merges** (or just _m_), pass the **--rebase-merges** option to _git_ _rebase_ so that the local merge commits are included in the rebase (see [**git-rebase**(1)](https://www.chedong.com/phpMan.php/man/git-rebase/1/markdown) for details). When the value is **interactive** (or just _i_), the rebase is run in interactive mode. **NOTE**: this is a possibly dangerous operation; do **not** use it unless you understand the implications (see [**git-rebase**(1)](https://www.chedong.com/phpMan.php/man/git-rebase/1/markdown) for details). branch..description Branch description, can be edited with **git** **branch** **--edit-description**. Branch description is automatically added in the format-patch cover letter or request-pull summary. browser..cmd Specify the command to invoke the specified browser. The specified command is evaluated in shell with the URLs passed as arguments. (See [**git-web--browse**(1)](https://www.chedong.com/phpMan.php/man/git-web--browse/1/markdown).) browser..path Override the path for the given tool that may be used to browse HTML help (see **-w** option in [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown)) or a working repository in gitweb (see [**git-instaweb**(1)](https://www.chedong.com/phpMan.php/man/git-instaweb/1/markdown)). checkout.defaultRemote When you run **git** **checkout** **** or **git** **switch** **** and only have one remote, it may implicitly fall back on checking out and tracking e.g. **origin/**. This stops working as soon as you have more than one remote with a **** reference. This setting allows for setting the name of a preferred remote that should always win when it comes to disambiguation. The typical use-case is to set this to **origin**. Currently this is used by [**git-switch**(1)](https://www.chedong.com/phpMan.php/man/git-switch/1/markdown) and [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown) when **git** **checkout** **** or **git** **switch** **** will checkout the **** branch on another remote, and by [**git-worktree**(1)](https://www.chedong.com/phpMan.php/man/git-worktree/1/markdown) when **git** **worktree** **add** refers to a remote branch. This setting might be used for other checkout-like commands or functionality in the future. checkout.guess Provides the default value for the **--guess** or **--no-guess** option in **git** **checkout** and **git** **switch**. See [**git-switch**(1)](https://www.chedong.com/phpMan.php/man/git-switch/1/markdown) and [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown). checkout.workers The number of parallel workers to use when updating the working tree. The default is one, i.e. sequential execution. If set to a value less than one, Git will use as many workers as the number of logical cores available. This setting and **checkout.thresholdForParallelism** affect all commands that perform checkout. E.g. checkout, clone, reset, sparse-checkout, etc. Note: parallel checkout usually delivers better performance for repositories located on SSDs or over NFS. For repositories on spinning disks and/or machines with a small number of cores, the default sequential checkout often performs better. The size and compression level of a repository might also influence how well the parallel version performs. checkout.thresholdForParallelism When running parallel checkout with a small number of files, the cost of subprocess spawning and inter-process communication might outweigh the parallelization gains. This setting allows to define the minimum number of files for which parallel checkout should be attempted. The default is 100. clean.requireForce A boolean to make git-clean do nothing unless given -f, -i or -n. Defaults to true. clone.defaultRemoteName The name of the remote to create when cloning a repository. Defaults to **origin**, and can be overridden by passing the **--origin** command-line option to [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown). clone.rejectShallow Reject to clone a repository if it is a shallow one, can be overridden by passing option **--reject-shallow** in command line. See [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown) color.advice A boolean to enable/disable color in hints (e.g. when a push failed, see **advice.*** for a list). May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the error output goes to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.advice.hint Use customized color for hints. color.blame.highlightRecent Specify the line annotation color for **git** **blame** **--color-by-age** depending upon the age of the line. This setting should be set to a comma-separated list of color and date settings, starting and ending with a color, the dates should be set from oldest to newest. The metadata will be colored with the specified colors if the line was introduced before the given timestamp, overwriting older timestamped colors. Instead of an absolute timestamp relative timestamps work as well, e.g. **2.weeks.ago** is valid to address anything older than 2 weeks. It defaults to **blue,12** **month** **ago,white,1** **month** **ago,red**, which colors everything older than one year blue, recent changes between one month and one year old are kept white, and lines introduced within the last month are colored red. color.blame.repeatedLines Use the specified color to colorize line annotations for **git** **blame** **--color-lines**, if they come from the same commit as the preceding line. Defaults to cyan. color.branch A boolean to enable/disable color in the output of [**git-branch**(1)](https://www.chedong.com/phpMan.php/man/git-branch/1/markdown). May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the output is to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.branch. Use customized color for branch coloration. **** is one of **current** (the current branch), **local** (a local branch), **remote** (a remote-tracking branch in refs/remotes/), **upstream** (upstream tracking branch), **plain** (other refs). color.diff Whether to use ANSI escape sequences to add color to patches. If this is set to **always**, [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown), [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), and [**git-show**(1)](https://www.chedong.com/phpMan.php/man/git-show/1/markdown) will use color for all patches. If it is set to **true** or **auto**, those commands will only use color when output is to the terminal. If unset, then the value of **color.ui** is used (**auto** by default). This does not affect [**git-format-patch**(1)](https://www.chedong.com/phpMan.php/man/git-format-patch/1/markdown) or the _git-diff-*_ plumbing commands. Can be overridden on the command line with the **--color[=]** option. color.diff. Use customized color for diff colorization. **** specifies which part of the patch to use the specified color, and is one of **context** (context text - **plain** is a historical synonym), **meta** (metainformation), **frag** (hunk header), _func_ (function in hunk header), **old** (removed lines), **new** (added lines), **commit** (commit headers), **whitespace** (highlighting whitespace errors), **oldMoved** (deleted lines), **newMoved** (added lines), **oldMovedDimmed**, **oldMovedAlternative**, **oldMovedAlternativeDimmed**, **newMovedDimmed**, **newMovedAlternative** **newMovedAlternativeDimmed** (See the __ setting of _--color-moved_ in [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown) for details), **contextDimmed**, **oldDimmed**, **newDimmed**, **contextBold**, **oldBold**, and **newBold** (see [**git-range-diff**(1)](https://www.chedong.com/phpMan.php/man/git-range-diff/1/markdown) for details). color.decorate. Use customized color for _git_ _log_ _--decorate_ output. **** is one of **branch**, **remoteBranch**, **tag**, **stash** or **HEAD** for local branches, remote-tracking branches, tags, stash and HEAD, respectively and **grafted** for grafted commits. color.grep When set to **always**, always highlight matches. When **false** (or **never**), never. When set to **true** or **auto**, use color only when the output is written to the terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.grep. Use customized color for grep colorization. **** specifies which part of the line to use the specified color, and is one of **context** non-matching text in context lines (when using **-A**, **-B**, or **-C**) **filename** filename prefix (when not using **-h**) **function** function name lines (when using **-p**) **lineNumber** line number prefix (when using **-n**) **column** column number prefix (when using **--column**) **match** matching text (same as setting **matchContext** and **matchSelected**) **matchContext** matching text in context lines **matchSelected** matching text in selected lines. Also, used to customize the following [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown) subcommands: **--grep**, **--author** and **--committer**. **selected** non-matching text in selected lines. Also, used to customize the following [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown) subcommands: **--grep**, **--author** and **--committer**. **separator** separators between fields on a line (**:**, **-**, and **=**) and between hunks (**--**) color.interactive When set to **always**, always use colors for interactive prompts and displays (such as those used by "git-add --interactive" and "git-clean --interactive"). When false (or **never**), never. When set to **true** or **auto**, use colors only when the output is to the terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.interactive. Use customized color for _git_ _add_ _--interactive_ and _git_ _clean_ _--interactive_ output. **** may be **prompt**, **header**, **help** or **error**, for four distinct types of normal output from interactive commands. color.pager A boolean to specify whether **auto** color modes should colorize output going to the pager. Defaults to true; set this to false if your pager does not understand ANSI color codes. color.push A boolean to enable/disable color in push errors. May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the error output goes to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.push.error Use customized color for push errors. color.remote If set, keywords at the start of the line are highlighted. The keywords are "error", "warning", "hint" and "success", and are matched case-insensitively. May be set to **always**, **false** (or **never**) or **auto** (or **true**). If unset, then the value of **color.ui** is used (**auto** by default). color.remote. Use customized color for each remote keyword. **** may be **hint**, **warning**, **success** or **error** which match the corresponding keyword. color.showBranch A boolean to enable/disable color in the output of [**git-show-branch**(1)](https://www.chedong.com/phpMan.php/man/git-show-branch/1/markdown). May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the output is to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.status A boolean to enable/disable color in the output of [**git-status**(1)](https://www.chedong.com/phpMan.php/man/git-status/1/markdown). May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the output is to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.status. Use customized color for status colorization. **** is one of **header** (the header text of the status message), **added** or **updated** (files which are added but not committed), **changed** (files which are changed but not added in the index), **untracked** (files which are not tracked by Git), **branch** (the current branch), **nobranch** (the color the _no_ _branch_ warning is shown in, defaulting to red), **localBranch** or **remoteBranch** (the local and remote branch names, respectively, when branch and tracking information is displayed in the status short-format), or **unmerged** (files which have unmerged changes). color.transport A boolean to enable/disable color when pushes are rejected. May be set to **always**, **false** (or **never**) or **auto** (or **true**), in which case colors are used only when the error output goes to a terminal. If unset, then the value of **color.ui** is used (**auto** by default). color.transport.rejected Use customized color when a push was rejected. color.ui This variable determines the default value for variables such as **color.diff** and **color.grep** that control the use of color per command family. Its scope will expand as more commands learn configuration to set a default for the **--color** option. Set it to **false** or **never** if you prefer Git commands not to use color unless enabled explicitly with some other configuration or the **--color** option. Set it to **always** if you want all output not intended for machine consumption to use color, to **true** or **auto** (this is the default since Git 1.8.4) if you want such output to use color when written to the terminal. column.ui Specify whether supported commands should output in columns. This variable consists of a list of tokens separated by spaces or commas: These options control when the feature should be enabled (defaults to _never_): **always** always show in columns **never** never show in columns **auto** show in columns if the output is to the terminal These options control layout (defaults to _column_). Setting any of these implies _always_ if none of _always_, _never_, or _auto_ are specified. **column** fill columns before rows **row** fill rows before columns **plain** show in one column Finally, these options can be combined with a layout option (defaults to _nodense_): **dense** make unequal size columns to utilize more space **nodense** make equal size columns column.branch Specify whether to output branch listing in **git** **branch** in columns. See **column.ui** for details. column.clean Specify the layout when list items in **git** **clean** **-i**, which always shows files and directories in columns. See **column.ui** for details. column.status Specify whether to output untracked files in **git** **status** in columns. See **column.ui** for details. column.tag Specify whether to output tag listing in **git** **tag** in columns. See **column.ui** for details. commit.cleanup This setting overrides the default of the **--cleanup** option in **git** **commit**. See **git-** [**commit**(1)](https://www.chedong.com/phpMan.php/man/commit/1/markdown) for details. Changing the default can be useful when you always want to keep lines that begin with comment character **#** in your log message, in which case you would do **git** **config** **commit.cleanup** **whitespace** (note that you will have to remove the help lines that begin with **#** in the commit log template yourself, if you do this). commit.gpgSign A boolean to specify whether all commits should be GPG signed. Use of this option when doing operations such as rebase can result in a large number of commits being signed. It may be convenient to use an agent to avoid typing your GPG passphrase several times. commit.status A boolean to enable/disable inclusion of status information in the commit message template when using an editor to prepare the commit message. Defaults to true. commit.template Specify the pathname of a file to use as the template for new commit messages. commit.verbose A boolean or int to specify the level of verbose with **git** **commit**. See [**git-commit**(1)](https://www.chedong.com/phpMan.php/man/git-commit/1/markdown). commitGraph.generationVersion Specifies the type of generation number version to use when writing or reading the commit-graph file. If version 1 is specified, then the corrected commit dates will not be written or read. Defaults to 2. commitGraph.maxNewFilters Specifies the default value for the **--max-new-filters** option of **git** **commit-graph** **write** (c.f., [**git-commit-graph**(1)](https://www.chedong.com/phpMan.php/man/git-commit-graph/1/markdown)). commitGraph.readChangedPaths If true, then git will use the changed-path Bloom filters in the commit-graph file (if it exists, and they are present). Defaults to true. See [**git-commit-graph**(1)](https://www.chedong.com/phpMan.php/man/git-commit-graph/1/markdown) for more information. credential.helper Specify an external helper to be called when a username or password credential is needed; the helper may consult external storage to avoid prompting the user for the credentials. This is normally the name of a credential helper with possible arguments, but may also be an absolute path with arguments or, if preceded by **!**, shell commands. Note that multiple helpers may be defined. See [**gitcredentials**(7)](https://www.chedong.com/phpMan.php/man/gitcredentials/7/markdown) for details and examples. credential.useHttpPath When acquiring credentials, consider the "path" component of an http or https URL to be important. Defaults to false. See [**gitcredentials**(7)](https://www.chedong.com/phpMan.php/man/gitcredentials/7/markdown) for more information. credential.sanitizePrompt By default, user names and hosts that are shown as part of the password prompt are not allowed to contain control characters (they will be URL-encoded by default). Configure this setting to **false** to override that behavior. credential.protectProtocol By default, Carriage Return characters are not allowed in the protocol that is used when Git talks to a credential helper. This setting allows users to override this default. credential.username If no username is set for a network authentication, use this username by default. See credential..* below, and [**gitcredentials**(7)](https://www.chedong.com/phpMan.php/man/gitcredentials/7/markdown). credential..* Any of the credential.* options above can be applied selectively to some credentials. For example "credential." would set the default username only for https connections to example.com. See [**gitcredentials**(7)](https://www.chedong.com/phpMan.php/man/gitcredentials/7/markdown) for details on how URLs are matched. credentialCache.ignoreSIGHUP Tell git-credential-cache—daemon to ignore SIGHUP, instead of quitting. credentialStore.lockTimeoutMS The length of time, in milliseconds, for git-credential-store to retry when trying to lock the credentials file. Value 0 means not to retry at all; -1 means to try indefinitely. Default is 1000 (i.e., retry for 1s). completion.commands This is only used by git-completion.bash to add or remove commands from the list of completed commands. Normally only porcelain commands and a few select others are completed. You can add more commands, separated by space, in this variable. Prefixing the command with _-_ will remove it from the existing list. diff.autoRefreshIndex When using _git_ _diff_ to compare with work tree files, do not consider stat-only change as changed. Instead, silently run **git** **update-index** **--refresh** to update the cached stat information for paths whose contents in the work tree match the contents in the index. This option defaults to true. Note that this affects only _git_ _diff_ Porcelain, and not lower level _diff_ commands such as _git_ _diff-files_. diff.dirstat A comma separated list of **--dirstat** parameters specifying the default behavior of the **--dirstat** option to [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown) and friends. The defaults can be overridden on the command line (using **--dirstat=**). The fallback defaults (when not changed by **diff.dirstat**) are **changes,noncumulative,3**. The following parameters are available: **changes** Compute the dirstat numbers by counting the lines that have been removed from the source, or added to the destination. This ignores the amount of pure code movements within a file. In other words, rearranging lines in a file is not counted as much as other changes. This is the default behavior when no parameter is given. **lines** Compute the dirstat numbers by doing the regular line-based diff analysis, and summing the removed/added line counts. (For binary files, count 64-byte chunks instead, since binary files have no natural concept of lines). This is a more expensive **--dirstat** behavior than the **changes** behavior, but it does count rearranged lines within a file as much as other changes. The resulting output is consistent with what you get from the other **--*stat** options. **files** Compute the dirstat numbers by counting the number of files changed. Each changed file counts equally in the dirstat analysis. This is the computationally cheapest **--dirstat** behavior, since it does not have to look at the file contents at all. **cumulative** Count changes in a child directory for the parent directory as well. Note that when using **cumulative**, the sum of the percentages reported may exceed 100%. The default (non-cumulative) behavior can be specified with the **noncumulative** parameter. An integer parameter specifies a cut-off percent (3% by default). Directories contributing less than this percentage of the changes are not shown in the output. Example: The following will count changed files, while ignoring directories with less than 10% of the total amount of changed files, and accumulating child directory counts in the parent directories: **files,10,cumulative**. diff.statGraphWidth Limit the width of the graph part in --stat output. If set, applies to all commands generating --stat output except format-patch. diff.context Generate diffs with lines of context instead of the default of 3. This value is overridden by the -U option. diff.interHunkContext Show the context between diff hunks, up to the specified number of lines, thereby fusing the hunks that are close to each other. This value serves as the default for the **--inter-hunk-context** command line option. diff.external If this config variable is set, diff generation is not performed using the internal diff machinery, but using the given command. Can be overridden with the ‘GIT_EXTERNAL_DIFF’ environment variable. The command is called with parameters as described under "git Diffs" in [**git**(1)](https://www.chedong.com/phpMan.php/man/git/1/markdown). Note: if you want to use an external diff program only on a subset of your files, you might want to use [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) instead. diff.ignoreSubmodules Sets the default value of --ignore-submodules. Note that this affects only _git_ _diff_ Porcelain, and not lower level _diff_ commands such as _git_ _diff-files_. _git_ _checkout_ and _git_ _switch_ also honor this setting when reporting uncommitted changes. Setting it to _all_ disables the submodule summary normally shown by _git_ _commit_ and _git_ _status_ when **status.submoduleSummary** is set unless it is overridden by using the --ignore-submodules command-line option. The _git_ _submodule_ commands are not affected by this setting. By default this is set to untracked so that any untracked submodules are ignored. diff.mnemonicPrefix If set, _git_ _diff_ uses a prefix pair that is different from the standard "a/" and "b/" depending on what is being compared. When this configuration is in effect, reverse diff output also swaps the order of the prefixes: **git** **diff** compares the (i)ndex and the (w)ork tree; **git** **diff** **HEAD** compares a (c)ommit and the (w)ork tree; **git** **diff** **--cached** compares a (c)ommit and the (i)ndex; **git** **diff** **HEAD:file1** **file2** compares an (o)bject and a (w)ork tree entity; **git** **diff** **--no-index** **a** **b** compares two non-git things (1) and (2). diff.noprefix If set, _git_ _diff_ does not show any source or destination prefix. diff.relative If set to _true_, _git_ _diff_ does not show changes outside of the directory and show pathnames relative to the current directory. diff.orderFile File indicating how to order files within a diff. See the _-O_ option to [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown) for details. If **diff.orderFile** is a relative pathname, it is treated as relative to the top of the working tree. diff.renameLimit The number of files to consider in the exhaustive portion of copy/rename detection; equivalent to the _git_ _diff_ option **-l**. If not set, the default value is currently 1000. This setting has no effect if rename detection is turned off. diff.renames Whether and how Git detects renames. If set to "false", rename detection is disabled. If set to "true", basic rename detection is enabled. If set to "copies" or "copy", Git will detect copies, as well. Defaults to true. Note that this affects only _git_ _diff_ Porcelain like [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown) and [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), and not lower level commands such as [**git-diff-files**(1)](https://www.chedong.com/phpMan.php/man/git-diff-files/1/markdown). diff.suppressBlankEmpty A boolean to inhibit the standard behavior of printing a space before each empty output line. Defaults to false. diff.submodule Specify the format in which differences in submodules are shown. The "short" format just shows the names of the commits at the beginning and end of the range. The "log" format lists the commits in the range like [**git-submodule**(1)](https://www.chedong.com/phpMan.php/man/git-submodule/1/markdown) **summary** does. The "diff" format shows an inline diff of the changed contents of the submodule. Defaults to "short". diff.wordRegex A POSIX Extended Regular Expression used to determine what is a "word" when performing word-by-word difference calculations. Character sequences that match the regular expression are "words", all other characters are **ignorable** whitespace. diff..command The custom diff driver command. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff..xfuncname The regular expression that the diff driver should use to recognize the hunk header. A built-in pattern may also be used. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff..binary Set this option to true to make the diff driver treat files as binary. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff..textconv The command that the diff driver should call to generate the text-converted version of a file. The result of the conversion is used to generate a human-readable diff. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff..wordRegex The regular expression that the diff driver should use to split words in a line. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff..cachetextconv Set this option to true to make the diff driver cache the text conversion outputs. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. diff.tool Controls which diff tool is used by [**git-difftool**(1)](https://www.chedong.com/phpMan.php/man/git-difftool/1/markdown). This variable overrides the value configured in **merge.tool**. The list below shows the valid built-in values. Any other value is treated as a custom diff tool and requires that a corresponding difftool..cmd variable is defined. diff.guitool Controls which diff tool is used by [**git-difftool**(1)](https://www.chedong.com/phpMan.php/man/git-difftool/1/markdown) when the -g/--gui flag is specified. This variable overrides the value configured in **merge.guitool**. The list below shows the valid built-in values. Any other value is treated as a custom diff tool and requires that a corresponding difftool..cmd variable is defined. • araxis • bc • bc3 • bc4 • codecompare • deltawalker • diffmerge • diffuse • ecmerge • emerge • examdiff • guiffy • gvimdiff • gvimdiff1 • gvimdiff2 • gvimdiff3 • kdiff3 • kompare • meld • nvimdiff • nvimdiff1 • nvimdiff2 • nvimdiff3 • opendiff • p4merge • smerge • tkdiff • vimdiff • vimdiff1 • vimdiff2 • vimdiff3 • winmerge • xxdiff diff.indentHeuristic Set this option to **false** to disable the default heuristics that shift diff hunk boundaries to make patches easier to read. diff.algorithm Choose a diff algorithm. The variants are as follows: **default**, **myers** The basic greedy diff algorithm. Currently, this is the default. **minimal** Spend extra time to make sure the smallest possible diff is produced. **patience** Use "patience diff" algorithm when generating patches. **histogram** This algorithm extends the patience algorithm to "support low-occurrence common elements". diff.wsErrorHighlight Highlight whitespace errors in the **context**, **old** or **new** lines of the diff. Multiple values are separated by comma, **none** resets previous values, **default** reset the list to **new** and **all** is a shorthand for **old,new,context**. The whitespace errors are colored with **color.diff.whitespace**. The command line option **--ws-error-highlight=** overrides this setting. diff.colorMoved If set to either a valid **** or a true value, moved lines in a diff are colored differently, for details of valid modes see _--color-moved_ in [**git-diff**(1)](https://www.chedong.com/phpMan.php/man/git-diff/1/markdown). If simply set to true the default color mode will be used. When set to false, moved lines are not colored. diff.colorMovedWS When moved lines are colored using e.g. the **diff.colorMoved** setting, this option controls the **** how spaces are treated for details of valid modes see _--color-moved-ws_ in **git-** [**diff**(1)](https://www.chedong.com/phpMan.php/man/diff/1/markdown). difftool..path Override the path for the given tool. This is useful in case your tool is not in the PATH. difftool..cmd Specify the command to invoke the specified diff tool. The specified command is evaluated in shell with the following variables available: _LOCAL_ is set to the name of the temporary file containing the contents of the diff pre-image and _REMOTE_ is set to the name of the temporary file containing the contents of the diff post-image. difftool.prompt Prompt before each invocation of the diff tool. extensions.objectFormat Specify the hash algorithm to use. The acceptable values are **sha1** and **sha256**. If not specified, **sha1** is assumed. It is an error to specify this key unless **core.repositoryFormatVersion** is 1. Note that this setting should only be set by [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown) or [**git-clone**(1)](https://www.chedong.com/phpMan.php/man/git-clone/1/markdown). Trying to change it after initialization will not work and will produce hard-to-diagnose issues. fastimport.unpackLimit If the number of objects imported by [**git-fast-import**(1)](https://www.chedong.com/phpMan.php/man/git-fast-import/1/markdown) is below this limit, then the objects will be unpacked into loose object files. However if the number of imported objects equals or exceeds this limit then the pack will be stored as a pack. Storing the pack from a fast-import can make the import operation complete faster, especially on slow filesystems. If not set, the value of **transfer.unpackLimit** is used instead. feature.* The config settings that start with **feature.** modify the defaults of a group of other config settings. These groups are created by the Git developer community as recommended defaults and are subject to change. In particular, new config options may be added with different defaults. feature.experimental Enable config options that are new to Git, and are being considered for future defaults. Config settings included here may be added or removed with each release, including minor version updates. These settings may have unintended interactions since they are so new. Please enable this setting if you are interested in providing feedback on experimental features. The new default values are: • **fetch.negotiationAlgorithm=skipping** may improve fetch negotiation times by skipping more commits at a time, reducing the number of round trips. feature.manyFiles Enable config options that optimize for repos with many files in the working directory. With many files, commands such as **git** **status** and **git** **checkout** may be slow and these new defaults improve performance: • **index.version=4** enables path-prefix compression in the index. • **core.untrackedCache=true** enables the untracked cache. This setting assumes that mtime is working on your machine. fetch.recurseSubmodules This option controls whether **git** **fetch** (and the underlying fetch in **git** **pull**) will recursively fetch into populated submodules. This option can be set either to a boolean value or to _on-demand_. Setting it to a boolean changes the behavior of fetch and pull to recurse unconditionally into submodules when set to true or to not recurse at all when set to false. When set to _on-demand_, fetch and pull will only recurse into a populated submodule when its superproject retrieves a commit that updates the submodule’s reference. Defaults to _on-demand_, or to the value of _submodule.recurse_ if set. fetch.fsckObjects If it is set to true, git-fetch-pack will check all fetched objects. See **transfer.fsckObjects** for what’s checked. Defaults to false. If not set, the value of **transfer.fsckObjects** is used instead. fetch.fsck. Acts like **fsck.**, but is used by [**git-fetch-pack**(1)](https://www.chedong.com/phpMan.php/man/git-fetch-pack/1/markdown) instead of [**git-fsck**(1)](https://www.chedong.com/phpMan.php/man/git-fsck/1/markdown). See the **fsck.** documentation for details. fetch.fsck.skipList Acts like **fsck.skipList**, but is used by [**git-fetch-pack**(1)](https://www.chedong.com/phpMan.php/man/git-fetch-pack/1/markdown) instead of [**git-fsck**(1)](https://www.chedong.com/phpMan.php/man/git-fsck/1/markdown). See the **fsck.skipList** documentation for details. fetch.unpackLimit If the number of objects fetched over the Git native transfer is below this limit, then the objects will be unpacked into loose object files. However if the number of received objects equals or exceeds this limit then the received pack will be stored as a pack, after adding any missing delta bases. Storing the pack from a push can make the push operation complete faster, especially on slow filesystems. If not set, the value of **transfer.unpackLimit** is used instead. fetch.prune If true, fetch will automatically behave as if the **--prune** option was given on the command line. See also **remote..prune** and the PRUNING section of [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown). fetch.pruneTags If true, fetch will automatically behave as if the **refs/tags/*:refs/tags/*** refspec was provided when pruning, if not set already. This allows for setting both this option and **fetch.prune** to maintain a 1=1 mapping to upstream refs. See also **remote..pruneTags** and the PRUNING section of [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown). fetch.output Control how ref update status is printed. Valid values are **full** and **compact**. Default value is **full**. See section OUTPUT in [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown) for detail. fetch.negotiationAlgorithm Control how information about the commits in the local repository is sent when negotiating the contents of the packfile to be sent by the server. Set to "skipping" to use an algorithm that skips commits in an effort to converge faster, but may result in a larger-than-necessary packfile; or set to "noop" to not send any information at all, which will almost certainly result in a larger-than-necessary packfile, but will skip the negotiation step. The default is "default" which instructs Git to use the default algorithm that never skips commits (unless the server has acknowledged it or one of its descendants). If **feature.experimental** is enabled, then this setting defaults to "skipping". Unknown values will cause _git_ _fetch_ to error out. See also the **--negotiate-only** and **--negotiation-tip** options to [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown). fetch.showForcedUpdates Set to false to enable **--no-show-forced-updates** in [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown) and [**git-pull**(1)](https://www.chedong.com/phpMan.php/man/git-pull/1/markdown) commands. Defaults to true. fetch.parallel Specifies the maximal number of fetch operations to be run in parallel at a time (submodules, or remotes when the **--multiple** option of [**git-fetch**(1)](https://www.chedong.com/phpMan.php/man/git-fetch/1/markdown) is in effect). A value of 0 will give some reasonable default. If unset, it defaults to 1. For submodules, this setting can be overridden using the **submodule.fetchJobs** config setting. fetch.writeCommitGraph Set to true to write a commit-graph after every **git** **fetch** command that downloads a pack-file from a remote. Using the **--split** option, most executions will create a very small commit-graph file on top of the existing commit-graph file(s). Occasionally, these files will merge and the write may take longer. Having an updated commit-graph file helps performance of many Git commands, including **git** **merge-base**, **git** **push** **-f**, and **git** **log** **--graph**. Defaults to false. format.attach Enable multipart/mixed attachments as the default for _format-patch_. The value can also be a double quoted string which will enable attachments as the default and set the value as the boundary. See the --attach option in [**git-format-patch**(1)](https://www.chedong.com/phpMan.php/man/git-format-patch/1/markdown). format.from Provides the default value for the **--from** option to format-patch. Accepts a boolean value, or a name and email address. If false, format-patch defaults to **--no-from**, using commit authors directly in the "From:" field of patch mails. If true, format-patch defaults to **--from**, using your committer identity in the "From:" field of patch mails and including a "From:" field in the body of the patch mail if different. If set to a non-boolean value, format-patch uses that value instead of your committer identity. Defaults to false. format.numbered A boolean which can enable or disable sequence numbers in patch subjects. It defaults to "auto" which enables it only if there is more than one patch. It can be enabled or disabled for all messages by setting it to "true" or "false". See --numbered option in [**git-format-patch**(1)](https://www.chedong.com/phpMan.php/man/git-format-patch/1/markdown). format.headers Additional email headers to include in a patch to be submitted by mail. See **git-format-** [**patch**(1)](https://www.chedong.com/phpMan.php/man/patch/1/markdown). format.to, format.cc Additional recipients to include in a patch to be submitted by mail. See the --to and --cc options in [**git-format-patch**(1)](https://www.chedong.com/phpMan.php/man/git-format-patch/1/markdown). format.subjectPrefix The default for format-patch is to output files with the _[PATCH]_ subject prefix. Use this variable to change that prefix. format.coverFromDescription The default mode for format-patch to determine which parts of the cover letter will be populated using the branch’s description. See the **--cover-from-description** option in **git-** [**format-patch**(1)](https://www.chedong.com/phpMan.php/man/format-patch/1/markdown). format.signature The default for format-patch is to output a signature containing the Git version number. Use this variable to change that default. Set this variable to the empty string ("") to suppress signature generation. format.signatureFile Works just like format.signature except the contents of the file specified by this variable will be used as the signature. format.suffix The default for format-patch is to output files with the suffix **.patch**. Use this variable to change that suffix (make sure to include the dot if you want it). format.encodeEmailHeaders Encode email headers that have non-ASCII characters with "Q-encoding" (described in RFC 2047) for email transmission. Defaults to true. format.pretty The default pretty format for log/show/whatchanged command, See [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), [**git-show**(1)](https://www.chedong.com/phpMan.php/man/git-show/1/markdown), [**git-whatchanged**(1)](https://www.chedong.com/phpMan.php/man/git-whatchanged/1/markdown). format.thread The default threading style for _git_ _format-patch_. Can be a boolean value, or **shallow** or **deep**. **shallow** threading makes every mail a reply to the head of the series, where the head is chosen from the cover letter, the **--in-reply-to**, and the first patch mail, in this order. **deep** threading makes every mail a reply to the previous one. A true boolean value is the same as **shallow**, and a false value disables threading. format.signOff A boolean value which lets you enable the **-s/--signoff** option of format-patch by default. **Note:** Adding the **Signed-off-by** trailer to a patch should be a conscious act and means that you certify you have the rights to submit this work under the same open source license. Please see the _SubmittingPatches_ document for further discussion. format.coverLetter A boolean that controls whether to generate a cover-letter when format-patch is invoked, but in addition can be set to "auto", to generate a cover-letter only when there’s more than one patch. Default is false. format.outputDirectory Set a custom directory to store the resulting files instead of the current working directory. All directory components will be created. format.filenameMaxLength The maximum length of the output filenames generated by the **format-patch** command; defaults to 64. Can be overridden by the **--filename-max-length=** command line option. format.useAutoBase A boolean value which lets you enable the **--base=auto** option of format-patch by default. Can also be set to "whenAble" to allow enabling **--base=auto** if a suitable base is available, but to skip adding base info otherwise without the format dying. format.notes Provides the default value for the **--notes** option to format-patch. Accepts a boolean value, or a ref which specifies where to get notes. If false, format-patch defaults to **--no-notes**. If true, format-patch defaults to **--notes**. If set to a non-boolean value, format-patch defaults to **--notes=**, where **ref** is the non-boolean value. Defaults to false. If one wishes to use the ref **ref/notes/true**, please use that literal instead. This configuration can be specified multiple times in order to allow multiple notes refs to be included. In that case, it will behave similarly to multiple **--[no-]notes[=]** options passed in. That is, a value of **true** will show the default notes, a value of **** will also show notes from that notes ref and a value of **false** will negate previous configurations and not show notes. For example, [format] notes = true notes = foo notes = false notes = bar will only show notes from **refs/notes/bar**. filter..clean The command which is used to convert the content of a worktree file to a blob upon checkin. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. filter..smudge The command which is used to convert the content of a blob object to a worktree file upon checkout. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details. fsck. During fsck git may find issues with legacy data which wouldn’t be generated by current versions of git, and which wouldn’t be sent over the wire if **transfer.fsckObjects** was set. This feature is intended to support working with legacy repositories containing such data. Setting **fsck.** will be picked up by [**git-fsck**(1)](https://www.chedong.com/phpMan.php/man/git-fsck/1/markdown), but to accept pushes of such data set **receive.fsck.** instead, or to clone or fetch it set **fetch.fsck.**. The rest of the documentation discusses **fsck.*** for brevity, but the same applies for the corresponding **receive.fsck.*** and **fetch..***. variables. Unlike variables like **color.ui** and **core.editor** the **receive.fsck.** and **fetch.fsck.** variables will not fall back on the **fsck.** configuration if they aren’t set. To uniformly configure the same fsck settings in different circumstances all three of them they must all set to the same values. When **fsck.** is set, errors can be switched to warnings and vice versa by configuring the **fsck.** setting where the **** is the fsck message ID and the value is one of **error**, **warn** or **ignore**. For convenience, fsck prefixes the error/warning with the message ID, e.g. "missingEmail: invalid author/committer line - missing email" means that setting **fsck.missingEmail** **=** **ignore** will hide that issue. In general, it is better to enumerate existing objects with problems with **fsck.skipList**, instead of listing the kind of breakages these problematic objects share to be ignored, as doing the latter will allow new instances of the same breakages go unnoticed. Setting an unknown **fsck.** value will cause fsck to die, but doing the same for **receive.fsck.** and **fetch.fsck.** will only cause git to warn. fsck.skipList The path to a list of object names (i.e. one unabbreviated SHA-1 per line) that are known to be broken in a non-fatal way and should be ignored. On versions of Git 2.20 and later comments (_#_), empty lines, and any leading and trailing whitespace is ignored. Everything but a SHA-1 per line will error out on older versions. This feature is useful when an established project should be accepted despite early commits containing errors that can be safely ignored such as invalid committer email addresses. Note: corrupt objects cannot be skipped with this setting. Like **fsck.** this variable has corresponding **receive.fsck.skipList** and **fetch.fsck.skipList** variants. Unlike variables like **color.ui** and **core.editor** the **receive.fsck.skipList** and **fetch.fsck.skipList** variables will not fall back on the **fsck.skipList** configuration if they aren’t set. To uniformly configure the same fsck settings in different circumstances all three of them they must all set to the same values. Older versions of Git (before 2.20) documented that the object names list should be sorted. This was never a requirement, the object names could appear in any order, but when reading the list we tracked whether the list was sorted for the purposes of an internal binary search implementation, which could save itself some work with an already sorted list. Unless you had a humongous list there was no reason to go out of your way to pre-sort the list. After Git version 2.20 a hash implementation is used instead, so there’s now no reason to pre-sort the list. gc.aggressiveDepth The depth parameter used in the delta compression algorithm used by _git_ _gc_ _--aggressive_. This defaults to 50, which is the default for the **--depth** option when **--aggressive** isn’t in use. See the documentation for the **--depth** option in [**git-repack**(1)](https://www.chedong.com/phpMan.php/man/git-repack/1/markdown) for more details. gc.aggressiveWindow The window size parameter used in the delta compression algorithm used by _git_ _gc_ _--aggressive_. This defaults to 250, which is a much more aggressive window size than the default **--window** of 10. See the documentation for the **--window** option in [**git-repack**(1)](https://www.chedong.com/phpMan.php/man/git-repack/1/markdown) for more details. gc.auto When there are approximately more than this many loose objects in the repository, **git** **gc** **--auto** will pack them. Some Porcelain commands use this command to perform a light-weight garbage collection from time to time. The default value is 6700. Setting this to 0 disables not only automatic packing based on the number of loose objects, but any other heuristic **git** **gc** **--auto** will otherwise use to determine if there’s work to do, such as **gc.autoPackLimit**. gc.autoPackLimit When there are more than this many packs that are not marked with ***.keep** file in the repository, **git** **gc** **--auto** consolidates them into one larger pack. The default value is 50. Setting this to 0 disables it. Setting **gc.auto** to 0 will also disable this. See the **gc.bigPackThreshold** configuration variable below. When in use, it’ll affect how the auto pack limit works. gc.autoDetach Make **git** **gc** **--auto** return immediately and run in background if the system supports it. Default is true. gc.bigPackThreshold If non-zero, all packs larger than this limit are kept when **git** **gc** is run. This is very similar to **--keep-largest-pack** except that all packs that meet the threshold are kept, not just the largest pack. Defaults to zero. Common unit suffixes of _k_, _m_, or _g_ are supported. Note that if the number of kept packs is more than gc.autoPackLimit, this configuration variable is ignored, all packs except the base pack will be repacked. After this the number of packs should go below gc.autoPackLimit and gc.bigPackThreshold should be respected again. If the amount of memory estimated for **git** **repack** to run smoothly is not available and **gc.bigPackThreshold** is not set, the largest pack will also be excluded (this is the equivalent of running **git** **gc** with **--keep-largest-pack**). gc.writeCommitGraph If true, then gc will rewrite the commit-graph file when [**git-gc**(1)](https://www.chedong.com/phpMan.php/man/git-gc/1/markdown) is run. When using **git** **gc** **--auto** the commit-graph will be updated if housekeeping is required. Default is true. See [**git-commit-graph**(1)](https://www.chedong.com/phpMan.php/man/git-commit-graph/1/markdown) for details. gc.logExpiry If the file gc.log exists, then **git** **gc** **--auto** will print its content and exit with status zero instead of running unless that file is more than _gc.logExpiry_ old. Default is "1.day". See **gc.pruneExpire** for more ways to specify its value. gc.packRefs Running **git** **pack-refs** in a repository renders it unclonable by Git versions prior to 1.5.1.2 over dumb transports such as HTTP. This variable determines whether _git_ _gc_ runs **git** **pack-refs**. This can be set to **notbare** to enable it within all non-bare repos or it can be set to a boolean value. The default is **true**. gc.pruneExpire When _git_ _gc_ is run, it will call _prune_ _--expire_ _2.weeks.ago_. Override the grace period with this config variable. The value "now" may be used to disable this grace period and always prune unreachable objects immediately, or "never" may be used to suppress pruning. This feature helps prevent corruption when _git_ _gc_ runs concurrently with another process writing to the repository; see the "NOTES" section of [**git-gc**(1)](https://www.chedong.com/phpMan.php/man/git-gc/1/markdown). gc.worktreePruneExpire When _git_ _gc_ is run, it calls _git_ _worktree_ _prune_ _--expire_ _3.months.ago_. This config variable can be used to set a different grace period. The value "now" may be used to disable the grace period and prune **$GIT**___**DIR/worktrees** immediately, or "never" may be used to suppress pruning. gc.reflogExpire, gc..reflogExpire _git_ _reflog_ _expire_ removes reflog entries older than this time; defaults to 90 days. The value "now" expires all entries immediately, and "never" suppresses expiration altogether. With "" (e.g. "refs/stash") in the middle the setting applies only to the refs that match the . gc.reflogExpireUnreachable, gc..reflogExpireUnreachable _git_ _reflog_ _expire_ removes reflog entries older than this time and are not reachable from the current tip; defaults to 30 days. The value "now" expires all entries immediately, and "never" suppresses expiration altogether. With "" (e.g. "refs/stash") in the middle, the setting applies only to the refs that match the . These types of entries are generally created as a result of using **git** **commit** **--amend** or **git** **rebase** and are the commits prior to the amend or rebase occurring. Since these changes are not part of the current project most users will want to expire them sooner, which is why the default is more aggressive than **gc.reflogExpire**. gc.rerereResolved Records of conflicted merge you resolved earlier are kept for this many days when _git_ _rerere_ _gc_ is run. You can also use more human-readable "1.month.ago", etc. The default is 60 days. See [**git-rerere**(1)](https://www.chedong.com/phpMan.php/man/git-rerere/1/markdown). gc.rerereUnresolved Records of conflicted merge you have not resolved are kept for this many days when _git_ _rerere_ _gc_ is run. You can also use more human-readable "1.month.ago", etc. The default is 15 days. See [**git-rerere**(1)](https://www.chedong.com/phpMan.php/man/git-rerere/1/markdown). gitcvs.commitMsgAnnotation Append this string to each commit message. Set to empty string to disable this feature. Defaults to "via git-CVS emulator". gitcvs.enabled Whether the CVS server interface is enabled for this repository. See [**git-cvsserver**(1)](https://www.chedong.com/phpMan.php/man/git-cvsserver/1/markdown). gitcvs.logFile Path to a log file where the CVS server interface well... logs various stuff. See **git-** [**cvsserver**(1)](https://www.chedong.com/phpMan.php/man/cvsserver/1/markdown). gitcvs.usecrlfattr If true, the server will look up the end-of-line conversion attributes for files to determine the **-k** modes to use. If the attributes force Git to treat a file as text, the **-k** mode will be left blank so CVS clients will treat it as text. If they suppress text conversion, the file will be set with _-kb_ mode, which suppresses any newline munging the client might otherwise do. If the attributes do not allow the file type to be determined, then **gitcvs.allBinary** is used. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown). gitcvs.allBinary This is used if **gitcvs.usecrlfattr** does not resolve the correct _-kb_ mode to use. If true, all unresolved files are sent to the client in mode _-kb_. This causes the client to treat them as binary files, which suppresses any newline munging it otherwise might do. Alternatively, if it is set to "guess", then the contents of the file are examined to decide if it is binary, similar to **core.autocrlf**. gitcvs.dbName Database used by git-cvsserver to cache revision information derived from the Git repository. The exact meaning depends on the used database driver, for SQLite (which is the default driver) this is a filename. Supports variable substitution (see **git-** [**cvsserver**(1)](https://www.chedong.com/phpMan.php/man/cvsserver/1/markdown) for details). May not contain semicolons (**;**). Default: _%Ggitcvs.%m.sqlite_ gitcvs.dbDriver Used Perl DBI driver. You can specify any available driver for this here, but it might not work. git-cvsserver is tested with [_DBD::SQLite_](https://www.chedong.com/phpMan.php/perldoc/DBD%3A%3ASQLite/markdown), reported to work with [_DBD::Pg_](https://www.chedong.com/phpMan.php/perldoc/DBD%3A%3APg/markdown), and reported **not** to work with [_DBD::mysql_](https://www.chedong.com/phpMan.php/perldoc/DBD%3A%3Amysql/markdown). Experimental feature. May not contain double colons (**:**). Default: _SQLite_. See [**git-cvsserver**(1)](https://www.chedong.com/phpMan.php/man/git-cvsserver/1/markdown). gitcvs.dbUser, gitcvs.dbPass Database user and password. Only useful if setting **gitcvs.dbDriver**, since SQLite has no concept of database users and/or passwords. _gitcvs.dbUser_ supports variable substitution (see [**git-cvsserver**(1)](https://www.chedong.com/phpMan.php/man/git-cvsserver/1/markdown) for details). gitcvs.dbTableNamePrefix Database table name prefix. Prepended to the names of any database tables used, allowing a single database to be used for several repositories. Supports variable substitution (see [**git-cvsserver**(1)](https://www.chedong.com/phpMan.php/man/git-cvsserver/1/markdown) for details). Any non-alphabetic characters will be replaced with underscores. All gitcvs variables except for **gitcvs.usecrlfattr** and **gitcvs.allBinary** can also be specified as _gitcvs.._ (where _access_method_ is one of "ext" and "pserver") to make them apply only for the given access method. gitweb.category, gitweb.description, gitweb.owner, gitweb.url See [**gitweb**(1)](https://www.chedong.com/phpMan.php/man/gitweb/1/markdown) for description. gitweb.avatar, gitweb.blame, gitweb.grep, gitweb.highlight, gitweb.patches, gitweb.pickaxe, gitweb.remote_heads, gitweb.showSizes, gitweb.snapshot See [**gitweb.conf**(5)](https://www.chedong.com/phpMan.php/man/gitweb.conf/5/markdown) for description. grep.lineNumber If set to true, enable **-n** option by default. grep.column If set to true, enable the **--column** option by default. grep.patternType Set the default matching behavior. Using a value of _basic_, _extended_, _fixed_, or _perl_ will enable the **--basic-regexp**, **--extended-regexp**, **--fixed-strings**, or **--perl-regexp** option accordingly, while the value _default_ will return to the default matching behavior. grep.extendedRegexp If set to true, enable **--extended-regexp** option by default. This option is ignored when the **grep.patternType** option is set to a value other than _default_. grep.threads Number of grep worker threads to use. See **grep.threads** in [**git-grep**(1)](https://www.chedong.com/phpMan.php/man/git-grep/1/markdown) for more information. grep.fallbackToNoIndex If set to true, fall back to git grep --no-index if git grep is executed outside of a git repository. Defaults to false. gpg.program Use this custom program instead of "**gpg**" found on **$PATH** when making or verifying a PGP signature. The program must support the same command-line interface as GPG, namely, to verify a detached signature, "**gpg** **--verify** **$signature** **-** **<$file**" is run, and the program is expected to signal a good signature by exiting with code 0, and to generate an ASCII-armored detached signature, the standard input of "**gpg** **-bsau** **$key**" is fed with the contents to be signed, and the program is expected to send the result to its standard output. gpg.format Specifies which key format to use when signing with **--gpg-sign**. Default is "openpgp". Other possible values are "x509", "ssh". gpg..program Use this to customize the program used for the signing format you chose. (see **gpg.program** and **gpg.format**) **gpg.program** can still be used as a legacy synonym for **gpg.openpgp.program**. The default value for **gpg.x509.program** is "gpgsm" and **gpg.ssh.program** is "ssh-keygen". gpg.minTrustLevel Specifies a minimum trust level for signature verification. If this option is unset, then signature verification for merge operations require a key with at least **marginal** trust. Other operations that perform signature verification require a key with at least **undefined** trust. Setting this option overrides the required trust-level for all operations. Supported values, in increasing order of significance: • **undefined** • **never** • **marginal** • **fully** • **ultimate** gpg.ssh.defaultKeyCommand: This command that will be run when user.signingkey is not set and a ssh signature is requested. On successful exit a valid ssh public key is expected in the first line of its output. To automatically use the first available key from your ssh-agent set this to "ssh-add -L". gpg.ssh.allowedSignersFile A file containing ssh public keys which you are willing to trust. The file consists of one or more lines of principals followed by an ssh public key. e.g.: ****[1],****[2] ssh-rsa AAAAX1... See [ssh-keygen(1)](https://www.chedong.com/phpMan.php/man/ssh-keygen/1/markdown) "ALLOWED SIGNERS" for details. The principal is only used to identify the key and is available when verifying a signature. SSH has no concept of trust levels like gpg does. To be able to differentiate between valid signatures and trusted signatures the trust level of a signature verification is set to **fully** when the public key is present in the allowedSignersFile. Otherwise the trust level is **undefined** and git verify-commit/tag will fail. This file can be set to a location outside of the repository and every developer maintains their own trust store. A central repository server could generate this file automatically from ssh keys with push access to verify the code against. In a corporate setting this file is probably generated at a global location from automation that already handles developer ssh keys. A repository that only allows signed commits can store the file in the repository itself using a path relative to the top-level of the working tree. This way only committers with an already valid key can add or change keys in the keyring. Using a SSH CA key with the cert-authority option (see [ssh-keygen(1)](https://www.chedong.com/phpMan.php/man/ssh-keygen/1/markdown) "CERTIFICATES") is also valid. gpg.ssh.revocationFile Either a SSH KRL or a list of revoked public keys (without the principal prefix). See [ssh-keygen(1)](https://www.chedong.com/phpMan.php/man/ssh-keygen/1/markdown) for details. If a public key is found in this file then it will always be treated as having trust level "never" and signatures will show as invalid. gui.commitMsgWidth Defines how wide the commit message window is in the [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown). "75" is the default. gui.diffContext Specifies how many context lines should be used in calls to diff made by the [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown). The default is "5". gui.displayUntracked Determines if [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown) shows untracked files in the file list. The default is "true". gui.encoding Specifies the default character encoding to use for displaying of file contents in **git-** [**gui**(1)](https://www.chedong.com/phpMan.php/man/gui/1/markdown) and [**gitk**(1)](https://www.chedong.com/phpMan.php/man/gitk/1/markdown). It can be overridden by setting the _encoding_ attribute for relevant files (see [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown)). If this option is not set, the tools default to the locale encoding. gui.matchTrackingBranch Determines if new branches created with [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown) should default to tracking remote branches with matching names or not. Default: "false". gui.newBranchTemplate Is used as suggested name when creating new branches using the [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown). gui.pruneDuringFetch "true" if [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown) should prune remote-tracking branches when performing a fetch. The default value is "false". gui.trustmtime Determines if [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown) should trust the file modification timestamp or not. By default the timestamps are not trusted. gui.spellingDictionary Specifies the dictionary used for spell checking commit messages in the [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown). When set to "none" spell checking is turned off. gui.fastCopyBlame If true, _git_ _gui_ _blame_ uses **-C** instead of **-C** **-C** for original location detection. It makes blame significantly faster on huge repositories at the expense of less thorough copy detection. gui.copyBlameThreshold Specifies the threshold to use in _git_ _gui_ _blame_ original location detection, measured in alphanumeric characters. See the [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown) manual for more information on copy detection. gui.blamehistoryctx Specifies the radius of history context in days to show in [**gitk**(1)](https://www.chedong.com/phpMan.php/man/gitk/1/markdown) for the selected commit, when the **Show** **History** **Context** menu item is invoked from _git_ _gui_ _blame_. If this variable is set to zero, the whole history is shown. guitool..cmd Specifies the shell command line to execute when the corresponding item of the [**git-gui**(1)](https://www.chedong.com/phpMan.php/man/git-gui/1/markdown) **Tools** menu is invoked. This option is mandatory for every tool. The command is executed from the root of the working directory, and in the environment it receives the name of the tool as **GIT**___**GUITOOL**, the name of the currently selected file as _FILENAME_, and the name of the current branch as _CUR_BRANCH_ (if the head is detached, _CUR_BRANCH_ is empty). guitool..needsFile Run the tool only if a diff is selected in the GUI. It guarantees that _FILENAME_ is not empty. guitool..noConsole Run the command silently, without creating a window to display its output. guitool..noRescan Don’t rescan the working directory for changes after the tool finishes execution. guitool..confirm Show a confirmation dialog before actually running the tool. guitool..argPrompt Request a string argument from the user, and pass it to the tool through the **ARGS** environment variable. Since requesting an argument implies confirmation, the _confirm_ option has no effect if this is enabled. If the option is set to _true_, _yes_, or _1_, the dialog uses a built-in generic prompt; otherwise the exact value of the variable is used. guitool..revPrompt Request a single valid revision from the user, and set the **REVISION** environment variable. In other aspects this option is similar to _argPrompt_, and can be used together with it. guitool..revUnmerged Show only unmerged branches in the _revPrompt_ subdialog. This is useful for tools similar to merge or rebase, but not for things like checkout or reset. guitool..title Specifies the title to use for the prompt dialog. The default is the tool name. guitool..prompt Specifies the general prompt string to display at the top of the dialog, before subsections for _argPrompt_ and _revPrompt_. The default value includes the actual command. help.browser Specify the browser that will be used to display help in the _web_ format. See [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown). help.format Override the default help format used by [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown). Values _man_, _info_, _web_ and _html_ are supported. _man_ is the default. _web_ and _html_ are the same. help.autoCorrect If git detects typos and can identify exactly one valid command similar to the error, git will try to suggest the correct command or even run the suggestion automatically. Possible config values are: • 0 (default): show the suggested command. • positive number: run the suggested command after specified deciseconds (0.1 sec). • "immediate": run the suggested command immediately. • "prompt": show the suggestion and prompt for confirmation to run the command. • "never": don’t run or show any suggested command. help.htmlPath Specify the path where the HTML documentation resides. File system paths and URLs are supported. HTML pages will be prefixed with this path when help is displayed in the _web_ format. This defaults to the documentation path of your Git installation. http.proxy Override the HTTP proxy, normally configured using the _http_proxy_, _https_proxy_, and _all_proxy_ environment variables (see [**curl(1)](https://www.chedong.com/phpMan.php/man/curl/1/markdown)**). In addition to the syntax understood by curl, it is possible to specify a proxy string with a user name but no password, in which case git will attempt to acquire one in the same way it does for other credentials. See [**gitcredentials**(7)](https://www.chedong.com/phpMan.php/man/gitcredentials/7/markdown) for more information. The syntax thus is _[protocol://][user[:password]@]proxyhost[:port]_. This can be overridden on a per-remote basis; see remote..proxy http.proxyAuthMethod Set the method with which to authenticate against the HTTP proxy. This only takes effect if the configured proxy string contains a user name part (i.e. is of the form _user@host_ or _user@host:port_). This can be overridden on a per-remote basis; see **remote..proxyAuthMethod**. Both can be overridden by the **GIT**___**HTTP**___**PROXY**___**AUTHMETHOD** environment variable. Possible values are: • **anyauth** - Automatically pick a suitable authentication method. It is assumed that the proxy answers an unauthenticated request with a 407 status code and one or more Proxy-authenticate headers with supported authentication methods. This is the default. • **basic** - HTTP Basic authentication • **digest** - HTTP Digest authentication; this prevents the password from being transmitted to the proxy in clear text • **negotiate** - GSS-Negotiate authentication (compare the --negotiate option of [**curl(1)](https://www.chedong.com/phpMan.php/man/curl/1/markdown)**) • **ntlm** - NTLM authentication (compare the --ntlm option of [**curl(1)](https://www.chedong.com/phpMan.php/man/curl/1/markdown)**) http.proxySSLCert The pathname of a file that stores a client certificate to use to authenticate with an HTTPS proxy. Can be overridden by the **GIT**___**PROXY**___**SSL**___**CERT** environment variable. http.proxySSLKey The pathname of a file that stores a private key to use to authenticate with an HTTPS proxy. Can be overridden by the **GIT**___**PROXY**___**SSL**___**KEY** environment variable. http.proxySSLCertPasswordProtected Enable Git’s password prompt for the proxy SSL certificate. Otherwise OpenSSL will prompt the user, possibly many times, if the certificate or private key is encrypted. Can be overridden by the **GIT**___**PROXY**___**SSL**___**CERT**___**PASSWORD**___**PROTECTED** environment variable. http.proxySSLCAInfo Pathname to the file containing the certificate bundle that should be used to verify the proxy with when using an HTTPS proxy. Can be overridden by the **GIT**___**PROXY**___**SSL**___**CAINFO** environment variable. http.emptyAuth Attempt authentication without seeking a username or password. This can be used to attempt GSS-Negotiate authentication without specifying a username in the URL, as libcurl normally requires a username for authentication. http.delegation Control GSSAPI credential delegation. The delegation is disabled by default in libcurl since version 7.21.7. Set parameter to tell the server what it is allowed to delegate when it comes to user credentials. Used with GSS/kerberos. Possible values are: • **none** - Don’t allow any delegation. • **policy** - Delegates if and only if the OK-AS-DELEGATE flag is set in the Kerberos service ticket, which is a matter of realm policy. • **always** - Unconditionally allow the server to delegate. http.extraHeader Pass an additional HTTP header when communicating with a server. If more than one such entry exists, all of them are added as extra headers. To allow overriding the settings inherited from the system config, an empty value will reset the extra headers to the empty list. http.cookieFile The pathname of a file containing previously stored cookie lines, which should be used in the Git http session, if they match the server. The file format of the file to read cookies from should be plain HTTP headers or the Netscape/Mozilla cookie file format (see [**curl(1)](https://www.chedong.com/phpMan.php/man/curl/1/markdown)**). NOTE that the file specified with http.cookieFile is used only as input unless http.saveCookies is set. http.saveCookies If set, store cookies received during requests to the file specified by http.cookieFile. Has no effect if http.cookieFile is unset. http.version Use the specified HTTP protocol version when communicating with a server. If you want to force the default. The available and default version depend on libcurl. Currently the possible values of this option are: • HTTP/2 • HTTP/1.1 http.sslVersion The SSL version to use when negotiating an SSL connection, if you want to force the default. The available and default version depend on whether libcurl was built against NSS or OpenSSL and the particular configuration of the crypto library in use. Internally this sets the _CURLOPT_SSL_VERSION_ option; see the libcurl documentation for more details on the format of this option and for the ssl version supported. Currently the possible values of this option are: • sslv2 • sslv3 • tlsv1 • tlsv1.0 • tlsv1.1 • tlsv1.2 • tlsv1.3 Can be overridden by the **GIT**___**SSL**___**VERSION** environment variable. To force git to use libcurl’s default ssl version and ignore any explicit http.sslversion option, set **GIT**___**SSL**___**VERSION** to the empty string. http.sslCipherList A list of SSL ciphers to use when negotiating an SSL connection. The available ciphers depend on whether libcurl was built against NSS or OpenSSL and the particular configuration of the crypto library in use. Internally this sets the _CURLOPT_SSL_CIPHER_LIST_ option; see the libcurl documentation for more details on the format of this list. Can be overridden by the **GIT**___**SSL**___**CIPHER**___**LIST** environment variable. To force git to use libcurl’s default cipher list and ignore any explicit http.sslCipherList option, set **GIT**___**SSL**___**CIPHER**___**LIST** to the empty string. http.sslVerify Whether to verify the SSL certificate when fetching or pushing over HTTPS. Defaults to true. Can be overridden by the **GIT**___**SSL**___**NO**___**VERIFY** environment variable. http.sslCert File containing the SSL certificate when fetching or pushing over HTTPS. Can be overridden by the **GIT**___**SSL**___**CERT** environment variable. http.sslKey File containing the SSL private key when fetching or pushing over HTTPS. Can be overridden by the **GIT**___**SSL**___**KEY** environment variable. http.sslCertPasswordProtected Enable Git’s password prompt for the SSL certificate. Otherwise OpenSSL will prompt the user, possibly many times, if the certificate or private key is encrypted. Can be overridden by the **GIT**___**SSL**___**CERT**___**PASSWORD**___**PROTECTED** environment variable. http.sslCAInfo File containing the certificates to verify the peer with when fetching or pushing over HTTPS. Can be overridden by the **GIT**___**SSL**___**CAINFO** environment variable. http.sslCAPath Path containing files with the CA certificates to verify the peer with when fetching or pushing over HTTPS. Can be overridden by the **GIT**___**SSL**___**CAPATH** environment variable. http.sslBackend Name of the SSL backend to use (e.g. "openssl" or "schannel"). This option is ignored if cURL lacks support for choosing the SSL backend at runtime. http.schannelCheckRevoke Used to enforce or disable certificate revocation checks in cURL when http.sslBackend is set to "schannel". Defaults to **true** if unset. Only necessary to disable this if Git consistently errors and the message is about checking the revocation status of a certificate. This option is ignored if cURL lacks support for setting the relevant SSL option at runtime. http.schannelUseSSLCAInfo As of cURL v7.60.0, the Secure Channel backend can use the certificate bundle provided via **http.sslCAInfo**, but that would override the Windows Certificate Store. Since this is not desirable by default, Git will tell cURL not to use that bundle by default when the **schannel** backend was configured via **http.sslBackend**, unless **http.schannelUseSSLCAInfo** overrides this behavior. http.pinnedpubkey Public key of the https service. It may either be the filename of a PEM or DER encoded public key file or a string starting with _sha256//_ followed by the base64 encoded sha256 hash of the public key. See also libcurl _CURLOPT_PINNEDPUBLICKEY_. git will exit with an error if this option is set but not supported by cURL. http.sslTry Attempt to use AUTH SSL/TLS and encrypted data transfers when connecting via regular FTP protocol. This might be needed if the FTP server requires it for security reasons or you wish to connect securely whenever remote FTP server supports it. Default is false since it might trigger certificate verification errors on misconfigured servers. http.maxRequests How many HTTP requests to launch in parallel. Can be overridden by the **GIT**___**HTTP**___**MAX**___**REQUESTS** environment variable. Default is 5. http.minSessions The number of curl sessions (counted across slots) to be kept across requests. They will not be ended with curl_easy_cleanup() until http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this value will be capped at 1. Defaults to 1. http.postBuffer Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests. Note that raising this limit is only effective for disabling chunked transfer encoding and therefore should be used only where the remote server or a proxy only supports HTTP/1.0 or is noncompliant with the HTTP standard. Raising this is not, in general, an effective solution for most push problems, but can increase memory consumption significantly since the entire buffer is allocated even for small pushes. http.lowSpeedLimit, http.lowSpeedTime If the HTTP transfer speed is less than _http.lowSpeedLimit_ for longer than _http.lowSpeedTime_ seconds, the transfer is aborted. Can be overridden by the **GIT**___**HTTP**___**LOW**___**SPEED**___**LIMIT** and **GIT**___**HTTP**___**LOW**___**SPEED**___**TIME** environment variables. http.noEPSV A boolean which disables using of EPSV ftp command by curl. This can helpful with some "poor" ftp servers which don’t support EPSV mode. Can be overridden by the **GIT**___**CURL**___**FTP**___**NO**___**EPSV** environment variable. Default is false (curl will use EPSV). http.userAgent The HTTP USER_AGENT string presented to an HTTP server. The default value represents the version of the client Git such as git/1.7.1. This option allows you to override this value to a more common value such as Mozilla/4.0. This may be necessary, for instance, if connecting through a firewall that restricts HTTP connections to a set of common USER_AGENT strings (but not including those like git/1.7.1). Can be overridden by the **GIT**___**HTTP**___**USER**___**AGENT** environment variable. http.followRedirects Whether git should follow HTTP redirects. If set to **true**, git will transparently follow any redirect issued by a server it encounters. If set to **false**, git will treat all redirects as errors. If set to **initial**, git will follow redirects only for the initial request to a remote, but not for subsequent follow-up HTTP requests. Since git uses the redirected URL as the base for the follow-up requests, this is generally sufficient. The default is **initial**. http..* Any of the http.* options above can be applied selectively to some URLs. For a config key to match a URL, each element of the config key is compared to that of the URL, in the following order: 1. Scheme (e.g., **https** in ****). This field must match exactly between the config key and the URL. 2. Host/domain name (e.g., **example.com** in ****). This field must match between the config key and the URL. It is possible to specify a ***** as part of the host name to match all subdomains at this level. **https://*.example.com/** for example would match ****, but not ****. 3. Port number (e.g., **8080** in ****). This field must match exactly between the config key and the URL. Omitted port numbers are automatically converted to the correct default for the scheme before matching. 4. Path (e.g., **repo.git** in ****). The path field of the config key must match the path field of the URL either exactly or as a prefix of slash-delimited path elements. This means a config key with path **foo/** matches URL path **foo/bar**. A prefix can only match on a slash (**/**) boundary. Longer matches take precedence (so a config key with path **foo/bar** is a better match to URL path **foo/bar** than a config key with just path **foo/**). 5. User name (e.g., **user** in **https:///repo.git**). If the config key has a user name it must match the user name in the URL exactly. If the config key does not have a user name, that config key will match a URL with any user name (including none), but at a lower precedence than a config key with a user name. The list above is ordered by decreasing precedence; a URL that matches a config key’s path is preferred to one that matches its user name. For example, if the URL is **https:///foo/bar** a config key match of **** will be preferred over a config key match of **https://**. All URLs are normalized before attempting any matching (the password part, if embedded in the URL, is always ignored for matching purposes) so that equivalent URLs that are simply spelled differently will match properly. Environment variable settings always override any matches. The URLs that are matched against are those given directly to Git commands. This means any URLs visited as a result of a redirection do not participate in matching. i18n.commitEncoding Character encoding the commit messages are stored in; Git itself does not care per se, but this information is necessary e.g. when importing commits from emails or in the gitk graphical history browser (and possibly at other places in the future or in other porcelains). See e.g. [**git-mailinfo**(1)](https://www.chedong.com/phpMan.php/man/git-mailinfo/1/markdown). Defaults to _utf-8_. i18n.logOutputEncoding Character encoding the commit messages are converted to when running _git_ _log_ and friends. imap.folder The folder to drop the mails into, which is typically the Drafts folder. For example: "INBOX.Drafts", "INBOX/Drafts" or "[Gmail]/Drafts". Required. imap.tunnel Command used to setup a tunnel to the IMAP server through which commands will be piped instead of using a direct network connection to the server. Required when imap.host is not set. imap.host A URL identifying the server. Use an **imap://** prefix for non-secure connections and an **imaps://** prefix for secure connections. Ignored when imap.tunnel is set, but required otherwise. imap.user The username to use when logging in to the server. imap.pass The password to use when logging in to the server. imap.port An integer port number to connect to on the server. Defaults to 143 for imap:// hosts and 993 for imaps:// hosts. Ignored when imap.tunnel is set. imap.sslverify A boolean to enable/disable verification of the server certificate used by the SSL/TLS connection. Default is **true**. Ignored when imap.tunnel is set. imap.preformattedHTML A boolean to enable/disable the use of html encoding when sending a patch. An html encoded patch will be bracketed with 
 and have a content type of text/html.
           Ironically, enabling this option causes Thunderbird to send the patch as a plain/text,
           format=fixed email. Default is **false**.

       imap.authMethod
           Specify authenticate method for authentication with IMAP server. If Git was built with
           the NO_CURL option, or if your curl version is older than 7.34.0, or if you’re running
           git-imap-send with the **--no-curl** option, the only supported method is _CRAM-MD5_. If this
           is not set then _git_ _imap-send_ uses the basic IMAP plaintext LOGIN command.

       index.recordEndOfIndexEntries
           Specifies whether the index file should include an "End Of Index Entry" section. This
           reduces index load time on multiprocessor machines but produces a message "ignoring EOIE
           extension" when reading the index using Git versions before 2.20. Defaults to _true_ if
           index.threads has been explicitly enabled, _false_ otherwise.

       index.recordOffsetTable
           Specifies whether the index file should include an "Index Entry Offset Table" section.
           This reduces index load time on multiprocessor machines but produces a message "ignoring
           IEOT extension" when reading the index using Git versions before 2.20. Defaults to _true_
           if index.threads has been explicitly enabled, _false_ otherwise.

       index.sparse
           When enabled, write the index using sparse-directory entries. This has no effect unless
           **core.sparseCheckout** and **core.sparseCheckoutCone** are both enabled. Defaults to _false_.

       index.threads
           Specifies the number of threads to spawn when loading the index. This is meant to reduce
           index load time on multiprocessor machines. Specifying 0 or _true_ will cause Git to
           auto-detect the number of CPU’s and set the number of threads accordingly. Specifying 1
           or _false_ will disable multithreading. Defaults to _true_.

       index.version
           Specify the version with which new index files should be initialized. This does not
           affect existing repositories. If **feature.manyFiles** is enabled, then the default is 4.

       init.templateDir
           Specify the directory from which templates will be copied. (See the "TEMPLATE DIRECTORY"
           section of [**git-init**(1)](https://www.chedong.com/phpMan.php/man/git-init/1/markdown).)

       init.defaultBranch
           Allows overriding the default branch name e.g. when initializing a new repository.

       instaweb.browser
           Specify the program that will be used to browse your working repository in gitweb. See
           [**git-instaweb**(1)](https://www.chedong.com/phpMan.php/man/git-instaweb/1/markdown).

       instaweb.httpd
           The HTTP daemon command-line to start gitweb on your working repository. See **git-**
           [**instaweb**(1)](https://www.chedong.com/phpMan.php/man/instaweb/1/markdown).

       instaweb.local
           If true the web server started by [**git-instaweb**(1)](https://www.chedong.com/phpMan.php/man/git-instaweb/1/markdown) will be bound to the local IP
           (127.0.0.1).

       instaweb.modulePath
           The default module path for [**git-instaweb**(1)](https://www.chedong.com/phpMan.php/man/git-instaweb/1/markdown) to use instead of /usr/lib/apache2/modules.
           Only used if httpd is Apache.

       instaweb.port
           The port number to bind the gitweb httpd to. See [**git-instaweb**(1)](https://www.chedong.com/phpMan.php/man/git-instaweb/1/markdown).

       interactive.singleKey
           In interactive commands, allow the user to provide one-letter input with a single key
           (i.e., without hitting enter). Currently this is used by the **--patch** mode of [**git-add**(1)](https://www.chedong.com/phpMan.php/man/git-add/1/markdown),
           [**git-checkout**(1)](https://www.chedong.com/phpMan.php/man/git-checkout/1/markdown), [**git-restore**(1)](https://www.chedong.com/phpMan.php/man/git-restore/1/markdown), [**git-commit**(1)](https://www.chedong.com/phpMan.php/man/git-commit/1/markdown), [**git-reset**(1)](https://www.chedong.com/phpMan.php/man/git-reset/1/markdown), and [**git-stash**(1)](https://www.chedong.com/phpMan.php/man/git-stash/1/markdown). Note that
           this setting is silently ignored if portable keystroke input is not available; requires
           the Perl module [Term::ReadKey](https://www.chedong.com/phpMan.php/perldoc/Term%3A%3AReadKey/markdown).

       interactive.diffFilter
           When an interactive command (such as **git** **add** **--patch**) shows a colorized diff, git will
           pipe the diff through the shell command defined by this configuration variable. The
           command may mark up the diff further for human consumption, provided that it retains a
           one-to-one correspondence with the lines in the original diff. Defaults to disabled (no
           filtering).

       log.abbrevCommit
           If true, makes [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), [**git-show**(1)](https://www.chedong.com/phpMan.php/man/git-show/1/markdown), and [**git-whatchanged**(1)](https://www.chedong.com/phpMan.php/man/git-whatchanged/1/markdown) assume **--abbrev-commit**.
           You may override this option with **--no-abbrev-commit**.

       log.date
           Set the default date-time mode for the _log_ command. Setting a value for log.date is
           similar to using _git_ _log_'s **--date** option. See [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown) for details.

       log.decorate
           Print out the ref names of any commits that are shown by the log command. If _short_ is
           specified, the ref name prefixes _refs/heads/_, _refs/tags/_ and _refs/remotes/_ will not be
           printed. If _full_ is specified, the full ref name (including prefix) will be printed. If
           _auto_ is specified, then if the output is going to a terminal, the ref names are shown as
           if _short_ were given, otherwise no ref names are shown. This is the same as the **--decorate**
           option of the **git** **log**.

       log.excludeDecoration
           Exclude the specified patterns from the log decorations. This is similar to the
           **--decorate-refs-exclude** command-line option, but the config option can be overridden by
           the **--decorate-refs** option.

       log.diffMerges
           Set default diff format to be used for merge commits. See **--diff-merges** in [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown) for
           details. Defaults to **separate**.

       log.follow
           If **true**, **git** **log** will act as if the **--follow** option was used when a single  is
           given. This has the same limitations as **--follow**, i.e. it cannot be used to follow
           multiple files and does not work well on non-linear history.

       log.graphColors
           A list of colors, separated by commas, that can be used to draw history lines in **git** **log**
           **--graph**.

       log.showRoot
           If true, the initial commit will be shown as a big creation event. This is equivalent to
           a diff against an empty tree. Tools like [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown) or [**git-whatchanged**(1)](https://www.chedong.com/phpMan.php/man/git-whatchanged/1/markdown), which normally
           hide the root commit will now show it. True by default.

       log.showSignature
           If true, makes [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), [**git-show**(1)](https://www.chedong.com/phpMan.php/man/git-show/1/markdown), and [**git-whatchanged**(1)](https://www.chedong.com/phpMan.php/man/git-whatchanged/1/markdown) assume **--show-signature**.

       log.mailmap
           If true, makes [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown), [**git-show**(1)](https://www.chedong.com/phpMan.php/man/git-show/1/markdown), and [**git-whatchanged**(1)](https://www.chedong.com/phpMan.php/man/git-whatchanged/1/markdown) assume **--use-mailmap**,
           otherwise assume **--no-use-mailmap**. True by default.

       lsrefs.unborn
           May be "advertise" (the default), "allow", or "ignore". If "advertise", the server will
           respond to the client sending "unborn" (as described in protocol-v2.txt) and will
           advertise support for this feature during the protocol v2 capability advertisement.
           "allow" is the same as "advertise" except that the server will not advertise support for
           this feature; this is useful for load-balanced servers that cannot be updated atomically
           (for example), since the administrator could configure "allow", then after a delay,
           configure "advertise".

       mailinfo.scissors
           If true, makes [**git-mailinfo**(1)](https://www.chedong.com/phpMan.php/man/git-mailinfo/1/markdown) (and therefore [**git-am**(1)](https://www.chedong.com/phpMan.php/man/git-am/1/markdown)) act by default as if the
           --scissors option was provided on the command-line. When active, this features removes
           everything from the message body before a scissors line (i.e. consisting mainly of ">8",
           "8<" and "-").

       mailmap.file
           The location of an augmenting mailmap file. The default mailmap, located in the root of
           the repository, is loaded first, then the mailmap file pointed to by this variable. The
           location of the mailmap file may be in a repository subdirectory, or somewhere outside of
           the repository itself. See [**git-shortlog**(1)](https://www.chedong.com/phpMan.php/man/git-shortlog/1/markdown) and [**git-blame**(1)](https://www.chedong.com/phpMan.php/man/git-blame/1/markdown).

       mailmap.blob
           Like **mailmap.file**, but consider the value as a reference to a blob in the repository. If
           both **mailmap.file** and **mailmap.blob** are given, both are parsed, with entries from
           **mailmap.file** taking precedence. In a bare repository, this defaults to **HEAD:.mailmap**. In
           a non-bare repository, it defaults to empty.

       maintenance.auto
           This boolean config option controls whether some commands run **git** **maintenance** **run** **--auto**
           after doing their normal work. Defaults to true.

       maintenance.strategy
           This string config option provides a way to specify one of a few recommended schedules
           for background maintenance. This only affects which tasks are run during **git** **maintenance**
           **run** **--schedule=X** commands, provided no **--task=** arguments are provided. Further, if
           a **maintenance..schedule** config value is set, then that value is used instead of the
           one provided by **maintenance.strategy**. The possible strategy strings are:

           •   **none**: This default setting implies no task are run at any schedule.

           •   **incremental**: This setting optimizes for performing small maintenance activities that
               do not delete any data. This does not schedule the **gc** task, but runs the **prefetch** and
               **commit-graph** tasks hourly, the **loose-objects** and **incremental-repack** tasks daily, and
               the **pack-refs** task weekly.

       maintenance..enabled
           This boolean config option controls whether the maintenance task with name **** is run
           when no **--task** option is specified to **git** **maintenance** **run**. These config values are
           ignored if a **--task** option exists. By default, only **maintenance.gc.enabled** is true.

       maintenance..schedule
           This config option controls whether or not the given **** runs during a **git** **maintenance**
           **run** **--schedule=** command. The value must be one of "hourly", "daily", or
           "weekly".

       maintenance.commit-graph.auto
           This integer config option controls how often the **commit-graph** task should be run as part
           of **git** **maintenance** **run** **--auto**. If zero, then the **commit-graph** task will not run with the
           **--auto** option. A negative value will force the task to run every time. Otherwise, a
           positive value implies the command should run when the number of reachable commits that
           are not in the commit-graph file is at least the value of **maintenance.commit-graph.auto**.
           The default value is 100.

       maintenance.loose-objects.auto
           This integer config option controls how often the **loose-objects** task should be run as
           part of **git** **maintenance** **run** **--auto**. If zero, then the **loose-objects** task will not run
           with the **--auto** option. A negative value will force the task to run every time.
           Otherwise, a positive value implies the command should run when the number of loose
           objects is at least the value of **maintenance.loose-objects.auto**. The default value is
           100.

       maintenance.incremental-repack.auto
           This integer config option controls how often the **incremental-repack** task should be run
           as part of **git** **maintenance** **run** **--auto**. If zero, then the **incremental-repack** task will not
           run with the **--auto** option. A negative value will force the task to run every time.
           Otherwise, a positive value implies the command should run when the number of pack-files
           not in the multi-pack-index is at least the value of **maintenance.incremental-repack.auto**.
           The default value is 10.

       man.viewer
           Specify the programs that may be used to display help in the _man_ format. See [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown).

       man..cmd
           Specify the command to invoke the specified man viewer. The specified command is
           evaluated in shell with the man page passed as argument. (See [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown).)

       man..path
           Override the path for the given tool that may be used to display help in the _man_ format.
           See [**git-help**(1)](https://www.chedong.com/phpMan.php/man/git-help/1/markdown).

       merge.conflictStyle
           Specify the style in which conflicted hunks are written out to working tree files upon
           merge. The default is "merge", which shows a **<<<<<<<** conflict marker, changes made by one
           side, a **=======** marker, changes made by the other side, and then a **>>>>>>>** marker. An
           alternate style, "diff3", adds a **|||||||** marker and the original text before the **=======**
           marker.

       merge.defaultToUpstream
           If merge is called without any commit argument, merge the upstream branches configured
           for the current branch by using their last observed values stored in their
           remote-tracking branches. The values of the **branch..merge** that name the
           branches at the remote named by **branch..remote** are consulted, and then
           they are mapped via **remote..fetch** to their corresponding remote-tracking
           branches, and the tips of these tracking branches are merged. Defaults to true.

       merge.ff
           By default, Git does not create an extra merge commit when merging a commit that is a
           descendant of the current commit. Instead, the tip of the current branch is
           fast-forwarded. When set to **false**, this variable tells Git to create an extra merge
           commit in such a case (equivalent to giving the **--no-ff** option from the command line).
           When set to **only**, only such fast-forward merges are allowed (equivalent to giving the
           **--ff-only** option from the command line).

       merge.verifySignatures
           If true, this is equivalent to the --verify-signatures command line option. See **git-**
           [**merge**(1)](https://www.chedong.com/phpMan.php/man/merge/1/markdown) for details.

       merge.branchdesc
           In addition to branch names, populate the log message with the branch description text
           associated with them. Defaults to false.

       merge.log
           In addition to branch names, populate the log message with at most the specified number
           of one-line descriptions from the actual commits that are being merged. Defaults to
           false, and true is a synonym for 20.

       merge.suppressDest
           By adding a glob that matches the names of integration branches to this multi-valued
           configuration variable, the default merge message computed for merges into these
           integration branches will omit "into " from its title.

           An element with an empty value can be used to clear the list of globs accumulated from
           previous configuration entries. When there is no **merge.suppressDest** variable defined, the
           default value of **master** is used for backward compatibility.

       merge.renameLimit
           The number of files to consider in the exhaustive portion of rename detection during a
           merge. If not specified, defaults to the value of diff.renameLimit. If neither
           merge.renameLimit nor diff.renameLimit are specified, currently defaults to 7000. This
           setting has no effect if rename detection is turned off.

       merge.renames
           Whether Git detects renames. If set to "false", rename detection is disabled. If set to
           "true", basic rename detection is enabled. Defaults to the value of diff.renames.

       merge.directoryRenames
           Whether Git detects directory renames, affecting what happens at merge time to new files
           added to a directory on one side of history when that directory was renamed on the other
           side of history. If merge.directoryRenames is set to "false", directory rename detection
           is disabled, meaning that such new files will be left behind in the old directory. If set
           to "true", directory rename detection is enabled, meaning that such new files will be
           moved into the new directory. If set to "conflict", a conflict will be reported for such
           paths. If merge.renames is false, merge.directoryRenames is ignored and treated as false.
           Defaults to "conflict".

       merge.renormalize
           Tell Git that canonical representation of files in the repository has changed over time
           (e.g. earlier commits record text files with CRLF line endings, but recent ones use LF
           line endings). In such a repository, Git can convert the data recorded in commits to a
           canonical form before performing a merge to reduce unnecessary conflicts. For more
           information, see section "Merging branches with differing checkin/checkout attributes" in
           [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown).

       merge.stat
           Whether to print the diffstat between ORIG_HEAD and the merge result at the end of the
           merge. True by default.

       merge.autoStash
           When set to true, automatically create a temporary stash entry before the operation
           begins, and apply it after the operation ends. This means that you can run merge on a
           dirty worktree. However, use with care: the final stash application after a successful
           merge might result in non-trivial conflicts. This option can be overridden by the
           **--no-autostash** and **--autostash** options of [**git-merge**(1)](https://www.chedong.com/phpMan.php/man/git-merge/1/markdown). Defaults to false.

       merge.tool
           Controls which merge tool is used by [**git-mergetool**(1)](https://www.chedong.com/phpMan.php/man/git-mergetool/1/markdown). The list below shows the valid
           built-in values. Any other value is treated as a custom merge tool and requires that a
           corresponding mergetool..cmd variable is defined.

       merge.guitool
           Controls which merge tool is used by [**git-mergetool**(1)](https://www.chedong.com/phpMan.php/man/git-mergetool/1/markdown) when the -g/--gui flag is
           specified. The list below shows the valid built-in values. Any other value is treated as
           a custom merge tool and requires that a corresponding mergetool..cmd variable is
           defined.

           •   araxis

           •   bc

           •   bc3

           •   bc4

           •   codecompare

           •   deltawalker

           •   diffmerge

           •   diffuse

           •   ecmerge

           •   emerge

           •   examdiff

           •   guiffy

           •   gvimdiff

           •   gvimdiff1

           •   gvimdiff2

           •   gvimdiff3

           •   kdiff3

           •   meld

           •   nvimdiff

           •   nvimdiff1

           •   nvimdiff2

           •   nvimdiff3

           •   opendiff

           •   p4merge

           •   smerge

           •   tkdiff

           •   tortoisemerge

           •   vimdiff

           •   vimdiff1

           •   vimdiff2

           •   vimdiff3

           •   winmerge

           •   xxdiff

       merge.verbosity
           Controls the amount of output shown by the recursive merge strategy. Level 0 outputs
           nothing except a final error message if conflicts were detected. Level 1 outputs only
           conflicts, 2 outputs conflicts and file changes. Level 5 and above outputs debugging
           information. The default is level 2. Can be overridden by the **GIT**___**MERGE**___**VERBOSITY**
           environment variable.

       merge..name
           Defines a human-readable name for a custom low-level merge driver. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown)
           for details.

       merge..driver
           Defines the command that implements a custom low-level merge driver. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown)
           for details.

       merge..recursive
           Names a low-level merge driver to be used when performing an internal merge between
           common ancestors. See [**gitattributes**(5)](https://www.chedong.com/phpMan.php/man/gitattributes/5/markdown) for details.

       mergetool..path
           Override the path for the given tool. This is useful in case your tool is not in the
           PATH.

       mergetool..cmd
           Specify the command to invoke the specified merge tool. The specified command is
           evaluated in shell with the following variables available: _BASE_ is the name of a
           temporary file containing the common base of the files to be merged, if available; _LOCAL_
           is the name of a temporary file containing the contents of the file on the current
           branch; _REMOTE_ is the name of a temporary file containing the contents of the file from
           the branch being merged; _MERGED_ contains the name of the file to which the merge tool
           should write the results of a successful merge.

       mergetool..hideResolved
           Allows the user to override the global **mergetool.hideResolved** value for a specific tool.
           See **mergetool.hideResolved** for the full description.

       mergetool..trustExitCode
           For a custom merge command, specify whether the exit code of the merge command can be
           used to determine whether the merge was successful. If this is not set to true then the
           merge target file timestamp is checked and the merge assumed to have been successful if
           the file has been updated, otherwise the user is prompted to indicate the success of the
           merge.

       mergetool.meld.hasOutput
           Older versions of **meld** do not support the **--output** option. Git will attempt to detect
           whether **meld** supports **--output** by inspecting the output of **meld** **--help**. Configuring
           **mergetool.meld.hasOutput** will make Git skip these checks and use the configured value
           instead. Setting **mergetool.meld.hasOutput** to **true** tells Git to unconditionally use the
           **--output** option, and **false** avoids using **--output**.

       mergetool.meld.useAutoMerge
           When the **--auto-merge** is given, meld will merge all non-conflicting parts automatically,
           highlight the conflicting parts and wait for user decision. Setting
           **mergetool.meld.useAutoMerge** to **true** tells Git to unconditionally use the **--auto-merge**
           option with **meld**. Setting this value to **auto** makes git detect whether **--auto-merge** is
           supported and will only use **--auto-merge** when available. A value of **false** avoids using
           **--auto-merge** altogether, and is the default value.

       mergetool.hideResolved
           During a merge Git will automatically resolve as many conflicts as possible and write the
           _MERGED_ file containing conflict markers around any conflicts that it cannot resolve;
           _LOCAL_ and _REMOTE_ normally represent the versions of the file from before Git’s conflict
           resolution. This flag causes _LOCAL_ and _REMOTE_ to be overwriten so that only the
           unresolved conflicts are presented to the merge tool. Can be configured per-tool via the
           **mergetool..hideResolved** configuration variable. Defaults to **false**.

       mergetool.keepBackup
           After performing a merge, the original file with conflict markers can be saved as a file
           with a **.orig** extension. If this variable is set to **false** then this file is not preserved.
           Defaults to **true** (i.e. keep the backup files).

       mergetool.keepTemporaries
           When invoking a custom merge tool, Git uses a set of temporary files to pass to the tool.
           If the tool returns an error and this variable is set to **true**, then these temporary files
           will be preserved, otherwise they will be removed after the tool has exited. Defaults to
           **false**.

       mergetool.writeToTemp
           Git writes temporary _BASE_, _LOCAL_, and _REMOTE_ versions of conflicting files in the
           worktree by default. Git will attempt to use a temporary directory for these files when
           set **true**. Defaults to **false**.

       mergetool.prompt
           Prompt before each invocation of the merge resolution program.

       notes.mergeStrategy
           Which merge strategy to choose by default when resolving notes conflicts. Must be one of
           **manual**, **ours**, **theirs**, **union**, or **cat**___**sort**___**uniq**. Defaults to **manual**. See "NOTES MERGE
           STRATEGIES" section of [**git-notes**(1)](https://www.chedong.com/phpMan.php/man/git-notes/1/markdown) for more information on each strategy.

       notes..mergeStrategy
           Which merge strategy to choose when doing a notes merge into refs/notes/. This
           overrides the more general "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES"
           section in [**git-notes**(1)](https://www.chedong.com/phpMan.php/man/git-notes/1/markdown) for more information on the available strategies.

       notes.displayRef
           The (fully qualified) refname from which to show notes when showing commit messages. The
           value of this variable can be set to a glob, in which case notes from all matching refs
           will be shown. You may also specify this configuration variable several times. A warning
           will be issued for refs that do not exist, but a glob that does not match any refs is
           silently ignored.

           This setting can be overridden with the **GIT**___**NOTES**___**DISPLAY**___**REF** environment variable, which
           must be a colon separated list of refs or globs.

           The effective value of "core.notesRef" (possibly overridden by GIT_NOTES_REF) is also
           implicitly added to the list of refs to be displayed.

       notes.rewrite.
           When rewriting commits with  (currently **amend** or **rebase**) and this variable is
           set to **true**, Git automatically copies your notes from the original to the rewritten
           commit. Defaults to **true**, but see "notes.rewriteRef" below.

       notes.rewriteMode
           When copying notes during a rewrite (see the "notes.rewrite." option),
           determines what to do if the target commit already has a note. Must be one of **overwrite**,
           **concatenate**, **cat**___**sort**___**uniq**, or **ignore**. Defaults to **concatenate**.

           This setting can be overridden with the **GIT**___**NOTES**___**REWRITE**___**MODE** environment variable.

       notes.rewriteRef
           When copying notes during a rewrite, specifies the (fully qualified) ref whose notes
           should be copied. The ref may be a glob, in which case notes in all matching refs will be
           copied. You may also specify this configuration several times.

           Does not have a default value; you must configure this variable to enable note rewriting.
           Set it to **refs/notes/commits** to enable rewriting for the default commit notes.

           This setting can be overridden with the **GIT**___**NOTES**___**REWRITE**___**REF** environment variable, which
           must be a colon separated list of refs or globs.

       pack.window
           The size of the window used by [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) when no window size is given on the
           command line. Defaults to 10.

       pack.depth
           The maximum delta depth used by [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) when no maximum depth is given on the
           command line. Defaults to 50. Maximum value is 4095.

       pack.windowMemory
           The maximum size of memory that is consumed by each thread in [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) for
           pack window memory when no limit is given on the command line. The value can be suffixed
           with "k", "m", or "g". When left unconfigured (or set explicitly to 0), there will be no
           limit.

       pack.compression
           An integer -1..9, indicating the compression level for objects in a pack file. -1 is the
           zlib default. 0 means no compression, and 1..9 are various speed/size tradeoffs, 9 being
           slowest. If not set, defaults to core.compression. If that is not set, defaults to -1,
           the zlib default, which is "a default compromise between speed and compression (currently
           equivalent to level 6)."

           Note that changing the compression level will not automatically recompress all existing
           objects. You can force recompression by passing the -F option to [**git-repack**(1)](https://www.chedong.com/phpMan.php/man/git-repack/1/markdown).

       pack.allowPackReuse
           When true, and when reachability bitmaps are enabled, pack-objects will try to send parts
           of the bitmapped packfile verbatim. This can reduce memory and CPU usage to serve
           fetches, but might result in sending a slightly larger pack. Defaults to true.

       pack.island
           An extended regular expression configuring a set of delta islands. See "DELTA ISLANDS" in
           [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) for details.

       pack.islandCore
           Specify an island name which gets to have its objects be packed first. This creates a
           kind of pseudo-pack at the front of one pack, so that the objects from the specified
           island are hopefully faster to copy into any pack that should be served to a user
           requesting these objects. In practice this means that the island specified should likely
           correspond to what is the most commonly cloned in the repo. See also "DELTA ISLANDS" in
           [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown).

       pack.deltaCacheSize
           The maximum memory in bytes used for caching deltas in [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) before writing
           them out to a pack. This cache is used to speed up the writing object phase by not having
           to recompute the final delta result once the best match for all objects is found.
           Repacking large repositories on machines which are tight with memory might be badly
           impacted by this though, especially if this cache pushes the system into swapping. A
           value of 0 means no limit. The smallest size of 1 byte may be used to virtually disable
           this cache. Defaults to 256 MiB.

       pack.deltaCacheLimit
           The maximum size of a delta, that is cached in [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown). This cache is used to
           speed up the writing object phase by not having to recompute the final delta result once
           the best match for all objects is found. Defaults to 1000. Maximum value is 65535.

       pack.threads
           Specifies the number of threads to spawn when searching for best delta matches. This
           requires that [**git-pack-objects**(1)](https://www.chedong.com/phpMan.php/man/git-pack-objects/1/markdown) be compiled with pthreads otherwise this option is
           ignored with a warning. This is meant to reduce packing time on multiprocessor machines.
           The required amount of memory for the delta search window is however multiplied by the
           number of threads. Specifying 0 will cause Git to auto-detect the number of CPU’s and set
           the number of threads accordingly.

       pack.indexVersion
           Specify the default pack index version. Valid values are 1 for legacy pack index used by
           Git versions prior to 1.5.2, and 2 for the new pack index with capabilities for packs
           larger than 4 GB as well as proper protection against the repacking of corrupted packs.
           Version 2 is the default. Note that version 2 is enforced and this config option ignored
           whenever the corresponding pack is larger than 2 GB.

           If you have an old Git that does not understand the version 2 ***.idx** file, cloning or
           fetching over a non native protocol (e.g. "http") that will copy both ***.pack** file and
           corresponding ***.idx** file from the other side may give you a repository that cannot be
           accessed with your older version of Git. If the ***.pack** file is smaller than 2 GB,
           however, you can use [**git-index-pack**(1)](https://www.chedong.com/phpMan.php/man/git-index-pack/1/markdown) on the *.pack file to regenerate the ***.idx** file.

       pack.packSizeLimit
           The maximum size of a pack. This setting only affects packing to a file when repacking,
           i.e. the git:// protocol is unaffected. It can be overridden by the **--max-pack-size**
           option of [**git-repack**(1)](https://www.chedong.com/phpMan.php/man/git-repack/1/markdown). Reaching this limit results in the creation of multiple
           packfiles.

           Note that this option is rarely useful, and may result in a larger total on-disk size
           (because Git will not store deltas between packs), as well as worse runtime performance
           (object lookup within multiple packs is slower than a single pack, and optimizations like
           reachability bitmaps cannot cope with multiple packs).

           If you need to actively run Git using smaller packfiles (e.g., because your filesystem
           does not support large files), this option may help. But if your goal is to transmit a
           packfile over a medium that supports limited sizes (e.g., removable media that cannot
           store the whole repository), you are likely better off creating a single large packfile
           and splitting it using a generic multi-volume archive tool (e.g., Unix **split**).

           The minimum size allowed is limited to 1 MiB. The default is unlimited. Common unit
           suffixes of _k_, _m_, or _g_ are supported.

       pack.useBitmaps
           When true, git will use pack bitmaps (if available) when packing to stdout (e.g., during
           the server side of a fetch). Defaults to true. You should not generally need to turn this
           off unless you are debugging pack bitmaps.

       pack.useSparse
           When true, git will default to using the _--sparse_ option in _git_ _pack-objects_ when the
           _--revs_ option is present. This algorithm only walks trees that appear in paths that
           introduce new objects. This can have significant performance benefits when computing a
           pack to send a small change. However, it is possible that extra objects are added to the
           pack-file if the included commits contain certain types of direct renames. Default is
           **true**.

       pack.preferBitmapTips
           When selecting which commits will receive bitmaps, prefer a commit at the tip of any
           reference that is a suffix of any value of this configuration over any other commits in
           the "selection window".

           Note that setting this configuration to **refs/foo** does not mean that the commits at the
           tips of **refs/foo/bar** and **refs/foo/baz** will necessarily be selected. This is because
           commits are selected for bitmaps from within a series of windows of variable length.

           If a commit at the tip of any reference which is a suffix of any value of this
           configuration is seen in a window, it is immediately given preference over any other
           commit in that window.

       pack.writeBitmaps (deprecated)
           This is a deprecated synonym for **repack.writeBitmaps**.

       pack.writeBitmapHashCache
           When true, git will include a "hash cache" section in the bitmap index (if one is
           written). This cache can be used to feed git’s delta heuristics, potentially leading to
           better deltas between bitmapped and non-bitmapped objects (e.g., when serving a fetch
           between an older, bitmapped pack and objects that have been pushed since the last gc).
           The downside is that it consumes 4 bytes per object of disk space. Defaults to true.

           When writing a multi-pack reachability bitmap, no new namehashes are computed; instead,
           any namehashes stored in an existing bitmap are permuted into their appropriate location
           when writing a new bitmap.

       pack.writeReverseIndex
           When true, git will write a corresponding .rev file (see:
           **Documentation/technical/pack-format.txt**[3]) for each new packfile that it writes in all
           places except for [**git-fast-import**(1)](https://www.chedong.com/phpMan.php/man/git-fast-import/1/markdown) and in the bulk checkin mechanism. Defaults to
           false.

       pager.
           If the value is boolean, turns on or off pagination of the output of a particular Git
           subcommand when writing to a tty. Otherwise, turns on pagination for the subcommand using
           the pager specified by the value of **pager.**. If **--paginate** or **--no-pager** is specified
           on the command line, it takes precedence over this option. To disable pagination for all
           commands, set **core.pager** or **GIT**___**PAGER** to **cat**.

       pretty.
           Alias for a --pretty= format string, as specified in [**git-log**(1)](https://www.chedong.com/phpMan.php/man/git-log/1/markdown). Any aliases defined here
           can be used just as the built-in pretty formats could. For example, running **git** **config**
           **pretty.changelog** **"format:*** **%H** **%s"** would cause the invocation **git** **log** **--pretty=changelog**
           to be equivalent to running **git** **log** **"--pretty=format:*** **%H** **%s"**. Note that an alias with
           the same name as a built-in format will be silently ignored.

       protocol.allow
           If set, provide a user defined default policy for all protocols which don’t explicitly
           have a policy (**protocol..allow**). By default, if unset, known-safe protocols (http,
           https, git, ssh) have a default policy of **always**, known-dangerous protocols (ext) have a
           default policy of **never**, and all other protocols (including file) have a default policy
           of **user**. Supported policies:

           •   **always** - protocol is always able to be used.

           •   **never** - protocol is never able to be used.

           •   **user** - protocol is only able to be used when **GIT**___**PROTOCOL**___**FROM**___**USER** is either unset
               or has a value of 1. This policy should be used when you want a protocol to be
               directly usable by the user but don’t want it used by commands which execute
               clone/fetch/push commands without user input, e.g. recursive submodule
               initialization.

       protocol..allow
           Set a policy to be used by protocol **** with clone/fetch/push commands. See
           **protocol.allow** above for the available policies.

           The protocol names currently used by git are:

           •   **file**: any local file-based path (including **file://** URLs, or local paths)

           •   **git**: the anonymous git protocol over a direct TCP connection (or proxy, if
               configured)

           •   **ssh**: git over ssh (including **host:path** syntax, **ssh://**, etc).

           •   **http**: git over http, both "smart http" and "dumb http". Note that this does _not_
               include **https**; if you want to configure both, you must do so individually.

           •   any external helpers are named by their protocol (e.g., use **hg** to allow the
               **git-remote-hg** helper)

       protocol.version
           If set, clients will attempt to communicate with a server using the specified protocol
           version. If the server does not support it, communication falls back to version 0. If
           unset, the default is **2**. Supported versions:

           •   **0** - the original wire protocol.

           •   **1** - the original wire protocol with the addition of a version string in the initial
               response from the server.

           •   **2** - **wire** **protocol** **version** **2**[4].

       pull.ff
           By default, Git does not create an extra merge commit when merging a commit that is a
           descendant of the current commit. Instead, the tip of the current branch is
           fast-forwarded. When set to **false**, this variable tells Git to create an extra merge
           commit in such a case (equivalent to giving the **--no-ff** option from the command line).
           When set to **only**, only such fast-forward merges are allowed (equivalent to giving the
           **--ff-only** option from the command line). This setting overrides **merge.ff** when pulling.

       pull.rebase
           When true, rebase branches on top of the fetched branch, instead of merging the default
           branch from the default remote when "git pull" is run. See "branch..rebase" for
           setting this on a per-branch basis.

           When **merges** (or just _m_), pass the **--rebase-merges** option to _git_ _rebase_ so that the local
           merge commits are included in the rebase (see [**git-rebase**(1)](https://www.chedong.com/phpMan.php/man/git-rebase/1/markdown) for details).

           When the value is **interactive** (or just _i_), the rebase is run in interactive mode.

           **NOTE**: this is a possibly dangerous operation; do **not** use it unless you understand the
           implications (see [**git-rebase**(1)](https://www.chedong.com/phpMan.php/man/git-rebase/1/markdown) for details).

       pull.octopus
           The default merge strategy to use when pulling multiple branches at once.

       pull.twohead
           The default merge strategy to use when pulling a single branch.

       push.default
           Defines the action **git** **push** should take if no refspec is given (whether from the
           command-line, config, or elsewhere). Different values are well-suited for specific
           workflows; for instance, in a purely central workflow (i.e. the fetch source is equal to
           the push destination), **upstream** is probably what you want. Possible values are:

           •   **nothing** - do not push anything (error out) unless a refspec is given. This is
               primarily meant for people who want to avoid mistakes by always being explicit.

           •   **current** - push the current branch to update a branch with the same name on the
               receiving end. Works in both central and non-central workflows.

           •   **upstream** - push the current branch back to the branch whose changes are usually
               integrated into the current branch (which is called **@{upstream}**). This mode only
               makes sense if you are pushing to the same repository you would normally pull from
               (i.e. central workflow).

           •   **tracking** - This is a deprecated synonym for **upstream**.

           •   **simple** - pushes the current branch with the same name on the remote.

               If you are working on a centralized workflow (pushing to the same repository you pull
               from, which is typically **origin**), then you need to configure an upstream branch with
               the same name.

               This mode is the default since Git 2.0, and is the safest option suited for
               beginners.

           •   **matching** - push all branches having the same name on both ends. This makes the
               repository you are pushing to remember the set of branches that will be pushed out
               (e.g. if you always push _maint_ and _master_ there and no other branches, the repository
               you push to will have these two branches, and your local _maint_ and _master_ will be
               pushed there).

               To use this mode effectively, you have to make sure _all_ the branches you would push
               out are ready to be pushed out before running _git_ _push_, as the whole point of this
               mode is to allow you to push all of the branches in one go. If you usually finish
               work on only one branch and push out the result, while other branches are unfinished,
               this mode is not for you. Also this mode is not suitable for pushing into a shared
               central repository, as other people may add new branches there, or update the tip of
               existing branches outside your control.

               This used to be the default, but not since Git 2.0 (**simple** is the new default).

       push.followTags
           If set to true enable **--follow-tags** option by default. You may override this
           configuration at time of push by specifying **--no-follow-tags**.

       push.gpgSign
           May be set to a boolean value, or the string _if-asked_. A true value causes all pushes to
           be GPG signed, as if **--signed** is passed to [**git-push**(1)](https://www.chedong.com/phpMan.php/man/git-push/1/markdown). The string _if-asked_ causes pushes
           to be signed if the server supports it, as if **--signed=if-asked** is passed to _git_ _push_. A
           false value may override a value from a lower-priority config file. An explicit
           command-line flag always overrides this config option.

       push.pushOption
           When no **--push-option=