]>
Commit | Line | Data |
---|---|---|
1ab661dd PB |
1 | CONFIGURATION FILE |
2 | ------------------ | |
3 | ||
2de9b711 TA |
4 | The Git configuration file contains a number of variables that affect |
5 | the Git commands' behavior. The `.git/config` file in each repository | |
66e35fcb SB |
6 | is used to store the configuration for that repository, and |
7 | `$HOME/.gitconfig` is used to store a per-user configuration as | |
773002a7 | 8 | fallback values for the `.git/config` file. The file `/etc/gitconfig` |
66e35fcb | 9 | can be used to store a system-wide default configuration. |
5ea5621f | 10 | |
2de9b711 | 11 | The configuration variables are used by both the Git plumbing |
b7ee2266 SB |
12 | and the porcelains. The variables are divided into sections, wherein |
13 | the fully qualified variable name of the variable itself is the last | |
1ab661dd | 14 | dot-separated segment and the section name is everything before the last |
e0a4aae8 LP |
15 | dot. The variable names are case-insensitive, allow only alphanumeric |
16 | characters and `-`, and must start with an alphabetic character. Some | |
a5285b6c JH |
17 | variables may appear multiple times; we say then that the variable is |
18 | multivalued. | |
1ab661dd | 19 | |
e136f33b JN |
20 | Syntax |
21 | ~~~~~~ | |
22 | ||
1ab661dd | 23 | The syntax is fairly flexible and permissive; whitespaces are mostly |
e136f33b JN |
24 | ignored. The '#' and ';' characters begin comments to the end of line, |
25 | blank lines are ignored. | |
26 | ||
27 | The file consists of sections and variables. A section begins with | |
28 | the name of the section in square brackets and continues until the next | |
05c3e5c7 | 29 | section begins. Section names are case-insensitive. Only alphanumeric |
dcb11263 | 30 | characters, `-` and `.` are allowed in section names. Each variable |
773002a7 SB |
31 | must belong to some section, which means that there must be a section |
32 | header before the first setting of a variable. | |
e136f33b JN |
33 | |
34 | Sections can be further divided into subsections. To begin a subsection | |
35 | put its name in double quotes, separated by space from the section name, | |
773002a7 | 36 | in the section header, like in the example below: |
e136f33b JN |
37 | |
38 | -------- | |
39 | [section "subsection"] | |
40 | ||
41 | -------- | |
42 | ||
b7ee2266 | 43 | Subsection names are case sensitive and can contain any characters except |
1feb0617 DB |
44 | newline and the null byte. Doublequote `"` and backslash can be included |
45 | by escaping them as `\"` and `\\`, respectively. Backslashes preceding | |
46 | other characters are dropped when reading; for example, `\t` is read as | |
47 | `t` and `\0` is read as `0` Section headers cannot span multiple lines. | |
48 | Variables may belong directly to a section or to a given subsection. You | |
49 | can have `[section]` if you have `[section "subsection"]`, but you don't | |
50 | need to. | |
e136f33b | 51 | |
f7376329 CMN |
52 | There is also a deprecated `[section.subsection]` syntax. With this |
53 | syntax, the subsection name is converted to lower-case and is also | |
54 | compared case sensitively. These subsection names follow the same | |
55 | restrictions as section names. | |
e136f33b | 56 | |
2ceb639f NS |
57 | All the other lines (and the remainder of the line after the section |
58 | header) are recognized as setting variables, in the form | |
1c448b3b JH |
59 | 'name = value' (or just 'name', which is a short-hand to say that |
60 | the variable is the boolean "true"). | |
e0a4aae8 | 61 | The variable names are case-insensitive, allow only alphanumeric characters |
a5285b6c | 62 | and `-`, and must start with an alphabetic character. |
e136f33b | 63 | |
ff5507ed JH |
64 | A line that defines a value can be continued to the next line by |
65 | ending it with a `\`; the backquote and the end-of-line are | |
66 | stripped. Leading whitespaces after 'name =', the remainder of the | |
67 | line after the first comment character '#' or ';', and trailing | |
68 | whitespaces of the line are discarded unless they are enclosed in | |
69 | double quotes. Internal whitespaces within the value are retained | |
70 | verbatim. | |
e136f33b | 71 | |
ff5507ed JH |
72 | Inside double quotes, double quote `"` and backslash `\` characters |
73 | must be escaped: use `\"` for `"` and `\\` for `\`. | |
e136f33b | 74 | |
dcb11263 CJ |
75 | The following escape sequences (beside `\"` and `\\`) are recognized: |
76 | `\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) | |
a58088ab JL |
77 | and `\b` for backspace (BS). Other char escape sequences (including octal |
78 | escape sequences) are invalid. | |
e136f33b | 79 | |
1ab661dd | 80 | |
9b25a0b5 JK |
81 | Includes |
82 | ~~~~~~~~ | |
83 | ||
9d71d94d JK |
84 | The `include` and `includeIf` sections allow you to include config |
85 | directives from another source. These sections behave identically to | |
86 | each other with the exception that `includeIf` sections may be ignored | |
87 | if their condition does not evaluate to true; see "Conditional includes" | |
88 | below. | |
89 | ||
df0233be | 90 | You can include a config file from another by setting the special |
9d71d94d JK |
91 | `include.path` (or `includeIf.*.path`) variable to the name of the file |
92 | to be included. The variable takes a pathname as its value, and is | |
93 | subject to tilde expansion. These variables can be given multiple times. | |
dca83abd | 94 | |
a076df28 JK |
95 | The contents of the included file are inserted immediately, as if they |
96 | had been found at the location of the include directive. If the value of the | |
9d71d94d | 97 | variable is a relative path, the path is considered to |
1050e987 NTND |
98 | be relative to the configuration file in which the include directive |
99 | was found. See below for examples. | |
dca83abd | 100 | |
3efd0bed NTND |
101 | Conditional includes |
102 | ~~~~~~~~~~~~~~~~~~~~ | |
103 | ||
104 | You can include a config file from another conditionally by setting a | |
105 | `includeIf.<condition>.path` variable to the name of the file to be | |
9d71d94d | 106 | included. |
3efd0bed NTND |
107 | |
108 | The condition starts with a keyword followed by a colon and some data | |
109 | whose format and meaning depends on the keyword. Supported keywords | |
110 | are: | |
111 | ||
112 | `gitdir`:: | |
113 | ||
114 | The data that follows the keyword `gitdir:` is used as a glob | |
115 | pattern. If the location of the .git directory matches the | |
116 | pattern, the include condition is met. | |
117 | + | |
118 | The .git location may be auto-discovered, or come from `$GIT_DIR` | |
119 | environment variable. If the repository is auto discovered via a .git | |
120 | file (e.g. from submodules, or a linked worktree), the .git location | |
121 | would be the final location where the .git directory is, not where the | |
122 | .git file is. | |
123 | + | |
124 | The pattern can contain standard globbing wildcards and two additional | |
125 | ones, `**/` and `/**`, that can match multiple path components. Please | |
126 | refer to linkgit:gitignore[5] for details. For convenience: | |
127 | ||
128 | * If the pattern starts with `~/`, `~` will be substituted with the | |
129 | content of the environment variable `HOME`. | |
130 | ||
131 | * If the pattern starts with `./`, it is replaced with the directory | |
132 | containing the current config file. | |
133 | ||
134 | * If the pattern does not start with either `~/`, `./` or `/`, `**/` | |
135 | will be automatically prepended. For example, the pattern `foo/bar` | |
136 | becomes `**/foo/bar` and would match `/any/path/to/foo/bar`. | |
137 | ||
138 | * If the pattern ends with `/`, `**` will be automatically added. For | |
139 | example, the pattern `foo/` becomes `foo/**`. In other words, it | |
140 | matches "foo" and everything inside, recursively. | |
141 | ||
142 | `gitdir/i`:: | |
143 | This is the same as `gitdir` except that matching is done | |
144 | case-insensitively (e.g. on case-insensitive file sytems) | |
145 | ||
146 | A few more notes on matching via `gitdir` and `gitdir/i`: | |
147 | ||
148 | * Symlinks in `$GIT_DIR` are not resolved before matching. | |
149 | ||
0624c63c ÆAB |
150 | * Both the symlink & realpath versions of paths will be matched |
151 | outside of `$GIT_DIR`. E.g. if ~/git is a symlink to | |
152 | /mnt/storage/git, both `gitdir:~/git` and `gitdir:/mnt/storage/git` | |
153 | will match. | |
154 | + | |
155 | This was not the case in the initial release of this feature in | |
156 | v2.13.0, which only matched the realpath version. Configuration that | |
157 | wants to be compatible with the initial release of this feature needs | |
158 | to either specify only the realpath version, or both versions. | |
159 | ||
3efd0bed NTND |
160 | * Note that "../" is not special and will match literally, which is |
161 | unlikely what you want. | |
9b25a0b5 | 162 | |
1ab661dd PB |
163 | Example |
164 | ~~~~~~~ | |
165 | ||
166 | # Core variables | |
167 | [core] | |
168 | ; Don't trust file modes | |
169 | filemode = false | |
170 | ||
171 | # Our diff algorithm | |
172 | [diff] | |
6bb9e51b | 173 | external = /usr/local/bin/diff-wrapper |
1ab661dd PB |
174 | renames = true |
175 | ||
910c00c8 AK |
176 | [branch "devel"] |
177 | remote = origin | |
178 | merge = refs/heads/devel | |
179 | ||
e136f33b JN |
180 | # Proxy settings |
181 | [core] | |
29093c28 | 182 | gitProxy="ssh" for "kernel.org" |
e136f33b | 183 | gitProxy=default-proxy ; for the rest |
910c00c8 | 184 | |
9b25a0b5 JK |
185 | [include] |
186 | path = /path/to/foo.inc ; include by absolute path | |
ce933ebd JK |
187 | path = foo.inc ; find "foo.inc" relative to the current file |
188 | path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory | |
9b25a0b5 | 189 | |
3efd0bed NTND |
190 | ; include if $GIT_DIR is /path/to/foo/.git |
191 | [includeIf "gitdir:/path/to/foo/.git"] | |
192 | path = /path/to/foo.inc | |
193 | ||
194 | ; include for all repositories inside /path/to/group | |
195 | [includeIf "gitdir:/path/to/group/"] | |
196 | path = /path/to/foo.inc | |
197 | ||
198 | ; include for all repositories inside $HOME/to/group | |
199 | [includeIf "gitdir:~/to/group/"] | |
200 | path = /path/to/foo.inc | |
5f7b91ba | 201 | |
994cd6c7 JK |
202 | ; relative paths are always relative to the including |
203 | ; file (if the condition is true); their location is not | |
204 | ; affected by the condition | |
205 | [includeIf "gitdir:/path/to/group/"] | |
206 | path = foo.inc | |
207 | ||
5f7b91ba JH |
208 | Values |
209 | ~~~~~~ | |
210 | ||
211 | Values of many variables are treated as a simple string, but there | |
212 | are variables that take values of specific types and there are rules | |
213 | as to how to spell them. | |
214 | ||
215 | boolean:: | |
216 | ||
217 | When a variable is said to take a boolean value, many | |
218 | synonyms are accepted for 'true' and 'false'; these are all | |
219 | case-insensitive. | |
220 | ||
7f0a02be AH |
221 | true;; Boolean true literals are `yes`, `on`, `true`, |
222 | and `1`. Also, a variable defined without `= <value>` | |
5f7b91ba JH |
223 | is taken as true. |
224 | ||
7f0a02be AH |
225 | false;; Boolean false literals are `no`, `off`, `false`, |
226 | `0` and the empty string. | |
5f7b91ba | 227 | + |
ed3bb3df | 228 | When converting a value to its canonical form using the `--type=bool` type |
7f0a02be | 229 | specifier, 'git config' will ensure that the output is "true" or |
5f7b91ba JH |
230 | "false" (spelled in lowercase). |
231 | ||
232 | integer:: | |
233 | The value for many variables that specify various sizes can | |
234 | be suffixed with `k`, `M`,... to mean "scale the number by | |
235 | 1024", "by 1024x1024", etc. | |
236 | ||
b92c1a28 | 237 | color:: |
adb33566 JK |
238 | The value for a variable that takes a color is a list of |
239 | colors (at most two, one for foreground and one for background) | |
240 | and attributes (as many as you want), separated by spaces. | |
5f456b3c | 241 | + |
adb33566 JK |
242 | The basic colors accepted are `normal`, `black`, `red`, `green`, `yellow`, |
243 | `blue`, `magenta`, `cyan` and `white`. The first color given is the | |
244 | foreground; the second is the background. | |
5ee87585 | 245 | + |
adb33566 JK |
246 | Colors may also be given as numbers between 0 and 255; these use ANSI |
247 | 256-color mode (but note that not all terminals may support this). If | |
248 | your terminal supports it, you may also specify 24-bit RGB values as | |
249 | hex, like `#ff0ab3`. | |
250 | + | |
9dc3515c JK |
251 | The accepted attributes are `bold`, `dim`, `ul`, `blink`, `reverse`, |
252 | `italic`, and `strike` (for crossed-out or "strikethrough" letters). | |
253 | The position of any attributes with respect to the colors | |
54590a0e JK |
254 | (before, after, or in between), doesn't matter. Specific attributes may |
255 | be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`, | |
256 | `no-ul`, etc). | |
adb33566 | 257 | + |
512aba26 JK |
258 | An empty color string produces no color effect at all. This can be used |
259 | to avoid coloring specific elements without disabling color entirely. | |
260 | + | |
adb33566 JK |
261 | For git's pre-defined color slots, the attributes are meant to be reset |
262 | at the beginning of each item in the colored output. So setting | |
263 | `color.decorate.branch` to `black` will paint that branch name in a | |
264 | plain `black`, even if the previous thing on the same output line (e.g. | |
265 | opening parenthesis before the list of branch names in `log --decorate` | |
266 | output) is set to be painted with `bold` or some other attribute. | |
267 | However, custom log formats may do more complicated and layered | |
268 | coloring, and the negated forms may be useful there. | |
b92c1a28 | 269 | |
dca83abd JH |
270 | pathname:: |
271 | A variable that takes a pathname value can be given a | |
272 | string that begins with "`~/`" or "`~user/`", and the usual | |
273 | tilde expansion happens to such a string: `~/` | |
274 | is expanded to the value of `$HOME`, and `~user/` to the | |
275 | specified user's home directory. | |
276 | ||
5f7b91ba | 277 | |
1ab661dd PB |
278 | Variables |
279 | ~~~~~~~~~ | |
280 | ||
281 | Note that this list is non-comprehensive and not necessarily complete. | |
b8936cf0 | 282 | For command-specific variables, you will find a more detailed description |
93728b23 CA |
283 | in the appropriate manual page. |
284 | ||
285 | Other git-related tools may and do use their own variables. When | |
286 | inventing new variables for use in your own tool, make sure their | |
287 | names do not conflict with those that are used by Git itself and | |
288 | other popular tools, and describe them in your documentation. | |
289 | ||
838ef420 | 290 | include::config/advice.txt[] |
75194438 | 291 | |
1a394fa9 | 292 | include::config/core.txt[] |
dce96489 | 293 | |
29120d8e | 294 | include::config/add.txt[] |
13bd2134 | 295 | |
f740c8f1 | 296 | include::config/alias.txt[] |
dfd42a3c | 297 | |
d293ffef | 298 | include::config/am.txt[] |
e97a5e76 | 299 | |
696d4796 | 300 | include::config/apply.txt[] |
1ab661dd | 301 | |
d09467b6 | 302 | include::config/blame.txt[] |
8578037b | 303 | |
7273b95d | 304 | include::config/branch.txt[] |
a5ba2cbe | 305 | |
6b0b9740 | 306 | include::config/browser.txt[] |
584627b4 | 307 | |
9140b410 | 308 | include::config/checkout.txt[] |
fa655d84 | 309 | |
328e629c | 310 | include::config/clean.txt[] |
2122591b | 311 | |
79f62e7d JS |
312 | color.advice:: |
313 | A boolean to enable/disable color in hints (e.g. when a push | |
314 | failed, see `advice.*` for a list). May be set to `always`, | |
315 | `false` (or `never`) or `auto` (or `true`), in which case colors | |
316 | are used only when the error output goes to a terminal. If | |
317 | unset, then the value of `color.ui` is used (`auto` by default). | |
318 | ||
319 | color.advice.hint:: | |
320 | Use customized color for hints. | |
321 | ||
8578037b NTND |
322 | color.blame.highlightRecent:: |
323 | This can be used to color the metadata of a blame line depending | |
324 | on age of the line. | |
325 | + | |
326 | This setting should be set to a comma-separated list of color and date settings, | |
327 | starting and ending with a color, the dates should be set from oldest to newest. | |
328 | The metadata will be colored given the colors if the the line was introduced | |
329 | before the given timestamp, overwriting older timestamped colors. | |
330 | + | |
331 | Instead of an absolute timestamp relative timestamps work as well, e.g. | |
332 | 2.weeks.ago is valid to address anything older than 2 weeks. | |
333 | + | |
334 | It defaults to 'blue,12 month ago,white,1 month ago,red', which colors | |
335 | everything older than one year blue, recent changes between one month and | |
336 | one year old are kept white, and lines introduced within the last month are | |
337 | colored red. | |
338 | ||
339 | color.blame.repeatedLines:: | |
340 | Use the customized color for the part of git-blame output that | |
341 | is repeated meta information per line (such as commit id, | |
342 | author name, date and timezone). Defaults to cyan. | |
343 | ||
f3673988 BG |
344 | color.branch:: |
345 | A boolean to enable/disable color in the output of | |
5162e697 | 346 | linkgit:git-branch[1]. May be set to `always`, |
cec99d8c | 347 | `false` (or `never`) or `auto` (or `true`), in which case colors are used |
14d16e2b MM |
348 | only when the output is to a terminal. If unset, then the |
349 | value of `color.ui` is used (`auto` by default). | |
f3673988 BG |
350 | |
351 | color.branch.<slot>:: | |
352 | Use customized color for branch coloration. `<slot>` is one of | |
353 | `current` (the current branch), `local` (a local branch), | |
dbda21fa FC |
354 | `remote` (a remote-tracking branch in refs/remotes/), |
355 | `upstream` (upstream tracking branch), `plain` (other | |
4f193f20 | 356 | refs). |
f3673988 | 357 | |
a159ca0c | 358 | color.diff:: |
6999c540 MG |
359 | Whether to use ANSI escape sequences to add color to patches. |
360 | If this is set to `always`, linkgit:git-diff[1], | |
361 | linkgit:git-log[1], and linkgit:git-show[1] will use color | |
362 | for all patches. If it is set to `true` or `auto`, those | |
363 | commands will only use color when output is to the terminal. | |
14d16e2b MM |
364 | If unset, then the value of `color.ui` is used (`auto` by |
365 | default). | |
6999c540 | 366 | + |
a58088ab | 367 | This does not affect linkgit:git-format-patch[1] or the |
6999c540 MG |
368 | 'git-diff-{asterisk}' plumbing commands. Can be overridden on the |
369 | command line with the `--color[=<when>]` option. | |
b5376648 | 370 | |
a159ca0c | 371 | color.diff.<slot>:: |
4f193f20 MW |
372 | Use customized color for diff colorization. `<slot>` specifies |
373 | which part of the patch to use the specified color, and is one | |
74b15bfb JK |
374 | of `context` (context text - `plain` is a historical synonym), |
375 | `meta` (metainformation), `frag` | |
89cb73a1 | 376 | (hunk header), 'func' (function in hunk header), `old` (removed lines), |
61e89eaa SB |
377 | `new` (added lines), `commit` (commit headers), `whitespace` |
378 | (highlighting whitespace errors), `oldMoved` (deleted lines), | |
379 | `newMoved` (added lines), `oldMovedDimmed`, `oldMovedAlternative`, | |
380 | `oldMovedAlternativeDimmed`, `newMovedDimmed`, `newMovedAlternative` | |
a7be92ac JS |
381 | `newMovedAlternativeDimmed` (See the '<mode>' |
382 | setting of '--color-moved' in linkgit:git-diff[1] for details), | |
383 | `contextDimmed`, `oldDimmed`, `newDimmed`, `contextBold`, | |
384 | `oldBold`, and `newBold` (see linkgit:git-range-diff[1] for details). | |
b5376648 | 385 | |
5e11bee6 NR |
386 | color.decorate.<slot>:: |
387 | Use customized color for 'git log --decorate' output. `<slot>` is one | |
388 | of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local | |
09c4ba41 NTND |
389 | branches, remote-tracking branches, tags, stash and HEAD, respectively |
390 | and `grafted` for grafted commits. | |
5e11bee6 | 391 | |
7e8f59d5 RS |
392 | color.grep:: |
393 | When set to `always`, always highlight matches. When `false` (or | |
394 | `never`), never. When set to `true` or `auto`, use color only | |
14d16e2b MM |
395 | when the output is written to the terminal. If unset, then the |
396 | value of `color.ui` is used (`auto` by default). | |
7e8f59d5 | 397 | |
55f638bd ML |
398 | color.grep.<slot>:: |
399 | Use customized color for grep colorization. `<slot>` specifies which | |
400 | part of the line to use the specified color, and is one of | |
401 | + | |
402 | -- | |
00588bb5 ML |
403 | `context`;; |
404 | non-matching text in context lines (when using `-A`, `-B`, or `-C`) | |
55f638bd ML |
405 | `filename`;; |
406 | filename prefix (when not using `-h`) | |
00588bb5 ML |
407 | `function`;; |
408 | function name lines (when using `-p`) | |
f8a0c6e7 | 409 | `lineNumber`;; |
55f638bd | 410 | line number prefix (when using `-n`) |
6653fec3 TB |
411 | `column`;; |
412 | column number prefix (when using `--column`) | |
55f638bd | 413 | `match`;; |
79a77109 RS |
414 | matching text (same as setting `matchContext` and `matchSelected`) |
415 | `matchContext`;; | |
416 | matching text in context lines | |
417 | `matchSelected`;; | |
418 | matching text in selected lines | |
00588bb5 ML |
419 | `selected`;; |
420 | non-matching text in selected lines | |
55f638bd ML |
421 | `separator`;; |
422 | separators between fields on a line (`:`, `-`, and `=`) | |
423 | and between hunks (`--`) | |
424 | -- | |
7e8f59d5 | 425 | |
b4c61ed6 | 426 | color.interactive:: |
47ee06f1 | 427 | When set to `always`, always use colors for interactive prompts |
7a9b0b80 JX |
428 | and displays (such as those used by "git-add --interactive" and |
429 | "git-clean --interactive"). When false (or `never`), never. | |
430 | When set to `true` or `auto`, use colors only when the output is | |
14d16e2b MM |
431 | to the terminal. If unset, then the value of `color.ui` is |
432 | used (`auto` by default). | |
b4c61ed6 JH |
433 | |
434 | color.interactive.<slot>:: | |
7a9b0b80 JX |
435 | Use customized color for 'git add --interactive' and 'git clean |
436 | --interactive' output. `<slot>` may be `prompt`, `header`, `help` | |
437 | or `error`, for four distinct types of normal output from | |
b92c1a28 | 438 | interactive commands. |
b4c61ed6 | 439 | |
1d77043b JH |
440 | color.pager:: |
441 | A boolean to enable/disable colored output when the pager is in | |
442 | use (default is true). | |
443 | ||
79f62e7d JS |
444 | color.push:: |
445 | A boolean to enable/disable color in push errors. May be set to | |
446 | `always`, `false` (or `never`) or `auto` (or `true`), in which | |
447 | case colors are used only when the error output goes to a terminal. | |
448 | If unset, then the value of `color.ui` is used (`auto` by default). | |
449 | ||
450 | color.push.error:: | |
451 | Use customized color for push errors. | |
452 | ||
bf1a11f0 HWN |
453 | color.remote:: |
454 | If set, keywords at the start of the line are highlighted. The | |
455 | keywords are "error", "warning", "hint" and "success", and are | |
456 | matched case-insensitively. May be set to `always`, `false` (or | |
457 | `never`) or `auto` (or `true`). If unset, then the value of | |
458 | `color.ui` is used (`auto` by default). | |
459 | ||
460 | color.remote.<slot>:: | |
461 | Use customized color for each remote keyword. `<slot>` may be | |
462 | `hint`, `warning`, `success` or `error` which match the | |
463 | corresponding keyword. | |
464 | ||
da0005b8 | 465 | color.showBranch:: |
ab07ba2a MH |
466 | A boolean to enable/disable color in the output of |
467 | linkgit:git-show-branch[1]. May be set to `always`, | |
468 | `false` (or `never`) or `auto` (or `true`), in which case colors are used | |
14d16e2b MM |
469 | only when the output is to a terminal. If unset, then the |
470 | value of `color.ui` is used (`auto` by default). | |
ab07ba2a | 471 | |
1d77043b JH |
472 | color.status:: |
473 | A boolean to enable/disable color in the output of | |
5162e697 | 474 | linkgit:git-status[1]. May be set to `always`, |
cec99d8c | 475 | `false` (or `never`) or `auto` (or `true`), in which case colors are used |
14d16e2b MM |
476 | only when the output is to a terminal. If unset, then the |
477 | value of `color.ui` is used (`auto` by default). | |
1d77043b JH |
478 | |
479 | color.status.<slot>:: | |
480 | Use customized color for status colorization. `<slot>` is | |
481 | one of `header` (the header text of the status message), | |
82dca848 SP |
482 | `added` or `updated` (files which are added but not committed), |
483 | `changed` (files which are changed but not added in the index), | |
2de9b711 | 484 | `untracked` (files which are not tracked by Git), |
0d6accc0 | 485 | `branch` (the current branch), |
950ce2e2 | 486 | `nobranch` (the color the 'no branch' warning is shown in, defaulting |
93fdf301 SK |
487 | to red), |
488 | `localBranch` or `remoteBranch` (the local and remote branch names, | |
489 | respectively, when branch and tracking information is displayed in the | |
490 | status short-format), or | |
0d6accc0 | 491 | `unmerged` (files which have unmerged changes). |
1d77043b | 492 | |
79f62e7d JS |
493 | color.transport:: |
494 | A boolean to enable/disable color when pushes are rejected. May be | |
495 | set to `always`, `false` (or `never`) or `auto` (or `true`), in which | |
496 | case colors are used only when the error output goes to a terminal. | |
497 | If unset, then the value of `color.ui` is used (`auto` by default). | |
498 | ||
499 | color.transport.rejected:: | |
500 | Use customized color when a push was rejected. | |
501 | ||
6b2f2d98 | 502 | color.ui:: |
6999c540 MG |
503 | This variable determines the default value for variables such |
504 | as `color.diff` and `color.grep` that control the use of color | |
505 | per command family. Its scope will expand as more commands learn | |
506 | configuration to set a default for the `--color` option. Set it | |
4c7f1819 MM |
507 | to `false` or `never` if you prefer Git commands not to use |
508 | color unless enabled explicitly with some other configuration | |
509 | or the `--color` option. Set it to `always` if you want all | |
510 | output not intended for machine consumption to use color, to | |
511 | `true` or `auto` (this is the default since Git 1.8.4) if you | |
512 | want such output to use color when written to the terminal. | |
6b2f2d98 | 513 | |
7e29b825 NTND |
514 | column.ui:: |
515 | Specify whether supported commands should output in columns. | |
516 | This variable consists of a list of tokens separated by spaces | |
517 | or commas: | |
518 | + | |
5e62cc14 RR |
519 | These options control when the feature should be enabled |
520 | (defaults to 'never'): | |
521 | + | |
7e29b825 NTND |
522 | -- |
523 | `always`;; | |
524 | always show in columns | |
525 | `never`;; | |
526 | never show in columns | |
527 | `auto`;; | |
528 | show in columns if the output is to the terminal | |
5e62cc14 RR |
529 | -- |
530 | + | |
531 | These options control layout (defaults to 'column'). Setting any | |
532 | of these implies 'always' if none of 'always', 'never', or 'auto' are | |
533 | specified. | |
534 | + | |
535 | -- | |
077539d7 | 536 | `column`;; |
5e62cc14 | 537 | fill columns before rows |
077539d7 NTND |
538 | `row`;; |
539 | fill rows before columns | |
7e29b825 NTND |
540 | `plain`;; |
541 | show in one column | |
5e62cc14 RR |
542 | -- |
543 | + | |
544 | Finally, these options can be combined with a layout option (defaults | |
545 | to 'nodense'): | |
546 | + | |
547 | -- | |
3f8eccbe NTND |
548 | `dense`;; |
549 | make unequal size columns to utilize more space | |
550 | `nodense`;; | |
551 | make equal size columns | |
7e29b825 | 552 | -- |
7e29b825 | 553 | |
ebe31ef2 NTND |
554 | column.branch:: |
555 | Specify whether to output branch listing in `git branch` in columns. | |
556 | See `column.ui` for details. | |
557 | ||
1b8fd467 JX |
558 | column.clean:: |
559 | Specify the layout when list items in `git clean -i`, which always | |
560 | shows files and directories in columns. See `column.ui` for details. | |
561 | ||
323d0530 NTND |
562 | column.status:: |
563 | Specify whether to output untracked files in `git status` in columns. | |
564 | See `column.ui` for details. | |
565 | ||
d96e3c15 NTND |
566 | column.tag:: |
567 | Specify whether to output tag listing in `git tag` in columns. | |
568 | See `column.ui` for details. | |
569 | ||
51fb3a3d RT |
570 | commit.cleanup:: |
571 | This setting overrides the default of the `--cleanup` option in | |
572 | `git commit`. See linkgit:git-commit[1] for details. Changing the | |
573 | default can be useful when you always want to keep lines that begin | |
574 | with comment character `#` in your log message, in which case you | |
575 | would do `git config commit.cleanup whitespace` (note that you will | |
576 | have to remove the help lines that begin with `#` in the commit log | |
577 | template yourself, if you do this). | |
578 | ||
da0005b8 | 579 | commit.gpgSign:: |
d95bfb12 NV |
580 | |
581 | A boolean to specify whether all commits should be GPG signed. | |
582 | Use of this option when doing operations such as rebase can | |
583 | result in a large number of commits being signed. It may be | |
584 | convenient to use an agent to avoid typing your GPG passphrase | |
585 | several times. | |
586 | ||
88955ed2 | 587 | commit.status:: |
bed575e4 JHI |
588 | A boolean to enable/disable inclusion of status information in the |
589 | commit message template when using an editor to prepare the commit | |
590 | message. Defaults to true. | |
591 | ||
b0f34c3d | 592 | commit.template:: |
dca83abd JH |
593 | Specify the pathname of a file to use as the template for |
594 | new commit messages. | |
b0f34c3d | 595 | |
aaab8420 PB |
596 | commit.verbose:: |
597 | A boolean or int to specify the level of verbose with `git commit`. | |
598 | See linkgit:git-commit[1]. | |
599 | ||
a6fc9fd3 JK |
600 | credential.helper:: |
601 | Specify an external helper to be called when a username or | |
602 | password credential is needed; the helper may consult external | |
24321375 JK |
603 | storage to avoid prompting the user for the credentials. Note |
604 | that multiple helpers may be defined. See linkgit:gitcredentials[7] | |
605 | for details. | |
a6fc9fd3 JK |
606 | |
607 | credential.useHttpPath:: | |
608 | When acquiring credentials, consider the "path" component of an http | |
609 | or https URL to be important. Defaults to false. See | |
610 | linkgit:gitcredentials[7] for more information. | |
611 | ||
612 | credential.username:: | |
613 | If no username is set for a network authentication, use this username | |
614 | by default. See credential.<context>.* below, and | |
615 | linkgit:gitcredentials[7]. | |
616 | ||
617 | credential.<url>.*:: | |
618 | Any of the credential.* options above can be applied selectively to | |
619 | some credentials. For example "credential.https://example.com.username" | |
620 | would set the default username only for https connections to | |
621 | example.com. See linkgit:gitcredentials[7] for details on how URLs are | |
622 | matched. | |
623 | ||
7f4d4746 NP |
624 | credentialCache.ignoreSIGHUP:: |
625 | Tell git-credential-cache--daemon to ignore SIGHUP, instead of quitting. | |
626 | ||
6532f374 NTND |
627 | completion.commands:: |
628 | This is only used by git-completion.bash to add or remove | |
629 | commands from the list of completed commands. Normally only | |
630 | porcelain commands and a few select others are completed. You | |
631 | can add more commands, separated by space, in this | |
632 | variable. Prefixing the command with '-' will remove it from | |
633 | the existing list. | |
634 | ||
19299a84 | 635 | include::diff-config.txt[] |
afcbc8e7 DA |
636 | |
637 | difftool.<tool>.path:: | |
638 | Override the path for the given tool. This is useful in case | |
639 | your tool is not in the PATH. | |
640 | ||
641 | difftool.<tool>.cmd:: | |
642 | Specify the command to invoke the specified diff tool. | |
643 | The specified command is evaluated in shell with the following | |
644 | variables available: 'LOCAL' is set to the name of the temporary | |
645 | file containing the contents of the diff pre-image and 'REMOTE' | |
646 | is set to the name of the temporary file containing the contents | |
647 | of the diff post-image. | |
648 | ||
a904392e DA |
649 | difftool.prompt:: |
650 | Prompt before each invocation of the diff tool. | |
651 | ||
d9545c7f EW |
652 | fastimport.unpackLimit:: |
653 | If the number of objects imported by linkgit:git-fast-import[1] | |
654 | is below this limit, then the objects will be unpacked into | |
655 | loose object files. However if the number of imported objects | |
656 | equals or exceeds this limit then the pack will be stored as a | |
657 | pack. Storing the pack from a fast-import can make the import | |
658 | operation complete faster, especially on slow filesystems. If | |
659 | not set, the value of `transfer.unpackLimit` is used instead. | |
660 | ||
ca0e61c0 | 661 | include::fetch-config.txt[] |
42cc7485 | 662 | |
e108551a | 663 | include::format-config.txt[] |
bb52995f | 664 | |
26488f59 RR |
665 | filter.<driver>.clean:: |
666 | The command which is used to convert the content of a worktree | |
667 | file to a blob upon checkin. See linkgit:gitattributes[5] for | |
668 | details. | |
669 | ||
670 | filter.<driver>.smudge:: | |
671 | The command which is used to convert the content of a blob | |
672 | object to a worktree file upon checkout. See | |
673 | linkgit:gitattributes[5] for details. | |
674 | ||
2becf00f | 675 | fsck.<msg-id>:: |
b2558abd ÆAB |
676 | During fsck git may find issues with legacy data which |
677 | wouldn't be generated by current versions of git, and which | |
678 | wouldn't be sent over the wire if `transfer.fsckObjects` was | |
679 | set. This feature is intended to support working with legacy | |
680 | repositories containing such data. | |
681 | + | |
682 | Setting `fsck.<msg-id>` will be picked up by linkgit:git-fsck[1], but | |
1362df0d ÆAB |
683 | to accept pushes of such data set `receive.fsck.<msg-id>` instead, or |
684 | to clone or fetch it set `fetch.fsck.<msg-id>`. | |
b2558abd ÆAB |
685 | + |
686 | The rest of the documentation discusses `fsck.*` for brevity, but the | |
1362df0d ÆAB |
687 | same applies for the corresponding `receive.fsck.*` and |
688 | `fetch.<msg-id>.*`. variables. | |
b2558abd | 689 | + |
d786da1c ÆAB |
690 | Unlike variables like `color.ui` and `core.editor` the |
691 | `receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>` variables will not | |
692 | fall back on the `fsck.<msg-id>` configuration if they aren't set. To | |
693 | uniformly configure the same fsck settings in different circumstances | |
694 | all three of them they must all set to the same values. | |
695 | + | |
b2558abd ÆAB |
696 | When `fsck.<msg-id>` is set, errors can be switched to warnings and |
697 | vice versa by configuring the `fsck.<msg-id>` setting where the | |
698 | `<msg-id>` is the fsck message ID and the value is one of `error`, | |
699 | `warn` or `ignore`. For convenience, fsck prefixes the error/warning | |
700 | with the message ID, e.g. "missingEmail: invalid author/committer line | |
701 | - missing email" means that setting `fsck.missingEmail = ignore` will | |
702 | hide that issue. | |
703 | + | |
704 | In general, it is better to enumerate existing objects with problems | |
705 | with `fsck.skipList`, instead of listing the kind of breakages these | |
706 | problematic objects share to be ignored, as doing the latter will | |
707 | allow new instances of the same breakages go unnoticed. | |
8a6d0525 ÆAB |
708 | + |
709 | Setting an unknown `fsck.<msg-id>` value will cause fsck to die, but | |
710 | doing the same for `receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>` | |
711 | will only cause git to warn. | |
2becf00f | 712 | |
1335f732 | 713 | fsck.skipList:: |
12b1c50a | 714 | The path to a list of object names (i.e. one unabbreviated SHA-1 per |
1335f732 | 715 | line) that are known to be broken in a non-fatal way and should |
371a6550 ÆAB |
716 | be ignored. On versions of Git 2.20 and later comments ('#'), empty |
717 | lines, and any leading and trailing whitespace is ignored. Everything | |
718 | but a SHA-1 per line will error out on older versions. | |
f706c42b ÆAB |
719 | + |
720 | This feature is useful when an established project should be accepted | |
721 | despite early commits containing errors that can be safely ignored | |
722 | such as invalid committer email addresses. Note: corrupt objects | |
723 | cannot be skipped with this setting. | |
b2558abd | 724 | + |
1362df0d ÆAB |
725 | Like `fsck.<msg-id>` this variable has corresponding |
726 | `receive.fsck.skipList` and `fetch.fsck.skipList` variants. | |
d786da1c ÆAB |
727 | + |
728 | Unlike variables like `color.ui` and `core.editor` the | |
729 | `receive.fsck.skipList` and `fetch.fsck.skipList` variables will not | |
730 | fall back on the `fsck.skipList` configuration if they aren't set. To | |
731 | uniformly configure the same fsck settings in different circumstances | |
732 | all three of them they must all set to the same values. | |
58dc440b ÆAB |
733 | + |
734 | Older versions of Git (before 2.20) documented that the object names | |
735 | list should be sorted. This was never a requirement, the object names | |
3b41fb0c RS |
736 | could appear in any order, but when reading the list we tracked whether |
737 | the list was sorted for the purposes of an internal binary search | |
738 | implementation, which could save itself some work with an already sorted | |
739 | list. Unless you had a humongous list there was no reason to go out of | |
740 | your way to pre-sort the list. After Git version 2.20 a hash implementation | |
741 | is used instead, so there's now no reason to pre-sort the list. | |
1335f732 | 742 | |
125f8146 NTND |
743 | gc.aggressiveDepth:: |
744 | The depth parameter used in the delta compression | |
745 | algorithm used by 'git gc --aggressive'. This defaults | |
07e7dbf0 | 746 | to 50. |
125f8146 | 747 | |
0d7566a5 TT |
748 | gc.aggressiveWindow:: |
749 | The window size parameter used in the delta compression | |
0b444cdb | 750 | algorithm used by 'git gc --aggressive'. This defaults |
f78683f3 | 751 | to 250. |
0d7566a5 | 752 | |
e9831e83 JH |
753 | gc.auto:: |
754 | When there are approximately more than this many loose | |
755 | objects in the repository, `git gc --auto` will pack them. | |
756 | Some Porcelain commands use this command to perform a | |
80cd9cf9 MB |
757 | light-weight garbage collection from time to time. The |
758 | default value is 6700. Setting this to 0 disables it. | |
e9831e83 | 759 | |
da0005b8 | 760 | gc.autoPackLimit:: |
17815501 JH |
761 | When there are more than this many packs that are not |
762 | marked with `*.keep` file in the repository, `git gc | |
80cd9cf9 | 763 | --auto` consolidates them into one larger pack. The |
97063974 | 764 | default value is 50. Setting this to 0 disables it. |
17815501 | 765 | |
da0005b8 | 766 | gc.autoDetach:: |
f745acb0 | 767 | Make `git gc --auto` return immediately and run in background |
9f673f94 NTND |
768 | if the system supports it. Default is true. |
769 | ||
55dfe13d NTND |
770 | gc.bigPackThreshold:: |
771 | If non-zero, all packs larger than this limit are kept when | |
772 | `git gc` is run. This is very similar to `--keep-base-pack` | |
773 | except that all packs that meet the threshold are kept, not | |
774 | just the base pack. Defaults to zero. Common unit suffixes of | |
775 | 'k', 'm', or 'g' are supported. | |
8fc67762 NTND |
776 | + |
777 | Note that if the number of kept packs is more than gc.autoPackLimit, | |
778 | this configuration variable is ignored, all packs except the base pack | |
779 | will be repacked. After this the number of packs should go below | |
780 | gc.autoPackLimit and gc.bigPackThreshold should be respected again. | |
55dfe13d | 781 | |
d915114a DS |
782 | gc.writeCommitGraph:: |
783 | If true, then gc will rewrite the commit-graph file when | |
784 | linkgit:git-gc[1] is run. When using linkgit:git-gc[1] | |
785 | '--auto' the commit-graph will be updated if housekeeping is | |
786 | required. Default is false. See linkgit:git-commit-graph[1] | |
787 | for details. | |
788 | ||
a831c06a | 789 | gc.logExpiry:: |
30299702 JN |
790 | If the file gc.log exists, then `git gc --auto` will print |
791 | its content and exit with status zero instead of running | |
a831c06a DT |
792 | unless that file is more than 'gc.logExpiry' old. Default is |
793 | "1.day". See `gc.pruneExpire` for more ways to specify its | |
794 | value. | |
795 | ||
da0005b8 | 796 | gc.packRefs:: |
efc266e8 JN |
797 | Running `git pack-refs` in a repository renders it |
798 | unclonable by Git versions prior to 1.5.1.2 over dumb | |
799 | transports such as HTTP. This variable determines whether | |
4be0c352 | 800 | 'git gc' runs `git pack-refs`. This can be set to `notbare` |
efc266e8 JN |
801 | to enable it within all non-bare repos or it can be set to a |
802 | boolean value. The default is `true`. | |
c2120e5e | 803 | |
da0005b8 | 804 | gc.pruneExpire:: |
0b444cdb | 805 | When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'. |
8e8daf33 | 806 | Override the grace period with this config variable. The value |
8cc88166 ES |
807 | "now" may be used to disable this grace period and always prune |
808 | unreachable objects immediately, or "never" may be used to | |
f1350d0c MM |
809 | suppress pruning. This feature helps prevent corruption when |
810 | 'git gc' runs concurrently with another process writing to the | |
811 | repository; see the "NOTES" section of linkgit:git-gc[1]. | |
25ee9731 | 812 | |
114ff888 | 813 | gc.worktreePruneExpire:: |
b07244f4 | 814 | When 'git gc' is run, it calls |
fe819b4b | 815 | 'git worktree prune --expire 3.months.ago'. |
b07244f4 MH |
816 | This config variable can be used to set a different grace |
817 | period. The value "now" may be used to disable the grace | |
f212dcc7 | 818 | period and prune `$GIT_DIR/worktrees` immediately, or "never" |
8cc88166 | 819 | may be used to suppress pruning. |
e3df33bb | 820 | |
da0005b8 NTND |
821 | gc.reflogExpire:: |
822 | gc.<pattern>.reflogExpire:: | |
0b444cdb | 823 | 'git reflog expire' removes reflog entries older than |
8cc88166 ES |
824 | this time; defaults to 90 days. The value "now" expires all |
825 | entries immediately, and "never" suppresses expiration | |
826 | altogether. With "<pattern>" (e.g. | |
eb523a8d JH |
827 | "refs/stash") in the middle the setting applies only to |
828 | the refs that match the <pattern>. | |
4aec56d1 | 829 | |
da0005b8 | 830 | gc.reflogExpireUnreachable:: |
f04c6904 | 831 | gc.<pattern>.reflogExpireUnreachable:: |
0b444cdb | 832 | 'git reflog expire' removes reflog entries older than |
4aec56d1 | 833 | this time and are not reachable from the current tip; |
8cc88166 ES |
834 | defaults to 30 days. The value "now" expires all entries |
835 | immediately, and "never" suppresses expiration altogether. | |
836 | With "<pattern>" (e.g. "refs/stash") | |
eb523a8d JH |
837 | in the middle, the setting applies only to the refs that |
838 | match the <pattern>. | |
4aec56d1 | 839 | |
da0005b8 | 840 | gc.rerereResolved:: |
48c32424 | 841 | Records of conflicted merge you resolved earlier are |
0b444cdb | 842 | kept for this many days when 'git rerere gc' is run. |
6e96cb52 | 843 | You can also use more human-readable "1.month.ago", etc. |
5162e697 | 844 | The default is 60 days. See linkgit:git-rerere[1]. |
48c32424 | 845 | |
da0005b8 | 846 | gc.rerereUnresolved:: |
48c32424 | 847 | Records of conflicted merge you have not resolved are |
0b444cdb | 848 | kept for this many days when 'git rerere gc' is run. |
6e96cb52 | 849 | You can also use more human-readable "1.month.ago", etc. |
5162e697 | 850 | The default is 15 days. See linkgit:git-rerere[1]. |
48c32424 | 851 | |
3d28c3d8 | 852 | include::gitcvs-config.txt[] |
04752868 | 853 | |
cd82323f JN |
854 | gitweb.category:: |
855 | gitweb.description:: | |
856 | gitweb.owner:: | |
857 | gitweb.url:: | |
858 | See linkgit:gitweb[1] for description. | |
859 | ||
860 | gitweb.avatar:: | |
861 | gitweb.blame:: | |
862 | gitweb.grep:: | |
863 | gitweb.highlight:: | |
864 | gitweb.patches:: | |
865 | gitweb.pickaxe:: | |
866 | gitweb.remote_heads:: | |
da0005b8 | 867 | gitweb.showSizes:: |
cd82323f JN |
868 | gitweb.snapshot:: |
869 | See linkgit:gitweb.conf[5] for description. | |
870 | ||
b22520a3 | 871 | grep.lineNumber:: |
23f8239b | 872 | If set to true, enable `-n` option by default. |
b22520a3 | 873 | |
6653fec3 TB |
874 | grep.column:: |
875 | If set to true, enable the `--column` option by default. | |
876 | ||
84befcd0 S |
877 | grep.patternType:: |
878 | Set the default matching behavior. Using a value of 'basic', 'extended', | |
bcf9626a MM |
879 | 'fixed', or 'perl' will enable the `--basic-regexp`, `--extended-regexp`, |
880 | `--fixed-strings`, or `--perl-regexp` option accordingly, while the | |
84befcd0 S |
881 | value 'default' will return to the default matching behavior. |
882 | ||
b22520a3 | 883 | grep.extendedRegexp:: |
bcf9626a | 884 | If set to true, enable `--extended-regexp` option by default. This |
ae9f6311 | 885 | option is ignored when the `grep.patternType` option is set to a value |
84befcd0 | 886 | other than 'default'. |
b22520a3 | 887 | |
89f09dd3 VL |
888 | grep.threads:: |
889 | Number of grep worker threads to use. | |
890 | See `grep.threads` in linkgit:git-grep[1] for more information. | |
891 | ||
ecd9ba61 TG |
892 | grep.fallbackToNoIndex:: |
893 | If set to true, fall back to git grep --no-index if git grep | |
894 | is executed outside of a git repository. Defaults to false. | |
895 | ||
0c5e70f0 | 896 | gpg.program:: |
f212dcc7 | 897 | Use this custom program instead of "`gpg`" found on `$PATH` when |
0c5e70f0 | 898 | making or verifying a PGP signature. The program must support the |
06ab60c0 | 899 | same command-line interface as GPG, namely, to verify a detached |
f212dcc7 | 900 | signature, "`gpg --verify $file - <$signature`" is run, and the |
0c5e70f0 | 901 | program is expected to signal a good signature by exiting with |
f745acb0 | 902 | code 0, and to generate an ASCII-armored detached signature, the |
f212dcc7 | 903 | standard input of "`gpg -bsau $key`" is fed with the contents to be |
0c5e70f0 JH |
904 | signed, and the program is expected to send the result to its |
905 | standard output. | |
906 | ||
57a8dd75 HS |
907 | gpg.format:: |
908 | Specifies which key format to use when signing with `--gpg-sign`. | |
1e7adb97 | 909 | Default is "openpgp" and another possible value is "x509". |
57a8dd75 | 910 | |
b02f51b1 HS |
911 | gpg.<format>.program:: |
912 | Use this to customize the program used for the signing format you | |
913 | chose. (see `gpg.program` and `gpg.format`) `gpg.program` can still | |
1e7adb97 HS |
914 | be used as a legacy synonym for `gpg.openpgp.program`. The default |
915 | value for `gpg.x509.program` is "gpgsm". | |
b02f51b1 | 916 | |
fb981ced | 917 | include::gui-config.txt[] |
a2df1fb2 | 918 | |
390c3480 AG |
919 | guitool.<name>.cmd:: |
920 | Specifies the shell command line to execute when the corresponding item | |
921 | of the linkgit:git-gui[1] `Tools` menu is invoked. This option is | |
922 | mandatory for every tool. The command is executed from the root of | |
923 | the working directory, and in the environment it receives the name of | |
eee7f4a2 | 924 | the tool as `GIT_GUITOOL`, the name of the currently selected file as |
390c3480 AG |
925 | 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if |
926 | the head is detached, 'CUR_BRANCH' is empty). | |
927 | ||
da0005b8 | 928 | guitool.<name>.needsFile:: |
390c3480 AG |
929 | Run the tool only if a diff is selected in the GUI. It guarantees |
930 | that 'FILENAME' is not empty. | |
931 | ||
da0005b8 | 932 | guitool.<name>.noConsole:: |
390c3480 AG |
933 | Run the command silently, without creating a window to display its |
934 | output. | |
935 | ||
da0005b8 | 936 | guitool.<name>.noRescan:: |
390c3480 AG |
937 | Don't rescan the working directory for changes after the tool |
938 | finishes execution. | |
939 | ||
940 | guitool.<name>.confirm:: | |
941 | Show a confirmation dialog before actually running the tool. | |
942 | ||
da0005b8 | 943 | guitool.<name>.argPrompt:: |
390c3480 | 944 | Request a string argument from the user, and pass it to the tool |
47d81b5c | 945 | through the `ARGS` environment variable. Since requesting an |
390c3480 AG |
946 | argument implies confirmation, the 'confirm' option has no effect |
947 | if this is enabled. If the option is set to 'true', 'yes', or '1', | |
948 | the dialog uses a built-in generic prompt; otherwise the exact | |
949 | value of the variable is used. | |
950 | ||
da0005b8 | 951 | guitool.<name>.revPrompt:: |
390c3480 | 952 | Request a single valid revision from the user, and set the |
47d81b5c | 953 | `REVISION` environment variable. In other aspects this option |
da0005b8 | 954 | is similar to 'argPrompt', and can be used together with it. |
390c3480 | 955 | |
da0005b8 NTND |
956 | guitool.<name>.revUnmerged:: |
957 | Show only unmerged branches in the 'revPrompt' subdialog. | |
390c3480 AG |
958 | This is useful for tools similar to merge or rebase, but not |
959 | for things like checkout or reset. | |
960 | ||
961 | guitool.<name>.title:: | |
962 | Specifies the title to use for the prompt dialog. The default | |
963 | is the tool name. | |
964 | ||
965 | guitool.<name>.prompt:: | |
966 | Specifies the general prompt string to display at the top of | |
da0005b8 | 967 | the dialog, before subsections for 'argPrompt' and 'revPrompt'. |
390c3480 AG |
968 | The default value includes the actual command. |
969 | ||
983a9eeb CC |
970 | help.browser:: |
971 | Specify the browser that will be used to display help in the | |
972 | 'web' format. See linkgit:git-help[1]. | |
973 | ||
974 | help.format:: | |
975 | Override the default help format used by linkgit:git-help[1]. | |
976 | Values 'man', 'info', 'web' and 'html' are supported. 'man' is | |
977 | the default. 'web' and 'html' are the same. | |
978 | ||
da0005b8 | 979 | help.autoCorrect:: |
f0e90716 AR |
980 | Automatically correct and execute mistyped commands after |
981 | waiting for the given number of deciseconds (0.1 sec). If more | |
982 | than one command can be deduced from the entered text, nothing | |
983 | will be executed. If the value of this option is negative, | |
984 | the corrected command will be executed immediately. If the | |
985 | value is 0 - the command will be just shown but not executed. | |
986 | This is the default. | |
987 | ||
da0005b8 | 988 | help.htmlPath:: |
b1f809d0 SS |
989 | Specify the path where the HTML documentation resides. File system paths |
990 | and URLs are supported. HTML pages will be prefixed with this path when | |
991 | help is displayed in the 'web' format. This defaults to the documentation | |
992 | path of your Git installation. | |
993 | ||
9c5665aa | 994 | http.proxy:: |
b2c8c6d9 | 995 | Override the HTTP proxy, normally configured using the 'http_proxy', |
372370f1 KF |
996 | 'https_proxy', and 'all_proxy' environment variables (see `curl(1)`). In |
997 | addition to the syntax understood by curl, it is possible to specify a | |
998 | proxy string with a user name but no password, in which case git will | |
999 | attempt to acquire one in the same way it does for other credentials. See | |
1000 | linkgit:gitcredentials[7] for more information. The syntax thus is | |
1001 | '[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden | |
1002 | on a per-remote basis; see remote.<name>.proxy | |
9c5665aa | 1003 | |
ef976395 KF |
1004 | http.proxyAuthMethod:: |
1005 | Set the method with which to authenticate against the HTTP proxy. This | |
1006 | only takes effect if the configured proxy string contains a user name part | |
1007 | (i.e. is of the form 'user@host' or 'user@host:port'). This can be | |
1008 | overridden on a per-remote basis; see `remote.<name>.proxyAuthMethod`. | |
eee7f4a2 | 1009 | Both can be overridden by the `GIT_HTTP_PROXY_AUTHMETHOD` environment |
ef976395 KF |
1010 | variable. Possible values are: |
1011 | + | |
1012 | -- | |
1013 | * `anyauth` - Automatically pick a suitable authentication method. It is | |
1014 | assumed that the proxy answers an unauthenticated request with a 407 | |
1015 | status code and one or more Proxy-authenticate headers with supported | |
1016 | authentication methods. This is the default. | |
1017 | * `basic` - HTTP Basic authentication | |
1018 | * `digest` - HTTP Digest authentication; this prevents the password from being | |
1019 | transmitted to the proxy in clear text | |
1020 | * `negotiate` - GSS-Negotiate authentication (compare the --negotiate option | |
1021 | of `curl(1)`) | |
1022 | * `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`) | |
1023 | -- | |
9c5665aa | 1024 | |
121061f6 | 1025 | http.emptyAuth:: |
1026 | Attempt authentication without seeking a username or password. This | |
1027 | can be used to attempt GSS-Negotiate authentication without specifying | |
1028 | a username in the URL, as libcurl normally requires a username for | |
1029 | authentication. | |
1030 | ||
26a7b234 PS |
1031 | http.delegation:: |
1032 | Control GSSAPI credential delegation. The delegation is disabled | |
1033 | by default in libcurl since version 7.21.7. Set parameter to tell | |
1034 | the server what it is allowed to delegate when it comes to user | |
1035 | credentials. Used with GSS/kerberos. Possible values are: | |
1036 | + | |
1037 | -- | |
1038 | * `none` - Don't allow any delegation. | |
1039 | * `policy` - Delegates if and only if the OK-AS-DELEGATE flag is set in the | |
1040 | Kerberos service ticket, which is a matter of realm policy. | |
1041 | * `always` - Unconditionally allow the server to delegate. | |
1042 | -- | |
1043 | ||
1044 | ||
8cb01e2f JS |
1045 | http.extraHeader:: |
1046 | Pass an additional HTTP header when communicating with a server. If | |
1047 | more than one such entry exists, all of them are added as extra | |
1048 | headers. To allow overriding the settings inherited from the system | |
1049 | config, an empty value will reset the extra headers to the empty list. | |
1050 | ||
da0005b8 | 1051 | http.cookieFile:: |
e5a39ad8 BN |
1052 | The pathname of a file containing previously stored cookie lines, |
1053 | which should be used | |
2de9b711 | 1054 | in the Git http session, if they match the server. The file format |
bcfb95dd | 1055 | of the file to read cookies from should be plain HTTP headers or |
1cca17df | 1056 | the Netscape/Mozilla cookie file format (see `curl(1)`). |
06ea368b | 1057 | NOTE that the file specified with http.cookieFile is used only as |
912b2acf DB |
1058 | input unless http.saveCookies is set. |
1059 | ||
da0005b8 | 1060 | http.saveCookies:: |
912b2acf | 1061 | If set, store cookies received during requests to the file specified by |
da0005b8 | 1062 | http.cookieFile. Has no effect if http.cookieFile is unset. |
bcfb95dd | 1063 | |
01861cb7 EP |
1064 | http.sslVersion:: |
1065 | The SSL version to use when negotiating an SSL connection, if you | |
1066 | want to force the default. The available and default version | |
1067 | depend on whether libcurl was built against NSS or OpenSSL and the | |
1068 | particular configuration of the crypto library in use. Internally | |
1069 | this sets the 'CURLOPT_SSL_VERSION' option; see the libcurl | |
1070 | documentation for more details on the format of this option and | |
1071 | for the ssl version supported. Actually the possible values of | |
1072 | this option are: | |
1073 | ||
1074 | - sslv2 | |
1075 | - sslv3 | |
1076 | - tlsv1 | |
1077 | - tlsv1.0 | |
1078 | - tlsv1.1 | |
1079 | - tlsv1.2 | |
d81b651f | 1080 | - tlsv1.3 |
01861cb7 EP |
1081 | |
1082 | + | |
eee7f4a2 | 1083 | Can be overridden by the `GIT_SSL_VERSION` environment variable. |
01861cb7 | 1084 | To force git to use libcurl's default ssl version and ignore any |
eee7f4a2 | 1085 | explicit http.sslversion option, set `GIT_SSL_VERSION` to the |
01861cb7 EP |
1086 | empty string. |
1087 | ||
f6f2a9e4 LKS |
1088 | http.sslCipherList:: |
1089 | A list of SSL ciphers to use when negotiating an SSL connection. | |
1090 | The available ciphers depend on whether libcurl was built against | |
1091 | NSS or OpenSSL and the particular configuration of the crypto | |
1092 | library in use. Internally this sets the 'CURLOPT_SSL_CIPHER_LIST' | |
1093 | option; see the libcurl documentation for more details on the format | |
1094 | of this list. | |
1095 | + | |
eee7f4a2 | 1096 | Can be overridden by the `GIT_SSL_CIPHER_LIST` environment variable. |
f6f2a9e4 | 1097 | To force git to use libcurl's default cipher list and ignore any |
eee7f4a2 | 1098 | explicit http.sslCipherList option, set `GIT_SSL_CIPHER_LIST` to the |
f6f2a9e4 LKS |
1099 | empty string. |
1100 | ||
1ab661dd PB |
1101 | http.sslVerify:: |
1102 | Whether to verify the SSL certificate when fetching or pushing | |
dec366c9 SR |
1103 | over HTTPS. Defaults to true. Can be overridden by the |
1104 | `GIT_SSL_NO_VERIFY` environment variable. | |
1ab661dd PB |
1105 | |
1106 | http.sslCert:: | |
1107 | File containing the SSL certificate when fetching or pushing | |
eee7f4a2 | 1108 | over HTTPS. Can be overridden by the `GIT_SSL_CERT` environment |
1ab661dd PB |
1109 | variable. |
1110 | ||
1111 | http.sslKey:: | |
1112 | File containing the SSL private key when fetching or pushing | |
eee7f4a2 | 1113 | over HTTPS. Can be overridden by the `GIT_SSL_KEY` environment |
1ab661dd PB |
1114 | variable. |
1115 | ||
754ae192 | 1116 | http.sslCertPasswordProtected:: |
2de9b711 | 1117 | Enable Git's password prompt for the SSL certificate. Otherwise |
754ae192 ML |
1118 | OpenSSL will prompt the user, possibly many times, if the |
1119 | certificate or private key is encrypted. Can be overridden by the | |
eee7f4a2 | 1120 | `GIT_SSL_CERT_PASSWORD_PROTECTED` environment variable. |
754ae192 | 1121 | |
1ab661dd PB |
1122 | http.sslCAInfo:: |
1123 | File containing the certificates to verify the peer with when | |
abda1ef5 | 1124 | fetching or pushing over HTTPS. Can be overridden by the |
eee7f4a2 | 1125 | `GIT_SSL_CAINFO` environment variable. |
1ab661dd PB |
1126 | |
1127 | http.sslCAPath:: | |
1128 | Path containing files with the CA certificates to verify the peer | |
37425065 | 1129 | with when fetching or pushing over HTTPS. Can be overridden |
eee7f4a2 | 1130 | by the `GIT_SSL_CAPATH` environment variable. |
1ab661dd | 1131 | |
21084e84 JS |
1132 | http.sslBackend:: |
1133 | Name of the SSL backend to use (e.g. "openssl" or "schannel"). | |
1134 | This option is ignored if cURL lacks support for choosing the SSL | |
1135 | backend at runtime. | |
1136 | ||
93aef7c7 BF |
1137 | http.schannelCheckRevoke:: |
1138 | Used to enforce or disable certificate revocation checks in cURL | |
1139 | when http.sslBackend is set to "schannel". Defaults to `true` if | |
1140 | unset. Only necessary to disable this if Git consistently errors | |
1141 | and the message is about checking the revocation status of a | |
1142 | certificate. This option is ignored if cURL lacks support for | |
1143 | setting the relevant SSL option at runtime. | |
1144 | ||
b67d40ad JS |
1145 | http.schannelUseSSLCAInfo:: |
1146 | As of cURL v7.60.0, the Secure Channel backend can use the | |
1147 | certificate bundle provided via `http.sslCAInfo`, but that would | |
1148 | override the Windows Certificate Store. Since this is not desirable | |
1149 | by default, Git will tell cURL not to use that bundle by default | |
1150 | when the `schannel` backend was configured via `http.sslBackend`, | |
1151 | unless `http.schannelUseSSLCAInfo` overrides this behavior. | |
1152 | ||
aeff8a61 CE |
1153 | http.pinnedpubkey:: |
1154 | Public key of the https service. It may either be the filename of | |
1155 | a PEM or DER encoded public key file or a string starting with | |
1156 | 'sha256//' followed by the base64 encoded sha256 hash of the | |
1157 | public key. See also libcurl 'CURLOPT_PINNEDPUBLICKEY'. git will | |
1158 | exit with an error if this option is set but not supported by | |
1159 | cURL. | |
1160 | ||
4bc444eb MV |
1161 | http.sslTry:: |
1162 | Attempt to use AUTH SSL/TLS and encrypted data transfers | |
1163 | when connecting via regular FTP protocol. This might be needed | |
1164 | if the FTP server requires it for security reasons or you wish | |
1165 | to connect securely whenever remote FTP server supports it. | |
1166 | Default is false since it might trigger certificate verification | |
1167 | errors on misconfigured servers. | |
1168 | ||
1ab661dd | 1169 | http.maxRequests:: |
abda1ef5 | 1170 | How many HTTP requests to launch in parallel. Can be overridden |
eee7f4a2 | 1171 | by the `GIT_HTTP_MAX_REQUESTS` environment variable. Default is 5. |
1ab661dd | 1172 | |
ad75ebe5 TRC |
1173 | http.minSessions:: |
1174 | The number of curl sessions (counted across slots) to be kept across | |
1175 | requests. They will not be ended with curl_easy_cleanup() until | |
1176 | http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this | |
1177 | value will be capped at 1. Defaults to 1. | |
1178 | ||
de1a2fdd SP |
1179 | http.postBuffer:: |
1180 | Maximum size in bytes of the buffer used by smart HTTP | |
1181 | transports when POSTing data to the remote system. | |
1182 | For requests larger than this buffer size, HTTP/1.1 and | |
1183 | Transfer-Encoding: chunked is used to avoid creating a | |
1184 | massive pack file locally. Default is 1 MiB, which is | |
1185 | sufficient for most requests. | |
1186 | ||
1ab661dd PB |
1187 | http.lowSpeedLimit, http.lowSpeedTime:: |
1188 | If the HTTP transfer speed is less than 'http.lowSpeedLimit' | |
1189 | for longer than 'http.lowSpeedTime' seconds, the transfer is aborted. | |
eee7f4a2 TR |
1190 | Can be overridden by the `GIT_HTTP_LOW_SPEED_LIMIT` and |
1191 | `GIT_HTTP_LOW_SPEED_TIME` environment variables. | |
1ab661dd | 1192 | |
3ea099d4 SK |
1193 | http.noEPSV:: |
1194 | A boolean which disables using of EPSV ftp command by curl. | |
befc9c42 | 1195 | This can helpful with some "poor" ftp servers which don't |
eee7f4a2 | 1196 | support EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV` |
3ea099d4 SK |
1197 | environment variable. Default is false (curl will use EPSV). |
1198 | ||
da0005b8 | 1199 | http.userAgent:: |
b1d1058c | 1200 | The HTTP USER_AGENT string presented to an HTTP server. The default |
2de9b711 | 1201 | value represents the version of the client Git such as git/1.7.1. |
b1d1058c SO |
1202 | This option allows you to override this value to a more common value |
1203 | such as Mozilla/4.0. This may be necessary, for instance, if | |
1204 | connecting through a firewall that restricts HTTP connections to a set | |
1205 | of common USER_AGENT strings (but not including those like git/1.7.1). | |
eee7f4a2 | 1206 | Can be overridden by the `GIT_HTTP_USER_AGENT` environment variable. |
b1d1058c | 1207 | |
50d34137 JK |
1208 | http.followRedirects:: |
1209 | Whether git should follow HTTP redirects. If set to `true`, git | |
1210 | will transparently follow any redirect issued by a server it | |
1211 | encounters. If set to `false`, git will treat all redirects as | |
1212 | errors. If set to `initial`, git will follow redirects only for | |
1213 | the initial request to a remote, but not for subsequent | |
1214 | follow-up HTTP requests. Since git uses the redirected URL as | |
1215 | the base for the follow-up requests, this is generally | |
1216 | sufficient. The default is `initial`. | |
1217 | ||
6a56993b | 1218 | http.<url>.*:: |
f745acb0 | 1219 | Any of the http.* options above can be applied selectively to some URLs. |
6a56993b KM |
1220 | For a config key to match a URL, each element of the config key is |
1221 | compared to that of the URL, in the following order: | |
1222 | + | |
1223 | -- | |
1224 | . Scheme (e.g., `https` in `https://example.com/`). This field | |
1225 | must match exactly between the config key and the URL. | |
1226 | ||
1227 | . Host/domain name (e.g., `example.com` in `https://example.com/`). | |
a272b9e7 PS |
1228 | This field must match between the config key and the URL. It is |
1229 | possible to specify a `*` as part of the host name to match all subdomains | |
1230 | at this level. `https://*.example.com/` for example would match | |
1231 | `https://foo.example.com/`, but not `https://foo.bar.example.com/`. | |
6a56993b KM |
1232 | |
1233 | . Port number (e.g., `8080` in `http://example.com:8080/`). | |
1234 | This field must match exactly between the config key and the URL. | |
1235 | Omitted port numbers are automatically converted to the correct | |
1236 | default for the scheme before matching. | |
1237 | ||
1238 | . Path (e.g., `repo.git` in `https://example.com/repo.git`). The | |
1239 | path field of the config key must match the path field of the URL | |
1240 | either exactly or as a prefix of slash-delimited path elements. This means | |
1241 | a config key with path `foo/` matches URL path `foo/bar`. A prefix can only | |
1242 | match on a slash (`/`) boundary. Longer matches take precedence (so a config | |
1243 | key with path `foo/bar` is a better match to URL path `foo/bar` than a config | |
1244 | key with just path `foo/`). | |
1245 | ||
1246 | . User name (e.g., `user` in `https://user@example.com/repo.git`). If | |
1247 | the config key has a user name it must match the user name in the | |
1248 | URL exactly. If the config key does not have a user name, that | |
1249 | config key will match a URL with any user name (including none), | |
1250 | but at a lower precedence than a config key with a user name. | |
1251 | -- | |
1252 | + | |
1253 | The list above is ordered by decreasing precedence; a URL that matches | |
1254 | a config key's path is preferred to one that matches its user name. For example, | |
1255 | if the URL is `https://user@example.com/foo/bar` a config key match of | |
1256 | `https://example.com/foo` will be preferred over a config key match of | |
1257 | `https://user@example.com`. | |
1258 | + | |
1259 | All URLs are normalized before attempting any matching (the password part, | |
1260 | if embedded in the URL, is always ignored for matching purposes) so that | |
f745acb0 TA |
1261 | equivalent URLs that are simply spelled differently will match properly. |
1262 | Environment variable settings always override any matches. The URLs that are | |
6a56993b KM |
1263 | matched against are those given directly to Git commands. This means any URLs |
1264 | visited as a result of a redirection do not participate in matching. | |
1265 | ||
dd33e077 | 1266 | ssh.variant:: |
0da0e49b JN |
1267 | By default, Git determines the command line arguments to use |
1268 | based on the basename of the configured SSH command (configured | |
1269 | using the environment variable `GIT_SSH` or `GIT_SSH_COMMAND` or | |
1270 | the config setting `core.sshCommand`). If the basename is | |
1271 | unrecognized, Git will attempt to detect support of OpenSSH | |
1272 | options by first invoking the configured SSH command with the | |
1273 | `-G` (print configuration) option and will subsequently use | |
1274 | OpenSSH options (if that is successful) or no options besides | |
1275 | the host and remote command (if it fails). | |
1276 | + | |
1277 | The config variable `ssh.variant` can be set to override this detection. | |
1278 | Valid values are `ssh` (to use OpenSSH options), `plink`, `putty`, | |
1279 | `tortoiseplink`, `simple` (no options except the host and remote command). | |
1280 | The default auto-detection can be explicitly requested using the value | |
1281 | `auto`. Any other value is treated as `ssh`. This setting can also be | |
1282 | overridden via the environment variable `GIT_SSH_VARIANT`. | |
94b8ae5a BW |
1283 | + |
1284 | The current command-line parameters used for each variant are as | |
1285 | follows: | |
1286 | + | |
1287 | -- | |
1288 | ||
1289 | * `ssh` - [-p port] [-4] [-6] [-o option] [username@]host command | |
1290 | ||
1291 | * `simple` - [username@]host command | |
1292 | ||
1293 | * `plink` or `putty` - [-P port] [-4] [-6] [username@]host command | |
1294 | ||
1295 | * `tortoiseplink` - [-P port] [-4] [-6] -batch [username@]host command | |
1296 | ||
1297 | -- | |
1298 | + | |
1299 | Except for the `simple` variant, command-line parameters are likely to | |
1300 | change as git gains new features. | |
dd33e077 | 1301 | |
1ab661dd | 1302 | i18n.commitEncoding:: |
2de9b711 | 1303 | Character encoding the commit messages are stored in; Git itself |
1ab661dd PB |
1304 | does not care per se, but this information is necessary e.g. when |
1305 | importing commits from emails or in the gitk graphical history | |
1306 | browser (and possibly at other places in the future or in other | |
5162e697 | 1307 | porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'. |
1ab661dd | 1308 | |
d2c11a38 JH |
1309 | i18n.logOutputEncoding:: |
1310 | Character encoding the commit messages are converted to when | |
0b444cdb | 1311 | running 'git log' and friends. |
d2c11a38 | 1312 | |
b0f34c3d MM |
1313 | imap:: |
1314 | The configuration variables in the 'imap' section are described | |
1315 | in linkgit:git-imap-send[1]. | |
1316 | ||
c780b9cf BP |
1317 | index.threads:: |
1318 | Specifies the number of threads to spawn when loading the index. | |
1319 | This is meant to reduce index load time on multiprocessor machines. | |
1320 | Specifying 0 or 'true' will cause Git to auto-detect the number of | |
1321 | CPU's and set the number of threads accordingly. Specifying 1 or | |
1322 | 'false' will disable multithreading. Defaults to 'true'. | |
1323 | ||
3c09d684 TG |
1324 | index.version:: |
1325 | Specify the version with which new index files should be | |
1326 | initialized. This does not affect existing repositories. | |
1327 | ||
da0005b8 | 1328 | init.templateDir:: |
d8a8488d SD |
1329 | Specify the directory from which templates will be copied. |
1330 | (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].) | |
1331 | ||
983a9eeb CC |
1332 | instaweb.browser:: |
1333 | Specify the program that will be used to browse your working | |
1334 | repository in gitweb. See linkgit:git-instaweb[1]. | |
1335 | ||
1336 | instaweb.httpd:: | |
1337 | The HTTP daemon command-line to start gitweb on your working | |
1338 | repository. See linkgit:git-instaweb[1]. | |
1339 | ||
1340 | instaweb.local:: | |
1341 | If true the web server started by linkgit:git-instaweb[1] will | |
1342 | be bound to the local IP (127.0.0.1). | |
1343 | ||
da0005b8 | 1344 | instaweb.modulePath:: |
6b677a28 VS |
1345 | The default module path for linkgit:git-instaweb[1] to use |
1346 | instead of /usr/lib/apache2/modules. Only used if httpd | |
1347 | is Apache. | |
983a9eeb CC |
1348 | |
1349 | instaweb.port:: | |
1350 | The port number to bind the gitweb httpd to. See | |
1351 | linkgit:git-instaweb[1]. | |
1352 | ||
da0005b8 | 1353 | interactive.singleKey:: |
57f6ec02 | 1354 | In interactive commands, allow the user to provide one-letter |
ca6ac7f1 | 1355 | input with a single key (i.e., without hitting enter). |
6cf378f0 | 1356 | Currently this is used by the `--patch` mode of |
e6b57a8a CI |
1357 | linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1], |
1358 | linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this | |
1359 | setting is silently ignored if portable keystroke input | |
8358f1ac | 1360 | is not available; requires the Perl module Term::ReadKey. |
ca6ac7f1 | 1361 | |
01143847 JK |
1362 | interactive.diffFilter:: |
1363 | When an interactive command (such as `git add --patch`) shows | |
1364 | a colorized diff, git will pipe the diff through the shell | |
1365 | command defined by this configuration variable. The command may | |
1366 | mark up the diff further for human consumption, provided that it | |
1367 | retains a one-to-one correspondence with the lines in the | |
1368 | original diff. Defaults to disabled (no filtering). | |
1369 | ||
0c47695a JS |
1370 | log.abbrevCommit:: |
1371 | If true, makes linkgit:git-log[1], linkgit:git-show[1], and | |
6cf378f0 JK |
1372 | linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may |
1373 | override this option with `--no-abbrev-commit`. | |
0c47695a | 1374 | |
dd0ffd5b | 1375 | log.date:: |
e860795d JN |
1376 | Set the default date-time mode for the 'log' command. |
1377 | Setting a value for log.date is similar to using 'git log''s | |
78a84416 | 1378 | `--date` option. See linkgit:git-log[1] for details. |
dd0ffd5b | 1379 | |
eb734454 SD |
1380 | log.decorate:: |
1381 | Print out the ref names of any commits that are shown by the log | |
1382 | command. If 'short' is specified, the ref name prefixes 'refs/heads/', | |
1383 | 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is | |
1384 | specified, the full ref name (including prefix) will be printed. | |
462cbb41 RJ |
1385 | If 'auto' is specified, then if the output is going to a terminal, |
1386 | the ref names are shown as if 'short' were given, otherwise no ref | |
ce18123c | 1387 | names are shown. This is the same as the `--decorate` option |
462cbb41 | 1388 | of the `git log`. |
eb734454 | 1389 | |
fd8d07ef EVW |
1390 | log.follow:: |
1391 | If `true`, `git log` will act as if the `--follow` option was used when | |
1392 | a single <path> is given. This has the same limitations as `--follow`, | |
1393 | i.e. it cannot be used to follow multiple files and does not work well | |
1394 | on non-linear history. | |
1395 | ||
73c727d6 NTND |
1396 | log.graphColors:: |
1397 | A list of colors, separated by commas, that can be used to draw | |
1398 | history lines in `git log --graph`. | |
1399 | ||
da0005b8 | 1400 | log.showRoot:: |
0f03ca94 PB |
1401 | If true, the initial commit will be shown as a big creation event. |
1402 | This is equivalent to a diff against an empty tree. | |
5162e697 | 1403 | Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which |
0f03ca94 PB |
1404 | normally hide the root commit will now show it. True by default. |
1405 | ||
ba4dce78 KM |
1406 | log.showSignature:: |
1407 | If true, makes linkgit:git-log[1], linkgit:git-show[1], and | |
1408 | linkgit:git-whatchanged[1] assume `--show-signature`. | |
1409 | ||
e6bb5f78 AP |
1410 | log.mailmap:: |
1411 | If true, makes linkgit:git-log[1], linkgit:git-show[1], and | |
1412 | linkgit:git-whatchanged[1] assume `--use-mailmap`. | |
1413 | ||
d5c4b185 MM |
1414 | mailinfo.scissors:: |
1415 | If true, makes linkgit:git-mailinfo[1] (and therefore | |
1416 | linkgit:git-am[1]) act by default as if the --scissors option | |
1417 | was provided on the command-line. When active, this features | |
1418 | removes everything from the message body before a scissors | |
1419 | line (i.e. consisting mainly of ">8", "8<" and "-"). | |
1420 | ||
d551a488 MSO |
1421 | mailmap.file:: |
1422 | The location of an augmenting mailmap file. The default | |
1423 | mailmap, located in the root of the repository, is loaded | |
1424 | first, then the mailmap file pointed to by this variable. | |
1425 | The location of the mailmap file may be in a repository | |
1426 | subdirectory, or somewhere outside of the repository itself. | |
1427 | See linkgit:git-shortlog[1] and linkgit:git-blame[1]. | |
1428 | ||
08610900 JK |
1429 | mailmap.blob:: |
1430 | Like `mailmap.file`, but consider the value as a reference to a | |
8c473cec JK |
1431 | blob in the repository. If both `mailmap.file` and |
1432 | `mailmap.blob` are given, both are parsed, with entries from | |
1433 | `mailmap.file` taking precedence. In a bare repository, this | |
1434 | defaults to `HEAD:.mailmap`. In a non-bare repository, it | |
1435 | defaults to empty. | |
08610900 | 1436 | |
b5578f33 | 1437 | man.viewer:: |
b8322ea8 | 1438 | Specify the programs that may be used to display help in the |
b5578f33 CC |
1439 | 'man' format. See linkgit:git-help[1]. |
1440 | ||
0bb64009 CC |
1441 | man.<tool>.cmd:: |
1442 | Specify the command to invoke the specified man viewer. The | |
1443 | specified command is evaluated in shell with the man page | |
1444 | passed as argument. (See linkgit:git-help[1].) | |
1445 | ||
7e8114c0 CC |
1446 | man.<tool>.path:: |
1447 | Override the path for the given tool that may be used to | |
1448 | display help in the 'man' format. See linkgit:git-help[1]. | |
1449 | ||
b0f34c3d | 1450 | include::merge-config.txt[] |
b5412484 | 1451 | |
77680caa JS |
1452 | mergetool.<tool>.path:: |
1453 | Override the path for the given tool. This is useful in case | |
1454 | your tool is not in the PATH. | |
1455 | ||
964473a0 CB |
1456 | mergetool.<tool>.cmd:: |
1457 | Specify the command to invoke the specified merge tool. The | |
1458 | specified command is evaluated in shell with the following | |
1459 | variables available: 'BASE' is the name of a temporary file | |
1460 | containing the common base of the files to be merged, if available; | |
1461 | 'LOCAL' is the name of a temporary file containing the contents of | |
1462 | the file on the current branch; 'REMOTE' is the name of a temporary | |
1463 | file containing the contents of the file from the branch being | |
1464 | merged; 'MERGED' contains the name of the file to which the merge | |
1465 | tool should write the results of a successful merge. | |
1466 | ||
1467 | mergetool.<tool>.trustExitCode:: | |
1468 | For a custom merge command, specify whether the exit code of | |
1469 | the merge command can be used to determine whether the merge was | |
1470 | successful. If this is not set to true then the merge target file | |
1471 | timestamp is checked and the merge assumed to have been successful | |
1472 | if the file has been updated, otherwise the user is prompted to | |
1473 | indicate the success of the merge. | |
1474 | ||
b12d0450 DA |
1475 | mergetool.meld.hasOutput:: |
1476 | Older versions of `meld` do not support the `--output` option. | |
1477 | Git will attempt to detect whether `meld` supports `--output` | |
1478 | by inspecting the output of `meld --help`. Configuring | |
1479 | `mergetool.meld.hasOutput` will make Git skip these checks and | |
1480 | use the configured value instead. Setting `mergetool.meld.hasOutput` | |
1481 | to `true` tells Git to unconditionally use the `--output` option, | |
1482 | and `false` avoids using `--output`. | |
1483 | ||
44c36d1c CB |
1484 | mergetool.keepBackup:: |
1485 | After performing a merge, the original file with conflict markers | |
1486 | can be saved as a file with a `.orig` extension. If this variable | |
1487 | is set to `false` then this file is not preserved. Defaults to | |
1488 | `true` (i.e. keep the backup files). | |
1489 | ||
162eba8b | 1490 | mergetool.keepTemporaries:: |
2de9b711 | 1491 | When invoking a custom merge tool, Git uses a set of temporary |
162eba8b CB |
1492 | files to pass to the tool. If the tool returns an error and this |
1493 | variable is set to `true`, then these temporary files will be | |
1494 | preserved, otherwise they will be removed after the tool has | |
1495 | exited. Defaults to `false`. | |
1496 | ||
8f0cb41d DA |
1497 | mergetool.writeToTemp:: |
1498 | Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of | |
1499 | conflicting files in the worktree by default. Git will attempt | |
1500 | to use a temporary directory for these files when set `true`. | |
1501 | Defaults to `false`. | |
1502 | ||
682b451f CB |
1503 | mergetool.prompt:: |
1504 | Prompt before each invocation of the merge resolution program. | |
1505 | ||
d2d68d99 JK |
1506 | notes.mergeStrategy:: |
1507 | Which merge strategy to choose by default when resolving notes | |
1508 | conflicts. Must be one of `manual`, `ours`, `theirs`, `union`, or | |
1509 | `cat_sort_uniq`. Defaults to `manual`. See "NOTES MERGE STRATEGIES" | |
1510 | section of linkgit:git-notes[1] for more information on each strategy. | |
1511 | ||
4f655e22 JK |
1512 | notes.<name>.mergeStrategy:: |
1513 | Which merge strategy to choose when doing a notes merge into | |
1514 | refs/notes/<name>. This overrides the more general | |
1515 | "notes.mergeStrategy". See the "NOTES MERGE STRATEGIES" section in | |
1516 | linkgit:git-notes[1] for more information on the available strategies. | |
1517 | ||
894a9d33 TR |
1518 | notes.displayRef:: |
1519 | The (fully qualified) refname from which to show notes when | |
1520 | showing commit messages. The value of this variable can be set | |
1521 | to a glob, in which case notes from all matching refs will be | |
1522 | shown. You may also specify this configuration variable | |
1523 | several times. A warning will be issued for refs that do not | |
1524 | exist, but a glob that does not match any refs is silently | |
1525 | ignored. | |
1526 | + | |
1527 | This setting can be overridden with the `GIT_NOTES_DISPLAY_REF` | |
1528 | environment variable, which must be a colon separated list of refs or | |
1529 | globs. | |
1530 | + | |
1531 | The effective value of "core.notesRef" (possibly overridden by | |
1532 | GIT_NOTES_REF) is also implicitly added to the list of refs to be | |
1533 | displayed. | |
1534 | ||
6956f858 TR |
1535 | notes.rewrite.<command>:: |
1536 | When rewriting commits with <command> (currently `amend` or | |
2de9b711 | 1537 | `rebase`) and this variable is set to `true`, Git |
6956f858 TR |
1538 | automatically copies your notes from the original to the |
1539 | rewritten commit. Defaults to `true`, but see | |
1540 | "notes.rewriteRef" below. | |
6956f858 TR |
1541 | |
1542 | notes.rewriteMode:: | |
1543 | When copying notes during a rewrite (see the | |
1544 | "notes.rewrite.<command>" option), determines what to do if | |
1545 | the target commit already has a note. Must be one of | |
e48ad1b9 JK |
1546 | `overwrite`, `concatenate`, `cat_sort_uniq`, or `ignore`. |
1547 | Defaults to `concatenate`. | |
6956f858 TR |
1548 | + |
1549 | This setting can be overridden with the `GIT_NOTES_REWRITE_MODE` | |
1550 | environment variable. | |
1551 | ||
1552 | notes.rewriteRef:: | |
1553 | When copying notes during a rewrite, specifies the (fully | |
1554 | qualified) ref whose notes should be copied. The ref may be a | |
1555 | glob, in which case notes in all matching refs will be copied. | |
1556 | You may also specify this configuration several times. | |
1557 | + | |
1558 | Does not have a default value; you must configure this variable to | |
2b4aa89c TR |
1559 | enable note rewriting. Set it to `refs/notes/commits` to enable |
1560 | rewriting for the default commit notes. | |
cfb88e9a LAS |
1561 | + |
1562 | This setting can be overridden with the `GIT_NOTES_REWRITE_REF` | |
1563 | environment variable, which must be a colon separated list of refs or | |
1564 | globs. | |
6956f858 | 1565 | |
4812a93a | 1566 | pack.window:: |
5162e697 | 1567 | The size of the window used by linkgit:git-pack-objects[1] when no |
4812a93a JK |
1568 | window size is given on the command line. Defaults to 10. |
1569 | ||
842aaf93 | 1570 | pack.depth:: |
5162e697 | 1571 | The maximum delta depth used by linkgit:git-pack-objects[1] when no |
618e613a | 1572 | maximum depth is given on the command line. Defaults to 50. |
b5c0cbd8 | 1573 | Maximum value is 4095. |
842aaf93 | 1574 | |
e93b15cd | 1575 | pack.windowMemory:: |
f4694a8c RB |
1576 | The maximum size of memory that is consumed by each thread |
1577 | in linkgit:git-pack-objects[1] for pack window memory when | |
1578 | no limit is given on the command line. The value can be | |
1579 | suffixed with "k", "m", or "g". When left unconfigured (or | |
1580 | set explicitly to 0), there will be no limit. | |
e93b15cd | 1581 | |
960ccca6 DH |
1582 | pack.compression:: |
1583 | An integer -1..9, indicating the compression level for objects | |
1584 | in a pack file. -1 is the zlib default. 0 means no | |
1585 | compression, and 1..9 are various speed/size tradeoffs, 9 being | |
1586 | slowest. If not set, defaults to core.compression. If that is | |
dec92309 BD |
1587 | not set, defaults to -1, the zlib default, which is "a default |
1588 | compromise between speed and compression (currently equivalent | |
1589 | to level 6)." | |
89d71f75 JK |
1590 | + |
1591 | Note that changing the compression level will not automatically recompress | |
1592 | all existing objects. You can force recompression by passing the -F option | |
1593 | to linkgit:git-repack[1]. | |
960ccca6 | 1594 | |
28b8a730 JK |
1595 | pack.island:: |
1596 | An extended regular expression configuring a set of delta | |
1597 | islands. See "DELTA ISLANDS" in linkgit:git-pack-objects[1] | |
1598 | for details. | |
1599 | ||
1600 | pack.islandCore:: | |
1601 | Specify an island name which gets to have its objects be | |
1602 | packed first. This creates a kind of pseudo-pack at the front | |
1603 | of one pack, so that the objects from the specified island are | |
1604 | hopefully faster to copy into any pack that should be served | |
1605 | to a user requesting these objects. In practice this means | |
1606 | that the island specified should likely correspond to what is | |
1607 | the most commonly cloned in the repo. See also "DELTA ISLANDS" | |
1608 | in linkgit:git-pack-objects[1]. | |
1609 | ||
074b2eea | 1610 | pack.deltaCacheSize:: |
02783075 | 1611 | The maximum memory in bytes used for caching deltas in |
5749b0b2 NP |
1612 | linkgit:git-pack-objects[1] before writing them out to a pack. |
1613 | This cache is used to speed up the writing object phase by not | |
1614 | having to recompute the final delta result once the best match | |
1615 | for all objects is found. Repacking large repositories on machines | |
1616 | which are tight with memory might be badly impacted by this though, | |
1617 | especially if this cache pushes the system into swapping. | |
1618 | A value of 0 means no limit. The smallest size of 1 byte may be | |
1619 | used to virtually disable this cache. Defaults to 256 MiB. | |
074b2eea | 1620 | |
e3dfddb3 | 1621 | pack.deltaCacheLimit:: |
693b86ff | 1622 | The maximum size of a delta, that is cached in |
5749b0b2 NP |
1623 | linkgit:git-pack-objects[1]. This cache is used to speed up the |
1624 | writing object phase by not having to recompute the final delta | |
0cb3c142 NTND |
1625 | result once the best match for all objects is found. |
1626 | Defaults to 1000. Maximum value is 65535. | |
e3dfddb3 | 1627 | |
693b86ff NP |
1628 | pack.threads:: |
1629 | Specifies the number of threads to spawn when searching for best | |
5162e697 | 1630 | delta matches. This requires that linkgit:git-pack-objects[1] |
693b86ff NP |
1631 | be compiled with pthreads otherwise this option is ignored with a |
1632 | warning. This is meant to reduce packing time on multiprocessor | |
1633 | machines. The required amount of memory for the delta search window | |
1634 | is however multiplied by the number of threads. | |
2de9b711 | 1635 | Specifying 0 will cause Git to auto-detect the number of CPU's |
833e3df1 | 1636 | and set the number of threads accordingly. |
693b86ff | 1637 | |
4d00bda2 NP |
1638 | pack.indexVersion:: |
1639 | Specify the default pack index version. Valid values are 1 for | |
1640 | legacy pack index used by Git versions prior to 1.5.2, and 2 for | |
1641 | the new pack index with capabilities for packs larger than 4 GB | |
1642 | as well as proper protection against the repacking of corrupted | |
c0a5e2d4 NP |
1643 | packs. Version 2 is the default. Note that version 2 is enforced |
1644 | and this config option ignored whenever the corresponding pack is | |
1645 | larger than 2 GB. | |
1646 | + | |
2de9b711 | 1647 | If you have an old Git that does not understand the version 2 `*.idx` file, |
0d0bac67 | 1648 | cloning or fetching over a non native protocol (e.g. "http") |
6cf378f0 | 1649 | that will copy both `*.pack` file and corresponding `*.idx` file from the |
c0a5e2d4 | 1650 | other side may give you a repository that cannot be accessed with your |
2de9b711 | 1651 | older version of Git. If the `*.pack` file is smaller than 2 GB, however, |
c0a5e2d4 | 1652 | you can use linkgit:git-index-pack[1] on the *.pack file to regenerate |
6cf378f0 | 1653 | the `*.idx` file. |
4d00bda2 | 1654 | |
dbdbfec4 | 1655 | pack.packSizeLimit:: |
07cf0f24 NP |
1656 | The maximum size of a pack. This setting only affects |
1657 | packing to a file when repacking, i.e. the git:// protocol | |
6cf378f0 | 1658 | is unaffected. It can be overridden by the `--max-pack-size` |
9cea46cd EW |
1659 | option of linkgit:git-repack[1]. Reaching this limit results |
1660 | in the creation of multiple packfiles; which in turn prevents | |
1661 | bitmaps from being created. | |
1662 | The minimum size allowed is limited to 1 MiB. | |
1663 | The default is unlimited. | |
07cf0f24 NP |
1664 | Common unit suffixes of 'k', 'm', or 'g' are |
1665 | supported. | |
2b84b5a8 | 1666 | |
6b8fda2d VM |
1667 | pack.useBitmaps:: |
1668 | When true, git will use pack bitmaps (if available) when packing | |
1669 | to stdout (e.g., during the server side of a fetch). Defaults to | |
1670 | true. You should not generally need to turn this off unless | |
1671 | you are debugging pack bitmaps. | |
1672 | ||
da0005b8 | 1673 | pack.writeBitmaps (deprecated):: |
71d76cb4 | 1674 | This is a deprecated synonym for `repack.writeBitmaps`. |
7cc8f971 | 1675 | |
ae4f07fb VM |
1676 | pack.writeBitmapHashCache:: |
1677 | When true, git will include a "hash cache" section in the bitmap | |
1678 | index (if one is written). This cache can be used to feed git's | |
1679 | delta heuristics, potentially leading to better deltas between | |
1680 | bitmapped and non-bitmapped objects (e.g., when serving a fetch | |
1681 | between an older, bitmapped pack and objects that have been | |
1682 | pushed since the last gc). The downside is that it consumes 4 | |
1683 | bytes per object of disk space, and that JGit's bitmap | |
1684 | implementation does not understand it, causing it to complain if | |
1685 | Git and JGit are used on the same repository. Defaults to false. | |
1686 | ||
4370c2d6 | 1687 | pager.<cmd>:: |
9bad7233 | 1688 | If the value is boolean, turns on or off pagination of the |
2de9b711 | 1689 | output of a particular Git subcommand when writing to a tty. |
9bad7233 | 1690 | Otherwise, turns on pagination for the subcommand using the |
6cf378f0 JK |
1691 | pager specified by the value of `pager.<cmd>`. If `--paginate` |
1692 | or `--no-pager` is specified on the command line, it takes | |
9bad7233 JK |
1693 | precedence over this option. To disable pagination for all |
1694 | commands, set `core.pager` or `GIT_PAGER` to `cat`. | |
4370c2d6 | 1695 | |
8028184e WP |
1696 | pretty.<name>:: |
1697 | Alias for a --pretty= format string, as specified in | |
1698 | linkgit:git-log[1]. Any aliases defined here can be used just | |
1699 | as the built-in pretty formats could. For example, | |
6cf378f0 | 1700 | running `git config pretty.changelog "format:* %H %s"` |
8028184e | 1701 | would cause the invocation `git log --pretty=changelog` |
6cf378f0 | 1702 | to be equivalent to running `git log "--pretty=format:* %H %s"`. |
8028184e WP |
1703 | Note that an alias with the same name as a built-in format |
1704 | will be silently ignored. | |
1705 | ||
f1762d77 BW |
1706 | protocol.allow:: |
1707 | If set, provide a user defined default policy for all protocols which | |
1708 | don't explicitly have a policy (`protocol.<name>.allow`). By default, | |
1709 | if unset, known-safe protocols (http, https, git, ssh, file) have a | |
1710 | default policy of `always`, known-dangerous protocols (ext) have a | |
1711 | default policy of `never`, and all other protocols have a default | |
1712 | policy of `user`. Supported policies: | |
1713 | + | |
1714 | -- | |
1715 | ||
1716 | * `always` - protocol is always able to be used. | |
1717 | ||
1718 | * `never` - protocol is never able to be used. | |
1719 | ||
1720 | * `user` - protocol is only able to be used when `GIT_PROTOCOL_FROM_USER` is | |
1721 | either unset or has a value of 1. This policy should be used when you want a | |
1722 | protocol to be directly usable by the user but don't want it used by commands which | |
1723 | execute clone/fetch/push commands without user input, e.g. recursive | |
1724 | submodule initialization. | |
1725 | ||
1726 | -- | |
1727 | ||
1728 | protocol.<name>.allow:: | |
1729 | Set a policy to be used by protocol `<name>` with clone/fetch/push | |
1730 | commands. See `protocol.allow` above for the available policies. | |
1731 | + | |
1732 | The protocol names currently used by git are: | |
1733 | + | |
1734 | -- | |
1735 | - `file`: any local file-based path (including `file://` URLs, | |
1736 | or local paths) | |
1737 | ||
1738 | - `git`: the anonymous git protocol over a direct TCP | |
1739 | connection (or proxy, if configured) | |
1740 | ||
1741 | - `ssh`: git over ssh (including `host:path` syntax, | |
1742 | `ssh://`, etc). | |
1743 | ||
1744 | - `http`: git over http, both "smart http" and "dumb http". | |
1745 | Note that this does _not_ include `https`; if you want to configure | |
1746 | both, you must do so individually. | |
1747 | ||
1748 | - any external helpers are named by their protocol (e.g., use | |
1749 | `hg` to allow the `git-remote-hg` helper) | |
1750 | -- | |
1751 | ||
373d70ef BW |
1752 | protocol.version:: |
1753 | Experimental. If set, clients will attempt to communicate with a | |
1754 | server using the specified protocol version. If unset, no | |
1755 | attempt will be made by the client to communicate using a | |
1756 | particular protocol version, this results in protocol version 0 | |
1757 | being used. | |
1758 | Supported versions: | |
1759 | + | |
1760 | -- | |
1761 | ||
1762 | * `0` - the original wire protocol. | |
1763 | ||
1764 | * `1` - the original wire protocol with the addition of a version string | |
1765 | in the initial response from the server. | |
1766 | ||
db2d36fa BW |
1767 | * `2` - link:technical/protocol-v2.html[wire protocol version 2]. |
1768 | ||
373d70ef BW |
1769 | -- |
1770 | ||
04750299 | 1771 | include::pull-config.txt[] |
d8052750 | 1772 | |
41b651d6 | 1773 | include::push-config.txt[] |
b33a15b0 | 1774 | |
946a9f20 | 1775 | include::rebase-config.txt[] |
16cf51c7 | 1776 | |
aaa3b458 | 1777 | include::receive-config.txt[] |
0a1bc12b | 1778 | |
da0005b8 | 1779 | remote.pushDefault:: |
224c2171 | 1780 | The remote to push to by default. Overrides |
9f765ce6 | 1781 | `branch.<name>.remote` for all branches, and is overridden by |
da0005b8 | 1782 | `branch.<name>.pushRemote` for specific branches. |
224c2171 | 1783 | |
0cc6d346 | 1784 | remote.<name>.url:: |
5162e697 DM |
1785 | The URL of a remote repository. See linkgit:git-fetch[1] or |
1786 | linkgit:git-push[1]. | |
0cc6d346 | 1787 | |
20346234 MG |
1788 | remote.<name>.pushurl:: |
1789 | The push URL of a remote repository. See linkgit:git-push[1]. | |
1790 | ||
14c98218 SV |
1791 | remote.<name>.proxy:: |
1792 | For remotes that require curl (http, https and ftp), the URL to | |
1793 | the proxy to use for that remote. Set to the empty string to | |
1794 | disable proxying for that remote. | |
1795 | ||
ef976395 KF |
1796 | remote.<name>.proxyAuthMethod:: |
1797 | For remotes that require curl (http, https and ftp), the method to use for | |
1798 | authenticating against the proxy in use (probably set in | |
1799 | `remote.<name>.proxy`). See `http.proxyAuthMethod`. | |
1800 | ||
0cc6d346 | 1801 | remote.<name>.fetch:: |
5162e697 DM |
1802 | The default set of "refspec" for linkgit:git-fetch[1]. See |
1803 | linkgit:git-fetch[1]. | |
0cc6d346 SB |
1804 | |
1805 | remote.<name>.push:: | |
5162e697 DM |
1806 | The default set of "refspec" for linkgit:git-push[1]. See |
1807 | linkgit:git-push[1]. | |
0cc6d346 | 1808 | |
84bb2dfd PB |
1809 | remote.<name>.mirror:: |
1810 | If true, pushing to this remote will automatically behave | |
6cf378f0 | 1811 | as if the `--mirror` option was given on the command line. |
84bb2dfd | 1812 | |
1918278e TT |
1813 | remote.<name>.skipDefaultUpdate:: |
1814 | If true, this remote will be skipped by default when updating | |
7cc91a2f BG |
1815 | using linkgit:git-fetch[1] or the `update` subcommand of |
1816 | linkgit:git-remote[1]. | |
1817 | ||
1818 | remote.<name>.skipFetchAll:: | |
1819 | If true, this remote will be skipped by default when updating | |
1820 | using linkgit:git-fetch[1] or the `update` subcommand of | |
1821 | linkgit:git-remote[1]. | |
1918278e | 1822 | |
060aafc1 | 1823 | remote.<name>.receivepack:: |
5dee29ac | 1824 | The default program to execute on the remote side when pushing. See |
1c262bb7 | 1825 | option --receive-pack of linkgit:git-push[1]. |
060aafc1 | 1826 | |
5dee29ac UKK |
1827 | remote.<name>.uploadpack:: |
1828 | The default program to execute on the remote side when fetching. See | |
1c262bb7 | 1829 | option --upload-pack of linkgit:git-fetch-pack[1]. |
5dee29ac | 1830 | |
da0005b8 | 1831 | remote.<name>.tagOpt:: |
1c262bb7 JK |
1832 | Setting this value to --no-tags disables automatic tag following when |
1833 | fetching from remote <name>. Setting it to --tags will fetch every | |
944163a4 | 1834 | tag from remote <name>, even if they are not reachable from remote |
ed368546 | 1835 | branch heads. Passing these flags directly to linkgit:git-fetch[1] can |
1c262bb7 | 1836 | override this setting. See options --tags and --no-tags of |
ed368546 | 1837 | linkgit:git-fetch[1]. |
047f636d | 1838 | |
c578f51d | 1839 | remote.<name>.vcs:: |
2de9b711 | 1840 | Setting this to a value <vcs> will cause Git to interact with |
c578f51d DB |
1841 | the remote with the git-remote-<vcs> helper. |
1842 | ||
737c5a9c MS |
1843 | remote.<name>.prune:: |
1844 | When set to true, fetching from this remote by default will also | |
0838bf47 MH |
1845 | remove any remote-tracking references that no longer exist on the |
1846 | remote (as if the `--prune` option was given on the command line). | |
737c5a9c MS |
1847 | Overrides `fetch.prune` settings, if any. |
1848 | ||
97716d21 ÆAB |
1849 | remote.<name>.pruneTags:: |
1850 | When set to true, fetching from this remote by default will also | |
1851 | remove any local tags that no longer exist on the remote if pruning | |
1852 | is activated in general via `remote.<name>.prune`, `fetch.prune` or | |
1853 | `--prune`. Overrides `fetch.pruneTags` settings, if any. | |
627a129b ÆAB |
1854 | + |
1855 | See also `remote.<name>.prune` and the PRUNING section of | |
1856 | linkgit:git-fetch[1]. | |
737c5a9c | 1857 | |
1918278e TT |
1858 | remotes.<group>:: |
1859 | The list of remotes which are fetched by "git remote update | |
5162e697 | 1860 | <group>". See linkgit:git-remote[1]. |
1918278e | 1861 | |
da0005b8 | 1862 | repack.useDeltaBaseOffset:: |
22c79eab NP |
1863 | By default, linkgit:git-repack[1] creates packs that use |
1864 | delta-base offset. If you need to share your repository with | |
2de9b711 | 1865 | Git older than version 1.4.4, either directly or via a dumb |
22c79eab | 1866 | protocol such as http, then you need to set this option to |
2de9b711 | 1867 | "false" and repack. Access from old Git versions over the |
22c79eab | 1868 | native protocol are unaffected by this option. |
b6945f57 | 1869 | |
ee34a2be JK |
1870 | repack.packKeptObjects:: |
1871 | If set to true, makes `git repack` act as if | |
1872 | `--pack-kept-objects` was passed. See linkgit:git-repack[1] for | |
1873 | details. Defaults to `false` normally, but `true` if a bitmap | |
1874 | index is being written (either via `--write-bitmap-index` or | |
71d76cb4 JK |
1875 | `repack.writeBitmaps`). |
1876 | ||
16d75fa4 JK |
1877 | repack.useDeltaIslands:: |
1878 | If set to true, makes `git repack` act as if `--delta-islands` | |
1879 | was passed. Defaults to `false`. | |
1880 | ||
71d76cb4 JK |
1881 | repack.writeBitmaps:: |
1882 | When true, git will write a bitmap index when packing all | |
1883 | objects to disk (e.g., when `git repack -a` is run). This | |
1884 | index can speed up the "counting objects" phase of subsequent | |
1885 | packs created for clones and fetches, at the cost of some disk | |
9cea46cd EW |
1886 | space and extra time spent on the initial repack. This has |
1887 | no effect if multiple packfiles are created. | |
1888 | Defaults to false. | |
ee34a2be | 1889 | |
da0005b8 | 1890 | rerere.autoUpdate:: |
b0f34c3d MM |
1891 | When set to true, `git-rerere` updates the index with the |
1892 | resulting contents after it cleanly resolves conflicts using | |
1893 | previously recorded resolution. Defaults to false. | |
1894 | ||
1895 | rerere.enabled:: | |
1896 | Activate recording of resolved conflicts, so that identical | |
07b88a00 TR |
1897 | conflict hunks can be resolved automatically, should they be |
1898 | encountered again. By default, linkgit:git-rerere[1] is | |
1899 | enabled if there is an `rr-cache` directory under the | |
b6fb7fed JH |
1900 | `$GIT_DIR`, e.g. if "rerere" was previously used in the |
1901 | repository. | |
b0f34c3d | 1902 | |
4c3abd05 BP |
1903 | reset.quiet:: |
1904 | When set to true, 'git reset' will default to the '--quiet' option. | |
1905 | ||
701137ee | 1906 | include::sendemail-config.txt[] |
5453b83b | 1907 | |
8dc9d22d NTND |
1908 | sequence.editor:: |
1909 | Text editor used by `git rebase -i` for editing the rebase instruction file. | |
1910 | The value is meant to be interpreted by the shell when it is used. | |
1911 | It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. | |
1912 | When not configured the default commit message editor is used instead. | |
1913 | ||
8da2f489 | 1914 | showBranch.default:: |
5162e697 DM |
1915 | The default set of branches for linkgit:git-show-branch[1]. |
1916 | See linkgit:git-show-branch[1]. | |
1ab661dd | 1917 | |
e77cf4ee CC |
1918 | splitIndex.maxPercentChange:: |
1919 | When the split index feature is used, this specifies the | |
1920 | percent of entries the split index can contain compared to the | |
1921 | total number of entries in both the split index and the shared | |
1922 | index before a new shared index is written. | |
1923 | The value should be between 0 and 100. If the value is 0 then | |
1924 | a new shared index is always written, if it is 100 a new | |
1925 | shared index is never written. | |
1926 | By default the value is 20, so a new shared index is written | |
1927 | if the number of entries in the split index would be greater | |
1928 | than 20 percent of the total number of entries. | |
1929 | See linkgit:git-update-index[1]. | |
1930 | ||
b2dd1c5c CC |
1931 | splitIndex.sharedIndexExpire:: |
1932 | When the split index feature is used, shared index files that | |
1933 | were not modified since the time this variable specifies will | |
1934 | be removed when a new shared index file is created. The value | |
1935 | "now" expires all entries immediately, and "never" suppresses | |
1936 | expiration altogether. | |
1937 | The default value is "2.weeks.ago". | |
1938 | Note that a shared index file is considered modified (for the | |
1939 | purpose of expiration) each time a new split-index file is | |
b4601395 | 1940 | either created based on it or read from it. |
b2dd1c5c CC |
1941 | See linkgit:git-update-index[1]. |
1942 | ||
46f721c8 | 1943 | status.relativePaths:: |
5162e697 | 1944 | By default, linkgit:git-status[1] shows paths relative to the |
46f721c8 | 1945 | current directory. Setting this variable to `false` shows paths |
2de9b711 | 1946 | relative to the repository root (this was the default for Git |
46f721c8 JK |
1947 | prior to v1.5.4). |
1948 | ||
4fb5166a JJGG |
1949 | status.short:: |
1950 | Set to true to enable --short by default in linkgit:git-status[1]. | |
1951 | The option --no-short takes precedence over this variable. | |
1952 | ||
ec85d070 JJGG |
1953 | status.branch:: |
1954 | Set to true to enable --branch by default in linkgit:git-status[1]. | |
1955 | The option --no-branch takes precedence over this variable. | |
1956 | ||
2556b996 MM |
1957 | status.displayCommentPrefix:: |
1958 | If set to true, linkgit:git-status[1] will insert a comment | |
1959 | prefix before each output line (starting with | |
1960 | `core.commentChar`, i.e. `#` by default). This was the | |
1961 | behavior of linkgit:git-status[1] in Git 1.8.4 and previous. | |
1962 | Defaults to false. | |
1963 | ||
e8b2dc2c BP |
1964 | status.renameLimit:: |
1965 | The number of files to consider when performing rename detection | |
1966 | in linkgit:git-status[1] and linkgit:git-commit[1]. Defaults to | |
1967 | the value of diff.renameLimit. | |
1968 | ||
1969 | status.renames:: | |
1970 | Whether and how Git detects renames in linkgit:git-status[1] and | |
1971 | linkgit:git-commit[1] . If set to "false", rename detection is | |
1972 | disabled. If set to "true", basic rename detection is enabled. | |
1973 | If set to "copies" or "copy", Git will detect copies, as well. | |
1974 | Defaults to the value of diff.renames. | |
1975 | ||
c1b5d019 LB |
1976 | status.showStash:: |
1977 | If set to true, linkgit:git-status[1] will display the number of | |
1978 | entries currently stashed away. | |
1979 | Defaults to false. | |
1980 | ||
d6293d1f MSO |
1981 | status.showUntrackedFiles:: |
1982 | By default, linkgit:git-status[1] and linkgit:git-commit[1] show | |
1983 | files which are not currently tracked by Git. Directories which | |
1984 | contain only untracked files, are shown with the directory name | |
1985 | only. Showing untracked files means that Git needs to lstat() all | |
71069cdf | 1986 | the files in the whole repository, which might be slow on some |
d6293d1f MSO |
1987 | systems. So, this variable controls how the commands displays |
1988 | the untracked files. Possible values are: | |
1989 | + | |
1990 | -- | |
9373bdc4 CF |
1991 | * `no` - Show no untracked files. |
1992 | * `normal` - Show untracked files and directories. | |
1993 | * `all` - Show also individual files in untracked directories. | |
d6293d1f MSO |
1994 | -- |
1995 | + | |
1996 | If this variable is not specified, it defaults to 'normal'. | |
1997 | This variable can be overridden with the -u|--untracked-files option | |
1998 | of linkgit:git-status[1] and linkgit:git-commit[1]. | |
1999 | ||
da0005b8 | 2000 | status.submoduleSummary:: |
4b2343fa MG |
2001 | Defaults to false. |
2002 | If this is set to a non zero number or true (identical to -1 or an | |
2003 | unlimited number), the submodule summary will be enabled and a | |
2004 | summary of commits for modified submodules will be shown (see | |
bb58b696 JL |
2005 | --summary-limit option of linkgit:git-submodule[1]). Please note |
2006 | that the summary output command will be suppressed for all | |
2007 | submodules when `diff.ignoreSubmodules` is set to 'all' or only | |
1d2f393a JL |
2008 | for those submodules where `submodule.<name>.ignore=all`. The only |
2009 | exception to that rule is that status and commit will show staged | |
2010 | submodule changes. To | |
bb58b696 | 2011 | also view the summary for ignored submodules you can either use |
06ab60c0 | 2012 | the --ignore-submodules=dirty command-line option or the 'git |
bb58b696 JL |
2013 | submodule summary' command, which shows a similar output but does |
2014 | not honor these settings. | |
4b2343fa | 2015 | |
3086c064 NK |
2016 | stash.showPatch:: |
2017 | If this is set to true, the `git stash show` command without an | |
e01db917 | 2018 | option will show the stash entry in patch form. Defaults to false. |
3086c064 NK |
2019 | See description of 'show' command in linkgit:git-stash[1]. |
2020 | ||
2021 | stash.showStat:: | |
2022 | If this is set to true, the `git stash show` command without an | |
e01db917 | 2023 | option will show diffstat of the stash entry. Defaults to true. |
3086c064 NK |
2024 | See description of 'show' command in linkgit:git-stash[1]. |
2025 | ||
6014363f | 2026 | include::submodule-config.txt[] |
31224cbd | 2027 | |
61c2fe0c LA |
2028 | tag.forceSignAnnotated:: |
2029 | A boolean to specify whether annotated tags created should be GPG signed. | |
2030 | If `--annotate` is specified on the command line, it takes | |
2031 | precedence over this option. | |
2032 | ||
b150794d JK |
2033 | tag.sort:: |
2034 | This variable controls the sort ordering of tags when displayed by | |
2035 | linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the | |
2036 | value of this variable will be used as the default. | |
2037 | ||
ce1a79b6 | 2038 | tar.umask:: |
687157c7 RS |
2039 | This variable can be used to restrict the permission bits of |
2040 | tar archive entries. The default is 0002, which turns off the | |
2041 | world write bit. The special value "user" indicates that the | |
2042 | archiving user's umask will be used instead. See umask(2) and | |
5162e697 | 2043 | linkgit:git-archive[1]. |
ce1a79b6 | 2044 | |
dab76d3a JH |
2045 | transfer.fsckObjects:: |
2046 | When `fetch.fsckObjects` or `receive.fsckObjects` are | |
2047 | not set, the value of this variable is used instead. | |
2048 | Defaults to false. | |
5180dd2e ÆAB |
2049 | + |
2050 | When set, the fetch or receive will abort in the case of a malformed | |
456bab87 ÆAB |
2051 | object or a link to a nonexistent object. In addition, various other |
2052 | issues are checked for, including legacy issues (see `fsck.<msg-id>`), | |
2053 | and potential security issues like the existence of a `.GIT` directory | |
2054 | or a malicious `.gitmodules` file (see the release notes for v2.2.1 | |
2055 | and v2.17.1 for details). Other sanity and security checks may be | |
2056 | added in future releases. | |
2057 | + | |
2058 | On the receiving side, failing fsckObjects will make those objects | |
2059 | unreachable, see "QUARANTINE ENVIRONMENT" in | |
2060 | linkgit:git-receive-pack[1]. On the fetch side, malformed objects will | |
2061 | instead be left unreferenced in the repository. | |
720dae5a ÆAB |
2062 | + |
2063 | Due to the non-quarantine nature of the `fetch.fsckObjects` | |
2064 | implementation it can not be relied upon to leave the object store | |
2065 | clean like `receive.fsckObjects` can. | |
2066 | + | |
2067 | As objects are unpacked they're written to the object store, so there | |
2068 | can be cases where malicious objects get introduced even though the | |
2069 | "fetch" failed, only to have a subsequent "fetch" succeed because only | |
2070 | new incoming objects are checked, not those that have already been | |
2071 | written to the object store. That difference in behavior should not be | |
2072 | relied upon. In the future, such objects may be quarantined for | |
2073 | "fetch" as well. | |
2074 | + | |
2075 | For now, the paranoid need to find some way to emulate the quarantine | |
2076 | environment if they'd like the same protection as "push". E.g. in the | |
2077 | case of an internal mirror do the mirroring in two steps, one to fetch | |
2078 | the untrusted objects, and then do a second "push" (which will use the | |
2079 | quarantine) to another internal repo, and have internal clients | |
2080 | consume this pushed-to repository, or embargo internal fetches and | |
2081 | only allow them once a full "fsck" has run (and no new fetches have | |
2082 | happened in the meantime). | |
dab76d3a | 2083 | |
da0005b8 | 2084 | transfer.hideRefs:: |
cc118a65 JK |
2085 | String(s) `receive-pack` and `upload-pack` use to decide which |
2086 | refs to omit from their initial advertisements. Use more than | |
2087 | one definition to specify multiple prefix strings. A ref that is | |
2088 | under the hierarchies listed in the value of this variable is | |
2089 | excluded, and is hidden when responding to `git push` or `git | |
2090 | fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for | |
2091 | program-specific versions of this config. | |
2bc31d16 JK |
2092 | + |
2093 | You may also include a `!` in front of the ref name to negate the entry, | |
2094 | explicitly exposing it, even if an earlier entry marked it as hidden. | |
2095 | If you have multiple hideRefs values, later entries override earlier ones | |
2096 | (and entries in more-specific config files override less-specific ones). | |
92cab492 LF |
2097 | + |
2098 | If a namespace is in use, the namespace prefix is stripped from each | |
2099 | reference before it is matched against `transfer.hiderefs` patterns. | |
2100 | For example, if `refs/heads/master` is specified in `transfer.hideRefs` and | |
2101 | the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master` | |
2102 | is omitted from the advertisements but `refs/heads/master` and | |
2103 | `refs/namespaces/bar/refs/heads/master` are still advertised as so-called | |
78a766ab LF |
2104 | "have" lines. In order to match refs before stripping, add a `^` in front of |
2105 | the ref name. If you combine `!` and `^`, `!` must be specified first. | |
235ec243 MM |
2106 | + |
2107 | Even if you hide refs, a client may still be able to steal the target | |
2108 | objects via the techniques described in the "SECURITY" section of the | |
2109 | linkgit:gitnamespaces[7] man page; it's best to keep private data in a | |
2110 | separate repository. | |
daebaa78 | 2111 | |
b0f34c3d MM |
2112 | transfer.unpackLimit:: |
2113 | When `fetch.unpackLimit` or `receive.unpackLimit` are | |
2114 | not set, the value of this variable is used instead. | |
2115 | The default value is 100. | |
2116 | ||
7671b632 SG |
2117 | uploadarchive.allowUnreachable:: |
2118 | If true, allow clients to use `git archive --remote` to request | |
2119 | any tree, whether reachable from the ref tips or not. See the | |
235ec243 | 2120 | discussion in the "SECURITY" section of |
7671b632 SG |
2121 | linkgit:git-upload-archive[1] for more details. Defaults to |
2122 | `false`. | |
2123 | ||
da0005b8 | 2124 | uploadpack.hideRefs:: |
cc118a65 JK |
2125 | This variable is the same as `transfer.hideRefs`, but applies |
2126 | only to `upload-pack` (and so affects only fetches, not pushes). | |
2127 | An attempt to fetch a hidden ref by `git fetch` will fail. See | |
2128 | also `uploadpack.allowTipSHA1InWant`. | |
390eb36b | 2129 | |
bc0a4741 | 2130 | uploadpack.allowTipSHA1InWant:: |
da0005b8 | 2131 | When `uploadpack.hideRefs` is in effect, allow `upload-pack` |
390eb36b JH |
2132 | to accept a fetch request that asks for an object at the tip |
2133 | of a hidden ref (by default, such a request is rejected). | |
235ec243 MM |
2134 | See also `uploadpack.hideRefs`. Even if this is false, a client |
2135 | may be able to steal objects via the techniques described in the | |
2136 | "SECURITY" section of the linkgit:gitnamespaces[7] man page; it's | |
2137 | best to keep private data in a separate repository. | |
daebaa78 | 2138 | |
68ee6289 FM |
2139 | uploadpack.allowReachableSHA1InWant:: |
2140 | Allow `upload-pack` to accept a fetch request that asks for an | |
2141 | object that is reachable from any ref tip. However, note that | |
2142 | calculating object reachability is computationally expensive. | |
235ec243 MM |
2143 | Defaults to `false`. Even if this is false, a client may be able |
2144 | to steal objects via the techniques described in the "SECURITY" | |
2145 | section of the linkgit:gitnamespaces[7] man page; it's best to | |
2146 | keep private data in a separate repository. | |
68ee6289 | 2147 | |
f8edeaa0 DT |
2148 | uploadpack.allowAnySHA1InWant:: |
2149 | Allow `upload-pack` to accept a fetch request that asks for any | |
2150 | object at all. | |
2151 | Defaults to `false`. | |
2152 | ||
da0005b8 | 2153 | uploadpack.keepAlive:: |
05e95155 JK |
2154 | When `upload-pack` has started `pack-objects`, there may be a |
2155 | quiet period while `pack-objects` prepares the pack. Normally | |
2156 | it would output progress information, but if `--quiet` was used | |
2157 | for the fetch, `pack-objects` will output nothing at all until | |
2158 | the pack data begins. Some clients and networks may consider | |
2159 | the server to be hung and give up. Setting this option instructs | |
2160 | `upload-pack` to send an empty keepalive packet every | |
da0005b8 | 2161 | `uploadpack.keepAlive` seconds. Setting this option to 0 |
115dedd7 | 2162 | disables keepalive packets entirely. The default is 5 seconds. |
05e95155 | 2163 | |
20b20a22 JK |
2164 | uploadpack.packObjectsHook:: |
2165 | If this option is set, when `upload-pack` would run | |
2166 | `git pack-objects` to create a packfile for a client, it will | |
2167 | run this shell command instead. The `pack-objects` command and | |
2168 | arguments it _would_ have run (including the `git pack-objects` | |
2169 | at the beginning) are appended to the shell command. The stdin | |
2170 | and stdout of the hook are treated as if `pack-objects` itself | |
2171 | was run. I.e., `upload-pack` will feed input intended for | |
2172 | `pack-objects` to the hook, and expects a completed packfile on | |
2173 | stdout. | |
2174 | + | |
2175 | Note that this configuration variable is ignored if it is seen in the | |
2176 | repository-level config (this is a safety measure against fetching from | |
2177 | untrusted repositories). | |
2178 | ||
e56b5355 NTND |
2179 | uploadpack.allowFilter:: |
2180 | If this option is set, `upload-pack` will support partial | |
2181 | clone and partial fetch object filtering. | |
2182 | ||
516e2b76 BW |
2183 | uploadpack.allowRefInWant:: |
2184 | If this option is set, `upload-pack` will support the `ref-in-want` | |
2185 | feature of the protocol version 2 `fetch` command. This feature | |
2186 | is intended for the benefit of load-balanced servers which may | |
2187 | not have the same view of what OIDs their refs point to due to | |
2188 | replication delay. | |
2189 | ||
55029ae4 DB |
2190 | url.<base>.insteadOf:: |
2191 | Any URL that starts with this value will be rewritten to | |
2192 | start, instead, with <base>. In cases where some site serves a | |
2193 | large number of repositories, and serves them with multiple | |
2194 | access methods, and some users need to use different access | |
2195 | methods, this feature allows people to specify any of the | |
2de9b711 | 2196 | equivalent URLs and have Git automatically rewrite the URL to |
55029ae4 | 2197 | the best alternative for the particular user, even for a |
844112ca JH |
2198 | never-before-seen repository on the site. When more than one |
2199 | insteadOf strings match a given URL, the longest match is used. | |
2c9a2ae2 JK |
2200 | + |
2201 | Note that any protocol restrictions will be applied to the rewritten | |
2202 | URL. If the rewrite changes the URL to use a custom protocol or remote | |
2203 | helper, you may need to adjust the `protocol.*.allow` config to permit | |
2204 | the request. In particular, protocols you expect to use for submodules | |
2205 | must be set to `always` rather than the default of `user`. See the | |
2206 | description of `protocol.allow` above. | |
55029ae4 | 2207 | |
1c2eafb8 JT |
2208 | url.<base>.pushInsteadOf:: |
2209 | Any URL that starts with this value will not be pushed to; | |
2210 | instead, it will be rewritten to start with <base>, and the | |
2211 | resulting URL will be pushed to. In cases where some site serves | |
2212 | a large number of repositories, and serves them with multiple | |
2213 | access methods, some of which do not allow push, this feature | |
2de9b711 | 2214 | allows people to specify a pull-only URL and have Git |
1c2eafb8 JT |
2215 | automatically use an appropriate URL to push, even for a |
2216 | never-before-seen repository on the site. When more than one | |
2217 | pushInsteadOf strings match a given URL, the longest match is | |
2de9b711 | 2218 | used. If a remote has an explicit pushurl, Git will ignore this |
1c2eafb8 JT |
2219 | setting for that remote. |
2220 | ||
1ab661dd PB |
2221 | user.email:: |
2222 | Your email address to be recorded in any newly created commits. | |
eee7f4a2 | 2223 | Can be overridden by the `GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_EMAIL`, and |
47d81b5c | 2224 | `EMAIL` environment variables. See linkgit:git-commit-tree[1]. |
1ab661dd PB |
2225 | |
2226 | user.name:: | |
2227 | Your full name to be recorded in any newly created commits. | |
eee7f4a2 | 2228 | Can be overridden by the `GIT_AUTHOR_NAME` and `GIT_COMMITTER_NAME` |
5162e697 | 2229 | environment variables. See linkgit:git-commit-tree[1]. |
1ab661dd | 2230 | |
4d5c2956 | 2231 | user.useConfigOnly:: |
ae9f6311 TR |
2232 | Instruct Git to avoid trying to guess defaults for `user.email` |
2233 | and `user.name`, and instead retrieve the values only from the | |
4d5c2956 DA |
2234 | configuration. For example, if you have multiple email addresses |
2235 | and would like to use a different one for each repository, then | |
2236 | with this configuration option set to `true` in the global config | |
2237 | along with a name, Git will prompt you to set up an email before | |
2238 | making new commits in a newly cloned repository. | |
2239 | Defaults to `false`. | |
2240 | ||
da0005b8 | 2241 | user.signingKey:: |
f0551693 NV |
2242 | If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the |
2243 | key you want it to automatically when creating a signed tag or | |
2244 | commit, you can override the default selection with this variable. | |
2245 | This option is passed unchanged to gpg's --local-user parameter, | |
2246 | so you may specify a key using any method that gpg supports. | |
d67778ec | 2247 | |
c026557a SG |
2248 | versionsort.prereleaseSuffix (deprecated):: |
2249 | Deprecated alias for `versionsort.suffix`. Ignored if | |
2250 | `versionsort.suffix` is set. | |
2251 | ||
2252 | versionsort.suffix:: | |
2253 | Even when version sort is used in linkgit:git-tag[1], tagnames | |
2254 | with the same base version but different suffixes are still sorted | |
2255 | lexicographically, resulting e.g. in prerelease tags appearing | |
2256 | after the main release (e.g. "1.0-rc1" after "1.0"). This | |
2257 | variable can be specified to determine the sorting order of tags | |
2258 | with different suffixes. | |
2259 | + | |
2260 | By specifying a single suffix in this variable, any tagname containing | |
2261 | that suffix will appear before the corresponding main release. E.g. if | |
2262 | the variable is set to "-rc", then all "1.0-rcX" tags will appear before | |
2263 | "1.0". If specified multiple times, once per suffix, then the order of | |
2264 | suffixes in the configuration will determine the sorting order of tagnames | |
2265 | with those suffixes. E.g. if "-pre" appears before "-rc" in the | |
2266 | configuration, then all "1.0-preX" tags will be listed before any | |
2267 | "1.0-rcX" tags. The placement of the main release tag relative to tags | |
2268 | with various suffixes can be determined by specifying the empty suffix | |
2269 | among those other suffixes. E.g. if the suffixes "-rc", "", "-ck" and | |
2270 | "-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags | |
2271 | are listed first, followed by "v4.8", then "v4.8-ckX" and finally | |
2272 | "v4.8-bfsX". | |
2273 | + | |
b8231660 | 2274 | If more than one suffixes match the same tagname, then that tagname will |
51acfa9d SG |
2275 | be sorted according to the suffix which starts at the earliest position in |
2276 | the tagname. If more than one different matching suffixes start at | |
2277 | that earliest position, then that tagname will be sorted according to the | |
2278 | longest of those suffixes. | |
b8231660 SG |
2279 | The sorting order between different suffixes is undefined if they are |
2280 | in multiple config files. | |
d811c8e1 | 2281 | |
983a9eeb CC |
2282 | web.browser:: |
2283 | Specify a web browser that may be used by some commands. | |
2284 | Currently only linkgit:git-instaweb[1] and linkgit:git-help[1] | |
2285 | may use it. | |
e92445a7 TG |
2286 | |
2287 | worktree.guessRemote:: | |
2288 | With `add`, if no branch argument, and neither of `-b` nor | |
2289 | `-B` nor `--detach` are given, the command defaults to | |
2290 | creating a new branch from HEAD. If `worktree.guessRemote` is | |
2291 | set to true, `worktree add` tries to find a remote-tracking | |
2292 | branch whose name uniquely matches the new branch name. If | |
2293 | such a branch exists, it is checked out and set as "upstream" | |
2294 | for the new branch. If no such match can be found, it falls | |
2295 | back to creating a new branch from the current HEAD. |