]>
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 | |
0a7839e3 | 312 | include::config/color.txt[] |
6b2f2d98 | 313 | |
dbfc949f | 314 | include::config/column.txt[] |
d96e3c15 | 315 | |
5453d236 | 316 | include::config/commit.txt[] |
aaab8420 | 317 | |
3a49be6d | 318 | include::config/credential.txt[] |
7f4d4746 | 319 | |
2b4b7305 | 320 | include::config/completion.txt[] |
6532f374 | 321 | |
fa922d74 | 322 | include::config/diff.txt[] |
afcbc8e7 | 323 | |
9155f6f6 | 324 | include::config/difftool.txt[] |
a904392e | 325 | |
f2e58246 | 326 | include::config/fastimport.txt[] |
d9545c7f | 327 | |
561fda20 | 328 | include::config/fetch.txt[] |
42cc7485 | 329 | |
ab14f494 | 330 | include::config/format.txt[] |
bb52995f | 331 | |
734dfebb | 332 | include::config/filter.txt[] |
26488f59 | 333 | |
f80ccccb | 334 | include::config/fsck.txt[] |
1335f732 | 335 | |
8daf3271 | 336 | include::config/gc.txt[] |
48c32424 | 337 | |
996f66eb | 338 | include::config/gitcvs.txt[] |
04752868 | 339 | |
0648b769 | 340 | include::config/gitweb.txt[] |
cd82323f | 341 | |
434e6e75 | 342 | include::config/grep.txt[] |
ecd9ba61 | 343 | |
ea555d04 | 344 | include::config/gpg.txt[] |
b02f51b1 | 345 | |
d864cf8b | 346 | include::config/gui.txt[] |
a2df1fb2 | 347 | |
2c31a830 | 348 | include::config/guitool.txt[] |
390c3480 | 349 | |
d3df4270 | 350 | include::config/help.txt[] |
b1f809d0 | 351 | |
ad308479 | 352 | include::config/http.txt[] |
6a56993b | 353 | |
8fc3f75f | 354 | include::config/i18n.txt[] |
d2c11a38 | 355 | |
ae461026 | 356 | include::config/imap.txt[] |
b0f34c3d | 357 | |
c1b342ad | 358 | include::config/index.txt[] |
3c09d684 | 359 | |
ec335607 | 360 | include::config/init.txt[] |
d8a8488d | 361 | |
cef9b951 | 362 | include::config/instaweb.txt[] |
983a9eeb | 363 | |
630c2738 | 364 | include::config/interactive.txt[] |
01143847 | 365 | |
83009762 | 366 | include::config/log.txt[] |
e6bb5f78 | 367 | |
55e51cd7 | 368 | include::config/mailinfo.txt[] |
d5c4b185 | 369 | |
4a9f0c52 | 370 | include::config/mailmap.txt[] |
08610900 | 371 | |
f7ade6c9 | 372 | include::config/man.txt[] |
7e8114c0 | 373 | |
7fb5ab4a | 374 | include::config/merge.txt[] |
b5412484 | 375 | |
ea24a76a | 376 | include::config/mergetool.txt[] |
682b451f | 377 | |
e50472d8 | 378 | include::config/notes.txt[] |
6956f858 | 379 | |
a168c5a2 | 380 | include::config/pack.txt[] |
ae4f07fb | 381 | |
87e1b41a | 382 | include::config/pager.txt[] |
4370c2d6 | 383 | |
cd967547 | 384 | include::config/pretty.txt[] |
8028184e | 385 | |
dd55172c | 386 | include::config/protocol.txt[] |
373d70ef | 387 | |
7f50a495 | 388 | include::config/pull.txt[] |
d8052750 | 389 | |
d15dc439 | 390 | include::config/push.txt[] |
b33a15b0 | 391 | |
c7245900 | 392 | include::config/rebase.txt[] |
16cf51c7 | 393 | |
5f5a5fca | 394 | include::config/receive.txt[] |
0a1bc12b | 395 | |
99fce397 | 396 | include::config/remote.txt[] |
737c5a9c | 397 | |
b720a9db | 398 | include::config/remotes.txt[] |
1918278e | 399 | |
be958be2 | 400 | include::config/repack.txt[] |
ee34a2be | 401 | |
72622c24 | 402 | include::config/rerere.txt[] |
b0f34c3d | 403 | |
e344b8b4 | 404 | include::config/reset.txt[] |
4c3abd05 | 405 | |
0ee42c86 | 406 | include::config/sendemail.txt[] |
5453b83b | 407 | |
c3324199 | 408 | include::config/sequencer.txt[] |
8dc9d22d | 409 | |
c52bcbb6 | 410 | include::config/showbranch.txt[] |
1ab661dd | 411 | |
2ef0e469 | 412 | include::config/splitindex.txt[] |
b2dd1c5c | 413 | |
12e60249 NTND |
414 | include::config/ssh.txt[] |
415 | ||
54ff5dda | 416 | include::config/status.txt[] |
4b2343fa | 417 | |
46a8bbb2 | 418 | include::config/stash.txt[] |
3086c064 | 419 | |
95c125f2 | 420 | include::config/submodule.txt[] |
31224cbd | 421 | |
61c2fe0c LA |
422 | tag.forceSignAnnotated:: |
423 | A boolean to specify whether annotated tags created should be GPG signed. | |
424 | If `--annotate` is specified on the command line, it takes | |
425 | precedence over this option. | |
426 | ||
b150794d JK |
427 | tag.sort:: |
428 | This variable controls the sort ordering of tags when displayed by | |
429 | linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the | |
430 | value of this variable will be used as the default. | |
431 | ||
ce1a79b6 | 432 | tar.umask:: |
687157c7 RS |
433 | This variable can be used to restrict the permission bits of |
434 | tar archive entries. The default is 0002, which turns off the | |
435 | world write bit. The special value "user" indicates that the | |
436 | archiving user's umask will be used instead. See umask(2) and | |
5162e697 | 437 | linkgit:git-archive[1]. |
ce1a79b6 | 438 | |
dab76d3a JH |
439 | transfer.fsckObjects:: |
440 | When `fetch.fsckObjects` or `receive.fsckObjects` are | |
441 | not set, the value of this variable is used instead. | |
442 | Defaults to false. | |
5180dd2e ÆAB |
443 | + |
444 | When set, the fetch or receive will abort in the case of a malformed | |
456bab87 ÆAB |
445 | object or a link to a nonexistent object. In addition, various other |
446 | issues are checked for, including legacy issues (see `fsck.<msg-id>`), | |
447 | and potential security issues like the existence of a `.GIT` directory | |
448 | or a malicious `.gitmodules` file (see the release notes for v2.2.1 | |
449 | and v2.17.1 for details). Other sanity and security checks may be | |
450 | added in future releases. | |
451 | + | |
452 | On the receiving side, failing fsckObjects will make those objects | |
453 | unreachable, see "QUARANTINE ENVIRONMENT" in | |
454 | linkgit:git-receive-pack[1]. On the fetch side, malformed objects will | |
455 | instead be left unreferenced in the repository. | |
720dae5a ÆAB |
456 | + |
457 | Due to the non-quarantine nature of the `fetch.fsckObjects` | |
458 | implementation it can not be relied upon to leave the object store | |
459 | clean like `receive.fsckObjects` can. | |
460 | + | |
461 | As objects are unpacked they're written to the object store, so there | |
462 | can be cases where malicious objects get introduced even though the | |
463 | "fetch" failed, only to have a subsequent "fetch" succeed because only | |
464 | new incoming objects are checked, not those that have already been | |
465 | written to the object store. That difference in behavior should not be | |
466 | relied upon. In the future, such objects may be quarantined for | |
467 | "fetch" as well. | |
468 | + | |
469 | For now, the paranoid need to find some way to emulate the quarantine | |
470 | environment if they'd like the same protection as "push". E.g. in the | |
471 | case of an internal mirror do the mirroring in two steps, one to fetch | |
472 | the untrusted objects, and then do a second "push" (which will use the | |
473 | quarantine) to another internal repo, and have internal clients | |
474 | consume this pushed-to repository, or embargo internal fetches and | |
475 | only allow them once a full "fsck" has run (and no new fetches have | |
476 | happened in the meantime). | |
dab76d3a | 477 | |
da0005b8 | 478 | transfer.hideRefs:: |
cc118a65 JK |
479 | String(s) `receive-pack` and `upload-pack` use to decide which |
480 | refs to omit from their initial advertisements. Use more than | |
481 | one definition to specify multiple prefix strings. A ref that is | |
482 | under the hierarchies listed in the value of this variable is | |
483 | excluded, and is hidden when responding to `git push` or `git | |
484 | fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for | |
485 | program-specific versions of this config. | |
2bc31d16 JK |
486 | + |
487 | You may also include a `!` in front of the ref name to negate the entry, | |
488 | explicitly exposing it, even if an earlier entry marked it as hidden. | |
489 | If you have multiple hideRefs values, later entries override earlier ones | |
490 | (and entries in more-specific config files override less-specific ones). | |
92cab492 LF |
491 | + |
492 | If a namespace is in use, the namespace prefix is stripped from each | |
493 | reference before it is matched against `transfer.hiderefs` patterns. | |
494 | For example, if `refs/heads/master` is specified in `transfer.hideRefs` and | |
495 | the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master` | |
496 | is omitted from the advertisements but `refs/heads/master` and | |
497 | `refs/namespaces/bar/refs/heads/master` are still advertised as so-called | |
78a766ab LF |
498 | "have" lines. In order to match refs before stripping, add a `^` in front of |
499 | the ref name. If you combine `!` and `^`, `!` must be specified first. | |
235ec243 MM |
500 | + |
501 | Even if you hide refs, a client may still be able to steal the target | |
502 | objects via the techniques described in the "SECURITY" section of the | |
503 | linkgit:gitnamespaces[7] man page; it's best to keep private data in a | |
504 | separate repository. | |
daebaa78 | 505 | |
b0f34c3d MM |
506 | transfer.unpackLimit:: |
507 | When `fetch.unpackLimit` or `receive.unpackLimit` are | |
508 | not set, the value of this variable is used instead. | |
509 | The default value is 100. | |
510 | ||
7671b632 SG |
511 | uploadarchive.allowUnreachable:: |
512 | If true, allow clients to use `git archive --remote` to request | |
513 | any tree, whether reachable from the ref tips or not. See the | |
235ec243 | 514 | discussion in the "SECURITY" section of |
7671b632 SG |
515 | linkgit:git-upload-archive[1] for more details. Defaults to |
516 | `false`. | |
517 | ||
da0005b8 | 518 | uploadpack.hideRefs:: |
cc118a65 JK |
519 | This variable is the same as `transfer.hideRefs`, but applies |
520 | only to `upload-pack` (and so affects only fetches, not pushes). | |
521 | An attempt to fetch a hidden ref by `git fetch` will fail. See | |
522 | also `uploadpack.allowTipSHA1InWant`. | |
390eb36b | 523 | |
bc0a4741 | 524 | uploadpack.allowTipSHA1InWant:: |
da0005b8 | 525 | When `uploadpack.hideRefs` is in effect, allow `upload-pack` |
390eb36b JH |
526 | to accept a fetch request that asks for an object at the tip |
527 | of a hidden ref (by default, such a request is rejected). | |
235ec243 MM |
528 | See also `uploadpack.hideRefs`. Even if this is false, a client |
529 | may be able to steal objects via the techniques described in the | |
530 | "SECURITY" section of the linkgit:gitnamespaces[7] man page; it's | |
531 | best to keep private data in a separate repository. | |
daebaa78 | 532 | |
68ee6289 FM |
533 | uploadpack.allowReachableSHA1InWant:: |
534 | Allow `upload-pack` to accept a fetch request that asks for an | |
535 | object that is reachable from any ref tip. However, note that | |
536 | calculating object reachability is computationally expensive. | |
235ec243 MM |
537 | Defaults to `false`. Even if this is false, a client may be able |
538 | to steal objects via the techniques described in the "SECURITY" | |
539 | section of the linkgit:gitnamespaces[7] man page; it's best to | |
540 | keep private data in a separate repository. | |
68ee6289 | 541 | |
f8edeaa0 DT |
542 | uploadpack.allowAnySHA1InWant:: |
543 | Allow `upload-pack` to accept a fetch request that asks for any | |
544 | object at all. | |
545 | Defaults to `false`. | |
546 | ||
da0005b8 | 547 | uploadpack.keepAlive:: |
05e95155 JK |
548 | When `upload-pack` has started `pack-objects`, there may be a |
549 | quiet period while `pack-objects` prepares the pack. Normally | |
550 | it would output progress information, but if `--quiet` was used | |
551 | for the fetch, `pack-objects` will output nothing at all until | |
552 | the pack data begins. Some clients and networks may consider | |
553 | the server to be hung and give up. Setting this option instructs | |
554 | `upload-pack` to send an empty keepalive packet every | |
da0005b8 | 555 | `uploadpack.keepAlive` seconds. Setting this option to 0 |
115dedd7 | 556 | disables keepalive packets entirely. The default is 5 seconds. |
05e95155 | 557 | |
20b20a22 JK |
558 | uploadpack.packObjectsHook:: |
559 | If this option is set, when `upload-pack` would run | |
560 | `git pack-objects` to create a packfile for a client, it will | |
561 | run this shell command instead. The `pack-objects` command and | |
562 | arguments it _would_ have run (including the `git pack-objects` | |
563 | at the beginning) are appended to the shell command. The stdin | |
564 | and stdout of the hook are treated as if `pack-objects` itself | |
565 | was run. I.e., `upload-pack` will feed input intended for | |
566 | `pack-objects` to the hook, and expects a completed packfile on | |
567 | stdout. | |
568 | + | |
569 | Note that this configuration variable is ignored if it is seen in the | |
570 | repository-level config (this is a safety measure against fetching from | |
571 | untrusted repositories). | |
572 | ||
e56b5355 NTND |
573 | uploadpack.allowFilter:: |
574 | If this option is set, `upload-pack` will support partial | |
575 | clone and partial fetch object filtering. | |
576 | ||
516e2b76 BW |
577 | uploadpack.allowRefInWant:: |
578 | If this option is set, `upload-pack` will support the `ref-in-want` | |
579 | feature of the protocol version 2 `fetch` command. This feature | |
580 | is intended for the benefit of load-balanced servers which may | |
581 | not have the same view of what OIDs their refs point to due to | |
582 | replication delay. | |
583 | ||
55029ae4 DB |
584 | url.<base>.insteadOf:: |
585 | Any URL that starts with this value will be rewritten to | |
586 | start, instead, with <base>. In cases where some site serves a | |
587 | large number of repositories, and serves them with multiple | |
588 | access methods, and some users need to use different access | |
589 | methods, this feature allows people to specify any of the | |
2de9b711 | 590 | equivalent URLs and have Git automatically rewrite the URL to |
55029ae4 | 591 | the best alternative for the particular user, even for a |
844112ca JH |
592 | never-before-seen repository on the site. When more than one |
593 | insteadOf strings match a given URL, the longest match is used. | |
2c9a2ae2 JK |
594 | + |
595 | Note that any protocol restrictions will be applied to the rewritten | |
596 | URL. If the rewrite changes the URL to use a custom protocol or remote | |
597 | helper, you may need to adjust the `protocol.*.allow` config to permit | |
598 | the request. In particular, protocols you expect to use for submodules | |
599 | must be set to `always` rather than the default of `user`. See the | |
600 | description of `protocol.allow` above. | |
55029ae4 | 601 | |
1c2eafb8 JT |
602 | url.<base>.pushInsteadOf:: |
603 | Any URL that starts with this value will not be pushed to; | |
604 | instead, it will be rewritten to start with <base>, and the | |
605 | resulting URL will be pushed to. In cases where some site serves | |
606 | a large number of repositories, and serves them with multiple | |
607 | access methods, some of which do not allow push, this feature | |
2de9b711 | 608 | allows people to specify a pull-only URL and have Git |
1c2eafb8 JT |
609 | automatically use an appropriate URL to push, even for a |
610 | never-before-seen repository on the site. When more than one | |
611 | pushInsteadOf strings match a given URL, the longest match is | |
2de9b711 | 612 | used. If a remote has an explicit pushurl, Git will ignore this |
1c2eafb8 JT |
613 | setting for that remote. |
614 | ||
1ab661dd PB |
615 | user.email:: |
616 | Your email address to be recorded in any newly created commits. | |
eee7f4a2 | 617 | Can be overridden by the `GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_EMAIL`, and |
47d81b5c | 618 | `EMAIL` environment variables. See linkgit:git-commit-tree[1]. |
1ab661dd PB |
619 | |
620 | user.name:: | |
621 | Your full name to be recorded in any newly created commits. | |
eee7f4a2 | 622 | Can be overridden by the `GIT_AUTHOR_NAME` and `GIT_COMMITTER_NAME` |
5162e697 | 623 | environment variables. See linkgit:git-commit-tree[1]. |
1ab661dd | 624 | |
4d5c2956 | 625 | user.useConfigOnly:: |
ae9f6311 TR |
626 | Instruct Git to avoid trying to guess defaults for `user.email` |
627 | and `user.name`, and instead retrieve the values only from the | |
4d5c2956 DA |
628 | configuration. For example, if you have multiple email addresses |
629 | and would like to use a different one for each repository, then | |
630 | with this configuration option set to `true` in the global config | |
631 | along with a name, Git will prompt you to set up an email before | |
632 | making new commits in a newly cloned repository. | |
633 | Defaults to `false`. | |
634 | ||
da0005b8 | 635 | user.signingKey:: |
f0551693 NV |
636 | If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the |
637 | key you want it to automatically when creating a signed tag or | |
638 | commit, you can override the default selection with this variable. | |
639 | This option is passed unchanged to gpg's --local-user parameter, | |
640 | so you may specify a key using any method that gpg supports. | |
d67778ec | 641 | |
c026557a SG |
642 | versionsort.prereleaseSuffix (deprecated):: |
643 | Deprecated alias for `versionsort.suffix`. Ignored if | |
644 | `versionsort.suffix` is set. | |
645 | ||
646 | versionsort.suffix:: | |
647 | Even when version sort is used in linkgit:git-tag[1], tagnames | |
648 | with the same base version but different suffixes are still sorted | |
649 | lexicographically, resulting e.g. in prerelease tags appearing | |
650 | after the main release (e.g. "1.0-rc1" after "1.0"). This | |
651 | variable can be specified to determine the sorting order of tags | |
652 | with different suffixes. | |
653 | + | |
654 | By specifying a single suffix in this variable, any tagname containing | |
655 | that suffix will appear before the corresponding main release. E.g. if | |
656 | the variable is set to "-rc", then all "1.0-rcX" tags will appear before | |
657 | "1.0". If specified multiple times, once per suffix, then the order of | |
658 | suffixes in the configuration will determine the sorting order of tagnames | |
659 | with those suffixes. E.g. if "-pre" appears before "-rc" in the | |
660 | configuration, then all "1.0-preX" tags will be listed before any | |
661 | "1.0-rcX" tags. The placement of the main release tag relative to tags | |
662 | with various suffixes can be determined by specifying the empty suffix | |
663 | among those other suffixes. E.g. if the suffixes "-rc", "", "-ck" and | |
664 | "-bfs" appear in the configuration in this order, then all "v4.8-rcX" tags | |
665 | are listed first, followed by "v4.8", then "v4.8-ckX" and finally | |
666 | "v4.8-bfsX". | |
667 | + | |
b8231660 | 668 | If more than one suffixes match the same tagname, then that tagname will |
51acfa9d SG |
669 | be sorted according to the suffix which starts at the earliest position in |
670 | the tagname. If more than one different matching suffixes start at | |
671 | that earliest position, then that tagname will be sorted according to the | |
672 | longest of those suffixes. | |
b8231660 SG |
673 | The sorting order between different suffixes is undefined if they are |
674 | in multiple config files. | |
d811c8e1 | 675 | |
983a9eeb CC |
676 | web.browser:: |
677 | Specify a web browser that may be used by some commands. | |
678 | Currently only linkgit:git-instaweb[1] and linkgit:git-help[1] | |
679 | may use it. | |
e92445a7 TG |
680 | |
681 | worktree.guessRemote:: | |
682 | With `add`, if no branch argument, and neither of `-b` nor | |
683 | `-B` nor `--detach` are given, the command defaults to | |
684 | creating a new branch from HEAD. If `worktree.guessRemote` is | |
685 | set to true, `worktree add` tries to find a remote-tracking | |
686 | branch whose name uniquely matches the new branch name. If | |
687 | such a branch exists, it is checked out and set as "upstream" | |
688 | for the new branch. If no such match can be found, it falls | |
689 | back to creating a new branch from the current HEAD. |