From: Christian Couder <christian.couder@gmail.com>
To: d.kopriwa@gmail.com
Cc: git <git@vger.kernel.org>
Subject: Re: Git credentials not working
Date: Wed, 3 Oct 2018 18:03:56 +0200 [thread overview]
Message-ID: <CAP8UFD3LEYd7RytZU_-wVcDosH+6VSdM2j3NUcnR0aQc8QfoQg@mail.gmail.com> (raw)
In-Reply-To: <f4f7bd2c-4c48-e749-4df1-ddf05896b337@gmail.com>
(removing git-security from CC)
On Wed, Oct 3, 2018 at 4:09 PM Dimitri Kopriwa <d.kopriwa@gmail.com> wrote:
> Git credentials in ~/.git-credentials and ~/.config/git/credentials are
> being removed by git upon reading.
https://git-scm.com/docs/git-credential says:
"If the action is reject, git-credential will send the description to
any configured credential helpers, which may erase any stored
credential matching the description."
So maybe this is expected.
Another possibility is that your .gitlab-ci.yml might launch scripts
writing into those files, like the before_script.sh script that is
described on:
https://stackoverflow.com/questions/50553049/is-it-possible-to-do-a-git-push-within-a-gitlab-ci-without-ssh
Could you also check which credential helper and which options are
used? For example with commands like:
$ git config -l --show-origin | grep -i cred
$ git config -l --show-origin | grep -i http
$ git config -l --show-origin | grep -i askpass
$ env | grep -i askpass
next prev parent reply other threads:[~2018-10-03 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1ceb967-6020-6074-f504-c684242c79ab@gmail.com>
2018-10-03 14:06 ` Fwd: Git credentials not working Dimitri Kopriwa
2018-10-03 16:03 ` Christian Couder [this message]
2018-10-03 17:29 ` Dimitri Kopriwa
2018-10-03 17:11 ` Fwd: " Jeff King
2018-10-03 18:12 ` Dimitri Kopriwa
2018-10-03 18:24 ` Jeff King
2018-10-03 19:34 ` Dimitri Kopriwa
2018-10-03 20:03 ` Bryan Turner
2018-10-03 20:43 ` Jeff King
2018-10-03 21:35 ` Dimitri Kopriwa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD3LEYd7RytZU_-wVcDosH+6VSdM2j3NUcnR0aQc8QfoQg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=d.kopriwa@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.
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 NNTP newsgroup(s).