···114are:
115116`gitdir`::
117-118- The data that follows the keyword `gitdir:` is used as a glob
119 pattern. If the location of the .git directory matches the
120 pattern, the include condition is met.
121+
···148 case-insensitively (e.g. on case-insensitive file systems)
149150`onbranch`::
151- The data that follows the keyword `onbranch:` is taken to be a
152 pattern with standard globbing wildcards and two additional
153 ones, `**/` and `/**`, that can match multiple path components.
154 If we are in a worktree where the name of the branch that is
···161organized hierarchically and you would like to apply a configuration to
162all the branches in that hierarchy.
163164-`hasconfig:remote.*.url:`::
165- The data that follows this keyword is taken to
166 be a pattern with standard globbing wildcards and two
167 additional ones, `**/` and `/**`, that can match multiple
168 components. The first time this keyword is seen, the rest of
···114are:
115116`gitdir`::
117+ The data that follows the keyword `gitdir` and a colon is used as a glob
0118 pattern. If the location of the .git directory matches the
119 pattern, the include condition is met.
120+
···147 case-insensitively (e.g. on case-insensitive file systems)
148149`onbranch`::
150+ The data that follows the keyword `onbranch` and a colon is taken to be a
151 pattern with standard globbing wildcards and two additional
152 ones, `**/` and `/**`, that can match multiple path components.
153 If we are in a worktree where the name of the branch that is
···160organized hierarchically and you would like to apply a configuration to
161all the branches in that hierarchy.
162163+`hasconfig:remote.*.url`::
164+ The data that follows this keyword and a colon is taken to
165 be a pattern with standard globbing wildcards and two
166 additional ones, `**/` and `/**`, that can match multiple
167 components. The first time this keyword is seen, the rest of