Re: Git credential store conflicting configuration leads to unexpected behavior
- From
Gennady Uraltsev <gennady.uraltsev@gmail.com>
- Date
- Dec 7, 2022, 01:19 UTC
- Message-ID
- <CACH4KQSJ_3J4qvbbv1+4URg4hpXAur3pzvMouXRkF8WsLVWhRg@mail.gmail.com>
- In-Reply-To
- <Y4/pO55b5DtPnavg@tapette.crustytoothpaste.net>
Thank you! I did miss it. I appreciate your time.
-- Gennady Uraltsev <gennady.uraltsev@gmail.com> (https://guraltsev.github.io)
On Tue, Dec 6, 2022 at 8:15 PM brian m. carlson <sandals@crustytoothpaste.net> wrote:
Show 25 quoted lines
> > On 2022-12-06 at 23:53:05, Gennady Uraltsev wrote: > > Thank you! > > > > This makes sense and the solution is simple. Is this somewhere in the > > documentation (honest question, I am not being a jerk)? I tried my > > best to figure this out before bugging people on the mailinglist. > > Yes, but maybe not where you'd expect. In gitcredentials(7), there's > this text: > > If there are multiple instances of the `credential.helper` configuration > variable, each helper will be tried in turn, and may provide a username, > password, or nothing. Once Git has acquired both a username and a > password, no more helpers will be tried. > > If `credential.helper` is configured to the empty string, this resets > the helper list to empty (so you may override a helper set by a > lower-priority config file by configuring the empty-string helper, > followed by whatever set of helpers you would like). > > The `credential.helper` option mentions that manual page. > -- > brian m. carlson (he/him or they/them) > Toronto, Ontario, CA