doc: config: terminate runaway lists
There are many places in git-config(1) where paragraphs that should logically come after a list are instead appended to the last item of the list. This is a well-documented quirk of AsciiDoc, and can be mitigated by enclosing the list in an open block: -- * first item * last item -- + New paragraph after the list. Fix the issue accordingly. Signed-off-by: Tuomas Ahola <taahol@utu.fi> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Tuomas Ahola committed
Jun 11, 2026 at 19:19 UTC
3eb61fda62191dc12c2a215a3775bdab2ca7f1a6
4 files changed
+9
-1
Documentation/config.adoc
+3
-1
@@ -276,13 +276,15 @@ boolean::
276
When a variable is said to take a boolean value, many
277
synonyms are accepted for 'true' and 'false'; these are all
278
case-insensitive.
279
-
279
++
280
+--
281
true;; Boolean true literals are `yes`, `on`, `true`,
282
and `1`. Also, a variable defined without `= <value>`
283
is taken as true.
284
285
false;; Boolean false literals are `no`, `off`, `false`,
286
`0` and the empty string.
287
+--
288
+
289
When converting a value to its canonical form using the `--type=bool` type
290
specifier, 'git config' will ensure that the output is "true" or
Documentation/config/promisor.adoc
+2
@@ -63,11 +63,13 @@ If one of these field names (e.g., "token") is being checked for an
63
advertised promisor remote (e.g., "foo"), three conditions must be met
64
for the check of this specific field to pass:
65
+
66
+--
67
1. The corresponding local configuration (e.g., `remote.foo.token`)
68
must be set.
69
2. The server must advertise the "token" field for remote "foo".
70
3. The value of the locally configured `remote.foo.token` must exactly
71
match the value advertised by the server for the "token" field.
72
+--
73
+
74
If any of these conditions is not met for any field name listed in
75
`promisor.checkFields`, the advertised remote "foo" is rejected.
Documentation/config/safe.adoc
+2
@@ -2,10 +2,12 @@ safe.bareRepository::
2
Specifies which bare repositories Git will work with. The currently
3
supported values are:
4
+
5
+--
6
* `all`: Git works with all bare repositories. This is the default.
7
* `explicit`: Git only works with bare repositories specified via
8
the top-level `--git-dir` command-line option, or the `GIT_DIR`
9
environment variable (see linkgit:git[1]).
10
+--
11
+
12
If you do not use bare repositories in your workflow, then it may be
13
beneficial to set `safe.bareRepository` to `explicit` in your global
Documentation/git-config.adoc
+2
@@ -221,6 +221,7 @@ Use `--no-value` to unset _<pattern>_.
221
+
222
Valid `<type>`'s include:
223
+
224
+--
225
- 'bool': canonicalize values `true`, `yes`, `on`, and positive
226
numbers as "true", and values `false`, `no`, `off` and `0` as
227
"false".
@@ -239,6 +240,7 @@ Valid `<type>`'s include:
240
escape sequence. When setting a value, a sanity-check is performed to ensure
241
that the given value is canonicalize-able as an ANSI color, but it is written
242
as-is.
243
+--
244
+
245
If the command is in `list` mode, then the `--type <type>` argument will apply
246
to each listed config value. If the value does not successfully parse in that