You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stuffing the contents of the git-credentials file in to a variable called envvars smells like a bit of copypasta from the envvars section.
We're not writing the contents of that variable to disk anywhere before we try to mv "$key" .git-credentials, so the command fails.
Running git config credential.helper outside of a git repo without --global will fail with fatal: not in a git directory
I wish I had a nice PR with the issues fixed, but I don't. I was able to work thru problems 1 and 2 without difficulty, but problem 3 above leads us to have to use the git config command with --global, which introduces all sorts of pain as many builds may be running at once.
The one thing I did not look into was writing a custom git credentials helper or askpass program.
If you all are aware of this, no worries!
But if not, you might want to pull that section of the README and direct folks to stick with the private keys.
The text was updated successfully, but these errors were encountered:
Hi all! Today I attempted to use the git-credentials method, as mentioned here.
Turns out, there's a couple issues with the code in question.
git-credentials
file in to a variable calledenvvars
smells like a bit of copypasta from the envvars section.mv "$key" .git-credentials
, so the command fails.git config credential.helper
outside of a git repo without--global
will fail withfatal: not in a git directory
I wish I had a nice PR with the issues fixed, but I don't. I was able to work thru problems 1 and 2 without difficulty, but problem 3 above leads us to have to use the
git config
command with--global
, which introduces all sorts of pain as many builds may be running at once.The one thing I did not look into was writing a custom git credentials helper or askpass program.
If you all are aware of this, no worries!
But if not, you might want to pull that section of the README and direct folks to stick with the private keys.
The text was updated successfully, but these errors were encountered: