diff options
author | David Zych <dmrz@illinois.edu> | 2018-09-27 00:23:11 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-09-28 00:24:50 +0200 |
commit | 4ba3c9be47a0132fd0ba9bb04db7842c3b4967b2 (patch) | |
tree | 50af6a902a764acf8710b01d67ec94f8b22b8d91 /Documentation/gitcredentials.txt | |
parent | Git 2.19 (diff) | |
download | git-4ba3c9be47a0132fd0ba9bb04db7842c3b4967b2.tar.xz git-4ba3c9be47a0132fd0ba9bb04db7842c3b4967b2.zip |
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>
Diffstat (limited to '')
-rw-r--r-- | Documentation/gitcredentials.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/gitcredentials.txt b/Documentation/gitcredentials.txt index f970196bc1..adc759612d 100644 --- a/Documentation/gitcredentials.txt +++ b/Documentation/gitcredentials.txt @@ -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 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 --------------------- |