From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Gennady Uraltsev <gennady.uraltsev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git credential store conflicting configuration leads to unexpected behavior
Date: Wed, 7 Dec 2022 01:15:39 +0000 [thread overview]
Message-ID: <Y4/pO55b5DtPnavg@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CACH4KQSj64WeqAV3CDkCXc+YW6dr+S2vN_QBj5SwcSP05fM0Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-12-07 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 22:05 Git credential store conflicting configuration leads to unexpected behavior Gennady Uraltsev
2022-12-06 22:16 ` brian m. carlson
2022-12-06 23:53 ` Gennady Uraltsev
2022-12-07 1:15 ` brian m. carlson [this message]
2022-12-07 1:19 ` Gennady Uraltsev
2022-12-07 12:01 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y4/pO55b5DtPnavg@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=gennady.uraltsev@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).