···150150 username = foo
151151--------------------------------------
152152153153-then we will match: both protocols are the same, both hosts are the same, and
154154-the "pattern" URL does not care about the path component at all. However, this
155155-context would not match:
153153+then we will match: both protocols are the same and both hosts are the same.
154154+However, this context would not match:
156155157156--------------------------------------
158157[credential "https://kernel.org"]
···166165the domain name and other pattern matching techniques as with the `http.<URL>.*`
167166options.
168167169169-If the "pattern" URL does include a path component, then this too must match
170170-exactly: the context `https://example.com/bar/baz.git` will match a config
171171-entry for `https://example.com/bar/baz.git` (in addition to matching the config
172172-entry for `https://example.com`) but will not match a config entry for
173173-`https://example.com/bar`.
168168+If the "pattern" URL does include a path component, then this must match
169169+as a prefix path: the context `https://example.com/bar` will match a config
170170+entry for `https://example.com/bar/baz.git` but will not match a config entry for
171171+`https://example.com/other/repo.git` or `https://example.com/barry/repo.git`
172172+(even though it is a string prefix).
174173175174176175CONFIGURATION OPTIONS