mirror of
https://github.com/git/git.git
synced 2025-12-12 20:36:24 +01:00
Merge branch 'mh/doc-credential-url-prefix' into maint-2.51
Doc update to describe a feature that has already been implemented. * mh/doc-credential-url-prefix: docs/gitcredentials: describe URL prefix matching
This commit is contained in:
@@ -150,9 +150,8 @@ pattern in the config file. For example, if you have this in your config file:
|
||||
username = foo
|
||||
--------------------------------------
|
||||
|
||||
then we will match: both protocols are the same, both hosts are the same, and
|
||||
the "pattern" URL does not care about the path component at all. However, this
|
||||
context would not match:
|
||||
then we will match: both protocols are the same and both hosts are the same.
|
||||
However, this context would not match:
|
||||
|
||||
--------------------------------------
|
||||
[credential "https://kernel.org"]
|
||||
@@ -166,11 +165,11 @@ match: Git compares the protocols exactly. However, you may use wildcards in
|
||||
the domain name and other pattern matching techniques as with the `http.<URL>.*`
|
||||
options.
|
||||
|
||||
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`.
|
||||
If the "pattern" URL does include a path component, then this must match
|
||||
as a prefix path: the context `https://example.com/bar` will match a config
|
||||
entry for `https://example.com/bar/baz.git` but will not match a config entry for
|
||||
`https://example.com/other/repo.git` or `https://example.com/barry/repo.git`
|
||||
(even though it is a string prefix).
|
||||
|
||||
|
||||
CONFIGURATION OPTIONS
|
||||
|
||||
Reference in New Issue
Block a user