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>
David Zych committed
Sep 26, 2018 at 22:23 UTC
4ba3c9be47a0132fd0ba9bb04db7842c3b4967b2
1 file changed
+6
Documentation/gitcredentials.txt
+6
@@ -133,6 +133,12 @@ compares hostnames exactly, without considering whether two hosts are part of
133
the same domain. Likewise, a config entry for `http://example.com` would not
134
match: Git compares the protocols exactly.
135
136
+If the "pattern" URL does include a path component, then this too must match
137
+exactly: the context `https://example.com/bar/baz.git` will match a config
138
+entry for `https://example.com/bar/baz.git` (in addition to matching the config
139
+entry for `https://example.com`) but will not match a config entry for
140
+`https://example.com/bar`.
141
+
142
143
CONFIGURATION OPTIONS
144
---------------------