Re: Git credential store conflicting configuration leads to unexpected behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux