doc: clarify gitcredentials path component matching
The gitcredentials documentation implied that the config file's "pattern" URL might include a path component, but did not explain that it must match exactly (potentially leaving readers with the false hope that it would support a more flexible prefix match). Signed-off-by: David Zych <dmrz@illinois.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>maint
parent
1d4361b0f3
commit
4ba3c9be47
|
@ -133,6 +133,12 @@ compares hostnames exactly, without considering whether two hosts are part of
|
||||||
the same domain. Likewise, a config entry for `http://example.com` would not
|
the same domain. Likewise, a config entry for `http://example.com` would not
|
||||||
match: Git compares the protocols exactly.
|
match: Git compares the protocols exactly.
|
||||||
|
|
||||||
|
If the "pattern" URL does include a path component, then this too must match
|
||||||
|
exactly: the context `https://example.com/bar/baz.git` will match a config
|
||||||
|
entry for `https://example.com/bar/baz.git` (in addition to matching the config
|
||||||
|
entry for `https://example.com`) but will not match a config entry for
|
||||||
|
`https://example.com/bar`.
|
||||||
|
|
||||||
|
|
||||||
CONFIGURATION OPTIONS
|
CONFIGURATION OPTIONS
|
||||||
---------------------
|
---------------------
|
||||||
|
|
Loading…
Reference in New Issue