6 git-config - Get and set repository or global options
12 'git config' [<file-option>] [type] [-z|--null] name [value [value_regex]]
13 'git config' [<file-option>] [type] --add name value
14 'git config' [<file-option>] [type] --replace-all name value [value_regex]
15 'git config' [<file-option>] [type] [-z|--null] --get name [value_regex]
16 'git config' [<file-option>] [type] [-z|--null] --get-all name [value_regex]
17 'git config' [<file-option>] [type] [-z|--null] --get-regexp name_regex [value_regex]
18 'git config' [<file-option>] --unset name [value_regex]
19 'git config' [<file-option>] --unset-all name [value_regex]
20 'git config' [<file-option>] --rename-section old_name new_name
21 'git config' [<file-option>] --remove-section name
22 'git config' [<file-option>] [-z|--null] -l | --list
23 'git config' [<file-option>] --get-color name [default]
24 'git config' [<file-option>] --get-colorbool name [stdout-is-tty]
25 'git config' [<file-option>] -e | --edit
29 You can query/set/replace/unset options with this command. The name is
30 actually the section and the key separated by a dot, and the value will be
33 Multiple lines can be added to an option by using the '--add' option.
34 If you want to update or unset an option which can occur on multiple
35 lines, a POSIX regexp `value_regex` needs to be given. Only the
36 existing values that match the regexp are updated or unset. If
37 you want to handle the lines that do *not* match the regex, just
38 prepend a single exclamation mark in front (see also <<EXAMPLES>>).
40 The type specifier can be either '--int' or '--bool', to make
41 'git config' ensure that the variable(s) are of the given type and
42 convert the value to the canonical form (simple decimal number for int,
43 a "true" or "false" string for bool), or '--path', which does some
44 path expansion (see '--path' below). If no type specifier is passed, no
45 checks or transformations are performed on the value.
47 When reading, the values are read from the system, global and
48 repository local configuration files by default, and options
49 '--system', '--global', '--local' and '--file <filename>' can be
50 used to tell the command to read from only that location (see <<FILES>>).
52 When writing, the new value is written to the repository local
53 configuration file by default, and options '--system', '--global',
54 '--file <filename>' can be used to tell the command to write to
55 that location (you can say '--local' but that is the default).
57 This command will fail with non-zero status upon error. Some exit
60 . The config file is invalid (ret=3),
61 . can not write to the config file (ret=4),
62 . no section or name was provided (ret=2),
63 . the section or key is invalid (ret=1),
64 . you try to unset an option which does not exist (ret=5),
65 . you try to unset/set an option for which multiple lines match (ret=5), or
66 . you try to use an invalid regexp (ret=6).
68 On success, the command returns the exit code 0.
74 Default behavior is to replace at most one line. This replaces
75 all lines matching the key (and optionally the value_regex).
78 Adds a new line to the option without altering any existing
79 values. This is the same as providing '^$' as the value_regex
83 Get the value for a given key (optionally filtered by a regex
84 matching the value). Returns error code 1 if the key was not
85 found and the last value if multiple key values were found.
88 Like get, but does not fail if the number of values for the key
92 Like --get-all, but interprets the name as a regular expression and
93 writes out the key names. Regular expression matching is currently
94 case-sensitive and done against a canonicalized version of the key
95 in which section and variable names are lowercased, but subsection
99 For writing options: write to global ~/.gitconfig file rather than
100 the repository .git/config, write to $XDG_CONFIG_HOME/git/config file
101 if this file exists and the ~/.gitconfig file doesn't.
103 For reading options: read only from global ~/.gitconfig and from
104 $XDG_CONFIG_HOME/git/config rather than from all available files.
109 For writing options: write to system-wide $(prefix)/etc/gitconfig
110 rather than the repository .git/config.
112 For reading options: read only from system-wide $(prefix)/etc/gitconfig
113 rather than from all available files.
118 For writing options: write to the repository .git/config file.
119 This is the default behavior.
121 For reading options: read only from the repository .git/config rather than
122 from all available files.
128 Use the given config file instead of the one specified by GIT_CONFIG.
131 Similar to '--file' but use the given blob instead of a file. E.g.
132 you can use 'master:.gitmodules' to read values from the file
133 '.gitmodules' in the master branch. See "SPECIFYING REVISIONS"
134 section in linkgit:gitrevisions[7] for a more complete list of
135 ways to spell blob names.
138 Remove the given section from the configuration file.
141 Rename the given section to a new name.
144 Remove the line matching the key from config file.
147 Remove all lines matching the key from config file.
151 List all variables set in config file.
154 'git config' will ensure that the output is "true" or "false"
157 'git config' will ensure that the output is a simple
158 decimal number. An optional value suffix of 'k', 'm', or 'g'
159 in the config file will cause the value to be multiplied
160 by 1024, 1048576, or 1073741824 prior to output.
163 'git config' will ensure that the output matches the format of
164 either --bool or --int, as described above.
167 'git-config' will expand leading '{tilde}' to the value of
168 '$HOME', and '{tilde}user' to the home directory for the
169 specified user. This option has no effect when setting the
170 value (but you can use 'git config bla {tilde}/' from the
171 command line to let your shell do the expansion).
175 For all options that output values and/or keys, always
176 end values with the null character (instead of a
177 newline). Use newline instead as a delimiter between
178 key and value. This allows for secure parsing of the
179 output without getting confused e.g. by values that
182 --get-colorbool name [stdout-is-tty]::
184 Find the color setting for `name` (e.g. `color.diff`) and output
185 "true" or "false". `stdout-is-tty` should be either "true" or
186 "false", and is taken into account when configuration says
187 "auto". If `stdout-is-tty` is missing, then checks the standard
188 output of the command itself, and exits with status 0 if color
189 is to be used, or exits with status 1 otherwise.
190 When the color setting for `name` is undefined, the command uses
191 `color.ui` as fallback.
193 --get-color name [default]::
195 Find the color configured for `name` (e.g. `color.diff.new`) and
196 output it as the ANSI color escape sequence to the standard
197 output. The optional `default` parameter is used instead, if
198 there is no color configured for `name`.
202 Opens an editor to modify the specified config file; either
203 '--system', '--global', or repository (default).
206 Respect `include.*` directives in config files when looking up
207 values. Defaults to on.
213 If not set explicitly with '--file', there are four files where
214 'git config' will search for configuration options:
216 $(prefix)/etc/gitconfig::
217 System-wide configuration file.
219 $XDG_CONFIG_HOME/git/config::
220 Second user-specific configuration file. If $XDG_CONFIG_HOME is not set
221 or empty, $HOME/.config/git/config will be used. Any single-valued
222 variable set in this file will be overwritten by whatever is in
223 ~/.gitconfig. It is a good idea not to create this file if
224 you sometimes use older versions of Git, as support for this
225 file was added fairly recently.
228 User-specific configuration file. Also called "global"
232 Repository specific configuration file.
234 If no further options are given, all reading options will read all of these
235 files that are available. If the global or the system-wide configuration
236 file are not available they will be ignored. If the repository configuration
237 file is not available or readable, 'git config' will exit with a non-zero
238 error code. However, in neither case will an error message be issued.
240 The files are read in the order given above, with last value found taking
241 precedence over values read earlier. When multiple values are taken then all
242 values of a key from all files will be used.
244 All writing options will per default write to the repository specific
245 configuration file. Note that this also affects options like '--replace-all'
246 and '--unset'. *'git config' will only ever change one file at a time*.
248 You can override these rules either by command line options or by environment
249 variables. The '--global' and the '--system' options will limit the file used
250 to the global or system-wide file respectively. The GIT_CONFIG environment
251 variable has a similar effect, but you can specify any filename you want.
258 Take the configuration from the given file instead of .git/config.
259 Using the "--global" option forces this to ~/.gitconfig. Using the
260 "--system" option forces this to $(prefix)/etc/gitconfig.
262 GIT_CONFIG_NOSYSTEM::
263 Whether to skip reading settings from the system-wide
264 $(prefix)/etc/gitconfig file. See linkgit:git[1] for details.
273 Given a .git/config like this:
276 # This is the config file, and
277 # a '#' or ';' character indicates
283 ; Don't trust file modes
288 external = /usr/local/bin/diff-wrapper
293 gitproxy=proxy-command for kernel.org
294 gitproxy=default-proxy ; for all the rest
296 you can set the filemode to true with
299 % git config core.filemode true
302 The hypothetical proxy command entries actually have a postfix to discern
303 what URL they apply to. Here is how to change the entry for kernel.org
307 % git config core.gitproxy '"ssh" for kernel.org' 'for kernel.org$'
310 This makes sure that only the key/value pair for kernel.org is replaced.
312 To delete the entry for renames, do
315 % git config --unset diff.renames
318 If you want to delete an entry for a multivar (like core.gitproxy above),
319 you have to provide a regex matching the value of exactly one line.
321 To query the value for a given key, do
324 % git config --get core.filemode
330 % git config core.filemode
333 or, to query a multivar:
336 % git config --get core.gitproxy "for kernel.org$"
339 If you want to know all the values for a multivar, do:
342 % git config --get-all core.gitproxy
345 If you like to live dangerously, you can replace *all* core.gitproxy by a
349 % git config --replace-all core.gitproxy ssh
352 However, if you really only want to replace the line for the default proxy,
353 i.e. the one without a "for ..." postfix, do something like this:
356 % git config core.gitproxy ssh '! for '
359 To actually match only values with an exclamation mark, you have to
362 % git config section.key value '[!]'
365 To add a new proxy, without altering any of the existing ones, use
368 % git config --add core.gitproxy '"proxy-command" for example.com'
371 An example to use customized color from the configuration in your
376 WS=$(git config --get-color color.diff.whitespace "blue reverse")
377 RESET=$(git config --get-color "" "reset")
378 echo "${WS}your whitespace color or blue reverse${RESET}"
381 include::config.txt[]
385 Part of the linkgit:git[1] suite