]>
Commit | Line | Data |
---|---|---|
e0d10e1c TP |
1 | git-config(1) |
2 | ============= | |
3 | ||
4 | NAME | |
5 | ---- | |
6 | git-config - Get and set repository or global options | |
7 | ||
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
11 | [verse] | |
fbad334d JH |
12 | 'git config' [<file-option>] [--type=<type>] [--comment=<message>] [--fixed-value] [--show-origin] [--show-scope] [-z|--null] <name> [<value> [<value-pattern>]] |
13 | 'git config' [<file-option>] [--type=<type>] [--comment=<message>] --add <name> <value> | |
14 | 'git config' [<file-option>] [--type=<type>] [--comment=<message>] [--fixed-value] --replace-all <name> <value> [<value-pattern>] | |
49cbad0e JNA |
15 | 'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get <name> [<value-pattern>] |
16 | 'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] --get-all <name> [<value-pattern>] | |
17 | 'git config' [<file-option>] [--type=<type>] [--show-origin] [--show-scope] [-z|--null] [--fixed-value] [--name-only] --get-regexp <name-regex> [<value-pattern>] | |
18 | 'git config' [<file-option>] [--type=<type>] [-z|--null] --get-urlmatch <name> <URL> | |
19 | 'git config' [<file-option>] [--fixed-value] --unset <name> [<value-pattern>] | |
20 | 'git config' [<file-option>] [--fixed-value] --unset-all <name> [<value-pattern>] | |
21 | 'git config' [<file-option>] --rename-section <old-name> <new-name> | |
22 | 'git config' [<file-option>] --remove-section <name> | |
145d59f4 | 23 | 'git config' [<file-option>] [--show-origin] [--show-scope] [-z|--null] [--name-only] -l | --list |
49cbad0e JNA |
24 | 'git config' [<file-option>] --get-color <name> [<default>] |
25 | 'git config' [<file-option>] --get-colorbool <name> [<stdout-is-tty>] | |
3bec8ff9 | 26 | 'git config' [<file-option>] -e | --edit |
e0d10e1c TP |
27 | |
28 | DESCRIPTION | |
29 | ----------- | |
30 | You can query/set/replace/unset options with this command. The name is | |
31 | actually the section and the key separated by a dot, and the value will be | |
32 | escaped. | |
33 | ||
bcf9626a | 34 | Multiple lines can be added to an option by using the `--add` option. |
e0d10e1c | 35 | If you want to update or unset an option which can occur on multiple |
c9026187 JH |
36 | lines, a `value-pattern` (which is an extended regular expression, |
37 | unless the `--fixed-value` option is given) needs to be given. Only the | |
38 | existing values that match the pattern are updated or unset. If | |
39 | you want to handle the lines that do *not* match the pattern, just | |
40 | prepend a single exclamation mark in front (see also <<EXAMPLES>>), | |
41 | but note that this only works when the `--fixed-value` option is not | |
42 | in use. | |
e0d10e1c | 43 | |
fb0dc3ba TB |
44 | The `--type=<type>` option instructs 'git config' to ensure that incoming and |
45 | outgoing values are canonicalize-able under the given <type>. If no | |
46 | `--type=<type>` is given, no canonicalization will be performed. Callers may | |
47 | unset an existing `--type` specifier with `--no-type`. | |
e0d10e1c | 48 | |
c598c5aa FA |
49 | When reading, the values are read from the system, global and |
50 | repository local configuration files by default, and options | |
58b284a2 NTND |
51 | `--system`, `--global`, `--local`, `--worktree` and |
52 | `--file <filename>` can be used to tell the command to read from only | |
53 | that location (see <<FILES>>). | |
c598c5aa FA |
54 | |
55 | When writing, the new value is written to the repository local | |
bcf9626a | 56 | configuration file by default, and options `--system`, `--global`, |
58b284a2 NTND |
57 | `--worktree`, `--file <filename>` can be used to tell the command to |
58 | write to that location (you can say `--local` but that is the | |
59 | default). | |
be52a41c | 60 | |
9409c7a5 JH |
61 | This command will fail with non-zero status upon error. Some exit |
62 | codes are: | |
e0d10e1c | 63 | |
376eb604 | 64 | - The section or key is invalid (ret=1), |
94c5b0e8 | 65 | - no section or name was provided (ret=2), |
376eb604 SB |
66 | - the config file is invalid (ret=3), |
67 | - the config file cannot be written (ret=4), | |
94c5b0e8 JK |
68 | - you try to unset an option which does not exist (ret=5), |
69 | - you try to unset/set an option for which multiple lines match (ret=5), or | |
70 | - you try to use an invalid regexp (ret=6). | |
e0d10e1c | 71 | |
7a397419 | 72 | On success, the command returns the exit code 0. |
e0d10e1c | 73 | |
ae578de9 PO |
74 | A list of all available configuration variables can be obtained using the |
75 | `git help --config` command. | |
76 | ||
73428385 | 77 | [[OPTIONS]] |
e0d10e1c TP |
78 | OPTIONS |
79 | ------- | |
80 | ||
81 | --replace-all:: | |
82 | Default behavior is to replace at most one line. This replaces | |
247e2f82 | 83 | all lines matching the key (and optionally the `value-pattern`). |
e0d10e1c TP |
84 | |
85 | --add:: | |
86 | Adds a new line to the option without altering any existing | |
247e2f82 | 87 | values. This is the same as providing '^$' as the `value-pattern` |
ac9f71cf | 88 | in `--replace-all`. |
e0d10e1c | 89 | |
fbad334d JH |
90 | --comment <message>:: |
91 | Append a comment at the end of new or modified lines. | |
31399a6b JH |
92 | |
93 | If _<message>_ begins with one or more whitespaces followed | |
94 | by "#", it is used as-is. If it begins with "#", a space is | |
95 | prepended before it is used. Otherwise, a string " # " (a | |
96 | space followed by a hash followed by a space) is prepended | |
97 | to it. And the resulting string is placed immediately after | |
98 | the value defined for the variable. The _<message>_ must | |
99 | not contain linefeed characters (no multi-line comments are | |
100 | permitted). | |
42d5c033 | 101 | |
e0d10e1c TP |
102 | --get:: |
103 | Get the value for a given key (optionally filtered by a regex | |
104 | matching the value). Returns error code 1 if the key was not | |
62e91efa | 105 | found and the last value if multiple key values were found. |
e0d10e1c TP |
106 | |
107 | --get-all:: | |
24990b2f | 108 | Like get, but returns all values for a multi-valued key. |
e0d10e1c TP |
109 | |
110 | --get-regexp:: | |
e0a4aae8 LP |
111 | Like --get-all, but interprets the name as a regular expression and |
112 | writes out the key names. Regular expression matching is currently | |
113 | case-sensitive and done against a canonicalized version of the key | |
114 | in which section and variable names are lowercased, but subsection | |
115 | names are not. | |
e0d10e1c | 116 | |
49cbad0e | 117 | --get-urlmatch <name> <URL>:: |
51e846e6 JNA |
118 | When given a two-part <name> as <section>.<key>, the value for |
119 | <section>.<URL>.<key> whose <URL> part matches the best to the | |
d4770964 | 120 | given URL is returned (if no such key exists, the value for |
51e846e6 JNA |
121 | <section>.<key> is used as a fallback). When given just the |
122 | <section> as name, do so for all the keys in the section and | |
27b30be6 | 123 | list them. Returns error code 1 if no value is found. |
d4770964 | 124 | |
e0d10e1c | 125 | --global:: |
5ff0c0e8 RR |
126 | For writing options: write to global `~/.gitconfig` file |
127 | rather than the repository `.git/config`, write to | |
128 | `$XDG_CONFIG_HOME/git/config` file if this file exists and the | |
129 | `~/.gitconfig` file doesn't. | |
17014090 | 130 | + |
5ff0c0e8 RR |
131 | For reading options: read only from global `~/.gitconfig` and from |
132 | `$XDG_CONFIG_HOME/git/config` rather than from all available files. | |
17014090 FL |
133 | + |
134 | See also <<FILES>>. | |
e0d10e1c | 135 | |
9bc20aa7 | 136 | --system:: |
5ff0c0e8 RR |
137 | For writing options: write to system-wide |
138 | `$(prefix)/etc/gitconfig` rather than the repository | |
139 | `.git/config`. | |
17014090 | 140 | + |
5ff0c0e8 | 141 | For reading options: read only from system-wide `$(prefix)/etc/gitconfig` |
17014090 FL |
142 | rather than from all available files. |
143 | + | |
144 | See also <<FILES>>. | |
9bc20aa7 | 145 | |
560d4b86 | 146 | --local:: |
5ff0c0e8 | 147 | For writing options: write to the repository `.git/config` file. |
8d75a1d1 | 148 | This is the default behavior. |
560d4b86 | 149 | + |
5ff0c0e8 | 150 | For reading options: read only from the repository `.git/config` rather than |
560d4b86 NK |
151 | from all available files. |
152 | + | |
153 | See also <<FILES>>. | |
154 | ||
58b284a2 | 155 | --worktree:: |
5c11c0d5 | 156 | Similar to `--local` except that `$GIT_DIR/config.worktree` is |
58b284a2 | 157 | read from or written to if `extensions.worktreeConfig` is |
5c11c0d5 DS |
158 | enabled. If not it's the same as `--local`. Note that `$GIT_DIR` |
159 | is equal to `$GIT_COMMON_DIR` for the main working tree, but is of | |
160 | the form `$GIT_DIR/worktrees/<id>/` for other working trees. See | |
161 | linkgit:git-worktree[1] to learn how to enable | |
162 | `extensions.worktreeConfig`. | |
58b284a2 | 163 | |
49cbad0e JNA |
164 | -f <config-file>:: |
165 | --file <config-file>:: | |
4bb9eb5f JK |
166 | For writing options: write to the specified file rather than the |
167 | repository `.git/config`. | |
168 | + | |
169 | For reading options: read only from the specified file rather than from all | |
170 | available files. | |
171 | + | |
172 | See also <<FILES>>. | |
67d454fe | 173 | |
49cbad0e | 174 | --blob <blob>:: |
bcf9626a | 175 | Similar to `--file` but use the given blob instead of a file. E.g. |
1bc88819 HV |
176 | you can use 'master:.gitmodules' to read values from the file |
177 | '.gitmodules' in the master branch. See "SPECIFYING REVISIONS" | |
178 | section in linkgit:gitrevisions[7] for a more complete list of | |
179 | ways to spell blob names. | |
180 | ||
118f8b24 PB |
181 | --remove-section:: |
182 | Remove the given section from the configuration file. | |
183 | ||
184 | --rename-section:: | |
185 | Rename the given section to a new name. | |
186 | ||
e0d10e1c TP |
187 | --unset:: |
188 | Remove the line matching the key from config file. | |
189 | ||
190 | --unset-all:: | |
9debca9a | 191 | Remove all lines matching the key from config file. |
e0d10e1c | 192 | |
3240240f SB |
193 | -l:: |
194 | --list:: | |
578625fa | 195 | List all variables set in config file, along with their values. |
e0d10e1c | 196 | |
fda43942 DS |
197 | --fixed-value:: |
198 | When used with the `value-pattern` argument, treat `value-pattern` as | |
199 | an exact string instead of a regular expression. This will restrict | |
200 | the name/value pairs that are matched to only those where the value | |
201 | is exactly equal to the `value-pattern`. | |
202 | ||
fb0dc3ba TB |
203 | --type <type>:: |
204 | 'git config' will ensure that any input or output is valid under the given | |
205 | type constraint(s), and will canonicalize outgoing values in `<type>`'s | |
206 | canonical form. | |
207 | + | |
208 | Valid `<type>`'s include: | |
209 | + | |
210 | - 'bool': canonicalize values as either "true" or "false". | |
211 | - 'int': canonicalize values as simple decimal numbers. An optional suffix of | |
212 | 'k', 'm', or 'g' will cause the value to be multiplied by 1024, 1048576, or | |
213 | 1073741824 upon input. | |
214 | - 'bool-or-int': canonicalize according to either 'bool' or 'int', as described | |
215 | above. | |
58be1143 | 216 | - 'path': canonicalize by expanding a leading `~` to the value of `$HOME` and |
fb0dc3ba TB |
217 | `~user` to the home directory for the specified user. This specifier has no |
218 | effect when setting the value (but you can use `git config section.variable | |
219 | ~/` from the command line to let your shell do the expansion.) | |
220 | - 'expiry-date': canonicalize by converting from a fixed or relative date-string | |
221 | to a timestamp. This specifier has no effect when setting the value. | |
63e2a0f8 TB |
222 | - 'color': When getting a value, canonicalize by converting to an ANSI color |
223 | escape sequence. When setting a value, a sanity-check is performed to ensure | |
224 | that the given value is canonicalize-able as an ANSI color, but it is written | |
225 | as-is. | |
fb0dc3ba | 226 | + |
e0d10e1c | 227 | |
fb0dc3ba | 228 | --bool:: |
e0d10e1c | 229 | --int:: |
d57f07eb | 230 | --bool-or-int:: |
1349484e | 231 | --path:: |
5f967424 | 232 | --expiry-date:: |
08caa95a MÅ |
233 | Historical options for selecting a type specifier. Prefer instead `--type` |
234 | (see above). | |
fb0dc3ba TB |
235 | |
236 | --no-type:: | |
237 | Un-sets the previously set type specifier (if one was previously set). This | |
238 | option requests that 'git config' not canonicalize the retrieved variable. | |
239 | `--no-type` has no effect without `--type=<type>` or `--<type>`. | |
5f967424 | 240 | |
3240240f SB |
241 | -z:: |
242 | --null:: | |
2275d502 | 243 | For all options that output values and/or keys, always |
a5d86f74 | 244 | end values with the null character (instead of a |
2275d502 FL |
245 | newline). Use newline instead as a delimiter between |
246 | key and value. This allows for secure parsing of the | |
247 | output without getting confused e.g. by values that | |
248 | contain line breaks. | |
249 | ||
578625fa SG |
250 | --name-only:: |
251 | Output only the names of config variables for `--list` or | |
252 | `--get-regexp`. | |
253 | ||
70bd879a LS |
254 | --show-origin:: |
255 | Augment the output of all queried config options with the | |
256 | origin type (file, standard input, blob, command line) and | |
257 | the actual origin (config file path, ref, or blob id if | |
258 | applicable). | |
259 | ||
145d59f4 MR |
260 | --show-scope:: |
261 | Similar to `--show-origin` in that it augments the output of | |
262 | all queried config options with the scope of that value | |
db7961e6 | 263 | (worktree, local, global, system, command). |
145d59f4 | 264 | |
49cbad0e | 265 | --get-colorbool <name> [<stdout-is-tty>]:: |
0f6f5a40 | 266 | |
49cbad0e JNA |
267 | Find the color setting for `<name>` (e.g. `color.diff`) and output |
268 | "true" or "false". `<stdout-is-tty>` should be either "true" or | |
0f6f5a40 | 269 | "false", and is taken into account when configuration says |
49cbad0e | 270 | "auto". If `<stdout-is-tty>` is missing, then checks the standard |
0f6f5a40 JH |
271 | output of the command itself, and exits with status 0 if color |
272 | is to be used, or exits with status 1 otherwise. | |
4d4f5ba3 MK |
273 | When the color setting for `name` is undefined, the command uses |
274 | `color.ui` as fallback. | |
0f6f5a40 | 275 | |
49cbad0e | 276 | --get-color <name> [<default>]:: |
9ce03522 JH |
277 | |
278 | Find the color configured for `name` (e.g. `color.diff.new`) and | |
279 | output it as the ANSI color escape sequence to the standard | |
280 | output. The optional `default` parameter is used instead, if | |
281 | there is no color configured for `name`. | |
63e2a0f8 | 282 | + |
cd8e7593 JK |
283 | `--type=color [--default=<default>]` is preferred over `--get-color` |
284 | (but note that `--get-color` will omit the trailing newline printed by | |
285 | `--type=color`). | |
e0d10e1c | 286 | |
3bec8ff9 FC |
287 | -e:: |
288 | --edit:: | |
289 | Opens an editor to modify the specified config file; either | |
7823a512 BL |
290 | `--system`, `--global`, `--local` (default), `--worktree`, or |
291 | `--file <config-file>`. | |
3bec8ff9 | 292 | |
0460ed2c | 293 | --[no-]includes:: |
9b25a0b5 | 294 | Respect `include.*` directives in config files when looking up |
753a2cda JK |
295 | values. Defaults to `off` when a specific file is given (e.g., |
296 | using `--file`, `--global`, etc) and `on` when searching all | |
297 | config files. | |
9b25a0b5 | 298 | |
eeaa24b9 TB |
299 | --default <value>:: |
300 | When using `--get`, and the requested variable is not found, behave as if | |
86f9ce7d | 301 | <value> were the value assigned to that variable. |
eeaa24b9 | 302 | |
32888b8f MÅ |
303 | CONFIGURATION |
304 | ------------- | |
305 | `pager.config` is only respected when listing configuration, i.e., when | |
306 | using `--list` or any of the `--get-*` which may return multiple results. | |
c0e9f5be | 307 | The default is to use a pager. |
32888b8f | 308 | |
17014090 FL |
309 | [[FILES]] |
310 | FILES | |
311 | ----- | |
312 | ||
5f5af373 GC |
313 | By default, 'git config' will read configuration options from multiple |
314 | files: | |
17014090 | 315 | |
7da9800f JK |
316 | $(prefix)/etc/gitconfig:: |
317 | System-wide configuration file. | |
17014090 | 318 | |
21cf3227 | 319 | $XDG_CONFIG_HOME/git/config:: |
7da9800f | 320 | ~/.gitconfig:: |
5f5af373 GC |
321 | User-specific configuration files. When the XDG_CONFIG_HOME environment |
322 | variable is not set or empty, $HOME/.config/ is used as | |
323 | $XDG_CONFIG_HOME. | |
324 | + | |
325 | These are also called "global" configuration files. If both files exist, both | |
326 | files are read in the order given above. | |
7da9800f JK |
327 | |
328 | $GIT_DIR/config:: | |
329 | Repository specific configuration file. | |
17014090 | 330 | |
58b284a2 NTND |
331 | $GIT_DIR/config.worktree:: |
332 | This is optional and is only searched when | |
333 | `extensions.worktreeConfig` is present in $GIT_DIR/config. | |
334 | ||
5f5af373 GC |
335 | You may also provide additional configuration parameters when running any |
336 | git command by using the `-c` option. See linkgit:git[1] for details. | |
337 | ||
338 | Options will be read from all of these files that are available. If the | |
339 | global or the system-wide configuration files are missing or unreadable they | |
340 | will be ignored. If the repository configuration file is missing or unreadable, | |
341 | 'git config' will exit with a non-zero error code. An error message is produced | |
342 | if the file is unreadable, but not if it is missing. | |
17014090 | 343 | |
7da9800f JK |
344 | The files are read in the order given above, with last value found taking |
345 | precedence over values read earlier. When multiple values are taken then all | |
346 | values of a key from all files will be used. | |
347 | ||
5f5af373 | 348 | By default, options are only written to the repository specific |
bcf9626a MM |
349 | configuration file. Note that this also affects options like `--replace-all` |
350 | and `--unset`. *'git config' will only ever change one file at a time*. | |
17014090 | 351 | |
5f5af373 GC |
352 | You can limit which configuration sources are read from or written to by |
353 | specifying the path of a file with the `--file` option, or by specifying a | |
354 | configuration scope with `--system`, `--global`, `--local`, or `--worktree`. | |
355 | For more, see <<OPTIONS>> above. | |
356 | ||
779ea930 | 357 | [[SCOPES]] |
5f5af373 GC |
358 | SCOPES |
359 | ------ | |
360 | ||
361 | Each configuration source falls within a configuration scope. The scopes | |
362 | are: | |
363 | ||
364 | system:: | |
365 | $(prefix)/etc/gitconfig | |
366 | ||
367 | global:: | |
368 | $XDG_CONFIG_HOME/git/config | |
369 | + | |
370 | ~/.gitconfig | |
371 | ||
372 | local:: | |
373 | $GIT_DIR/config | |
374 | ||
375 | worktree:: | |
376 | $GIT_DIR/config.worktree | |
377 | ||
378 | command:: | |
379 | GIT_CONFIG_{COUNT,KEY,VALUE} environment variables (see <<ENVIRONMENT>> | |
380 | below) | |
381 | + | |
382 | the `-c` option | |
383 | ||
384 | With the exception of 'command', each scope corresponds to a command line | |
385 | option: `--system`, `--global`, `--local`, `--worktree`. | |
386 | ||
387 | When reading options, specifying a scope will only read options from the | |
388 | files within that scope. When writing options, specifying a scope will write | |
389 | to the files within that scope (instead of the repository specific | |
390 | configuration file). See <<OPTIONS>> above for a complete description. | |
17014090 | 391 | |
5f5af373 GC |
392 | Most configuration options are respected regardless of the scope it is |
393 | defined in, but some options are only respected in certain scopes. See the | |
394 | respective option's documentation for the full details. | |
17014090 | 395 | |
779ea930 GC |
396 | Protected configuration |
397 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
398 | ||
399 | Protected configuration refers to the 'system', 'global', and 'command' scopes. | |
400 | For security reasons, certain options are only respected when they are | |
401 | specified in protected configuration, and ignored otherwise. | |
402 | ||
403 | Git treats these scopes as if they are controlled by the user or a trusted | |
404 | administrator. This is because an attacker who controls these scopes can do | |
405 | substantial harm without using Git, so it is assumed that the user's environment | |
406 | protects these scopes against attackers. | |
407 | ||
5f5af373 | 408 | [[ENVIRONMENT]] |
e0d10e1c TP |
409 | ENVIRONMENT |
410 | ----------- | |
411 | ||
4179b489 PS |
412 | GIT_CONFIG_GLOBAL:: |
413 | GIT_CONFIG_SYSTEM:: | |
414 | Take the configuration from the given files instead from global or | |
415 | system-level configuration. See linkgit:git[1] for details. | |
416 | ||
e8ef401c JN |
417 | GIT_CONFIG_NOSYSTEM:: |
418 | Whether to skip reading settings from the system-wide | |
419 | $(prefix)/etc/gitconfig file. See linkgit:git[1] for details. | |
420 | ||
17014090 | 421 | See also <<FILES>>. |
e0d10e1c | 422 | |
d8d77153 PS |
423 | GIT_CONFIG_COUNT:: |
424 | GIT_CONFIG_KEY_<n>:: | |
425 | GIT_CONFIG_VALUE_<n>:: | |
426 | If GIT_CONFIG_COUNT is set to a positive number, all environment pairs | |
427 | GIT_CONFIG_KEY_<n> and GIT_CONFIG_VALUE_<n> up to that number will be | |
428 | added to the process's runtime configuration. The config pairs are | |
429 | zero-indexed. Any missing key or value is treated as an error. An empty | |
430 | GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0, namely no | |
431 | pairs are processed. These environment variables will override values | |
432 | in configuration files, but will be overridden by any explicit options | |
433 | passed via `git -c`. | |
434 | + | |
435 | This is useful for cases where you want to spawn multiple git commands | |
436 | with a common configuration but cannot depend on a configuration file, | |
437 | for example when writing scripts. | |
438 | ||
b3b18626 JK |
439 | GIT_CONFIG:: |
440 | If no `--file` option is provided to `git config`, use the file | |
441 | given by `GIT_CONFIG` as if it were provided via `--file`. This | |
442 | variable has no effect on other Git commands, and is mostly for | |
443 | historical compatibility; there is generally no reason to use it | |
444 | instead of the `--file` option. | |
90a36e58 FL |
445 | |
446 | [[EXAMPLES]] | |
447 | EXAMPLES | |
448 | -------- | |
e0d10e1c TP |
449 | |
450 | Given a .git/config like this: | |
451 | ||
1925fe0c MÅ |
452 | ------------ |
453 | # | |
454 | # This is the config file, and | |
455 | # a '#' or ';' character indicates | |
456 | # a comment | |
457 | # | |
458 | ||
459 | ; core variables | |
460 | [core] | |
461 | ; Don't trust file modes | |
462 | filemode = false | |
463 | ||
464 | ; Our diff algorithm | |
465 | [diff] | |
466 | external = /usr/local/bin/diff-wrapper | |
467 | renames = true | |
468 | ||
469 | ; Proxy settings | |
470 | [core] | |
471 | gitproxy=proxy-command for kernel.org | |
472 | gitproxy=default-proxy ; for all the rest | |
473 | ||
474 | ; HTTP | |
475 | [http] | |
476 | sslVerify | |
477 | [http "https://weak.example.com"] | |
478 | sslVerify = false | |
479 | cookieFile = /tmp/cookie.txt | |
480 | ------------ | |
d4770964 | 481 | |
e0d10e1c TP |
482 | you can set the filemode to true with |
483 | ||
484 | ------------ | |
485 | % git config core.filemode true | |
486 | ------------ | |
487 | ||
488 | The hypothetical proxy command entries actually have a postfix to discern | |
489 | what URL they apply to. Here is how to change the entry for kernel.org | |
490 | to "ssh". | |
491 | ||
492 | ------------ | |
493 | % git config core.gitproxy '"ssh" for kernel.org' 'for kernel.org$' | |
494 | ------------ | |
495 | ||
496 | This makes sure that only the key/value pair for kernel.org is replaced. | |
497 | ||
498 | To delete the entry for renames, do | |
499 | ||
500 | ------------ | |
501 | % git config --unset diff.renames | |
502 | ------------ | |
503 | ||
504 | If you want to delete an entry for a multivar (like core.gitproxy above), | |
505 | you have to provide a regex matching the value of exactly one line. | |
506 | ||
507 | To query the value for a given key, do | |
508 | ||
509 | ------------ | |
510 | % git config --get core.filemode | |
511 | ------------ | |
512 | ||
513 | or | |
514 | ||
515 | ------------ | |
516 | % git config core.filemode | |
517 | ------------ | |
518 | ||
519 | or, to query a multivar: | |
520 | ||
521 | ------------ | |
522 | % git config --get core.gitproxy "for kernel.org$" | |
523 | ------------ | |
524 | ||
525 | If you want to know all the values for a multivar, do: | |
526 | ||
527 | ------------ | |
528 | % git config --get-all core.gitproxy | |
529 | ------------ | |
530 | ||
544ddb04 | 531 | If you like to live dangerously, you can replace *all* core.gitproxy by a |
e0d10e1c TP |
532 | new one with |
533 | ||
534 | ------------ | |
535 | % git config --replace-all core.gitproxy ssh | |
536 | ------------ | |
537 | ||
538 | However, if you really only want to replace the line for the default proxy, | |
539 | i.e. the one without a "for ..." postfix, do something like this: | |
540 | ||
541 | ------------ | |
542 | % git config core.gitproxy ssh '! for ' | |
543 | ------------ | |
544 | ||
545 | To actually match only values with an exclamation mark, you have to | |
546 | ||
547 | ------------ | |
548 | % git config section.key value '[!]' | |
549 | ------------ | |
550 | ||
551 | To add a new proxy, without altering any of the existing ones, use | |
552 | ||
553 | ------------ | |
d0714cc8 | 554 | % git config --add core.gitproxy '"proxy-command" for example.com' |
e0d10e1c TP |
555 | ------------ |
556 | ||
9ce03522 JH |
557 | An example to use customized color from the configuration in your |
558 | script: | |
559 | ||
560 | ------------ | |
561 | #!/bin/sh | |
562 | WS=$(git config --get-color color.diff.whitespace "blue reverse") | |
563 | RESET=$(git config --get-color "" "reset") | |
564 | echo "${WS}your whitespace color or blue reverse${RESET}" | |
565 | ------------ | |
e0d10e1c | 566 | |
d4770964 JH |
567 | For URLs in `https://weak.example.com`, `http.sslVerify` is set to |
568 | false, while it is set to `true` for all others: | |
569 | ||
570 | ------------ | |
ed3bb3df | 571 | % git config --type=bool --get-urlmatch http.sslverify https://good.example.com |
d4770964 | 572 | true |
ed3bb3df | 573 | % git config --type=bool --get-urlmatch http.sslverify https://weak.example.com |
d4770964 JH |
574 | false |
575 | % git config --get-urlmatch http https://weak.example.com | |
da0005b8 | 576 | http.cookieFile /tmp/cookie.txt |
d4770964 JH |
577 | http.sslverify false |
578 | ------------ | |
579 | ||
e0d10e1c TP |
580 | include::config.txt[] |
581 | ||
bff7df7a SB |
582 | BUGS |
583 | ---- | |
584 | When using the deprecated `[section.subsection]` syntax, changing a value | |
585 | will result in adding a multi-line key instead of a change, if the subsection | |
586 | is given with at least one uppercase character. For example when the config | |
587 | looks like | |
588 | ||
589 | -------- | |
590 | [section.subsection] | |
591 | key = value1 | |
592 | -------- | |
593 | ||
594 | and running `git config section.Subsection.key value2` will result in | |
595 | ||
596 | -------- | |
597 | [section.subsection] | |
598 | key = value1 | |
599 | key = value2 | |
600 | -------- | |
601 | ||
602 | ||
e0d10e1c TP |
603 | GIT |
604 | --- | |
9e1f0a85 | 605 | Part of the linkgit:git[1] suite |