Visual Studio Code always asking for git credentia

问题:

I started using Visual Studio Code, and I was trying to save my test project into GitHub, but Visual Studio Code is always asking for my GitHub credentials.

I have installed in my PC GitHub Desktop and also Git, I already ran:

 git config --global credential.helper wincred

but still Visual Studio Code is asking for the credentials.

Any help?

here is my .gitconfig file located in the user profile folfer:

    [filter "lfs"]
    clean = git-lfs clean %f
    smudge = git-lfs smudge %f
    required = true
[user]
    name = ddieppa
[user]
    email = [e-mail]
[credential]
    helper = wincred

Here is the popup windows asking for the credentials:

I enter my GitHub credentials in the popup, but still getting this error in the Git output window in Visual Studio Code:

remote: Anonymous access to ddieppa/LineOfBizApp.git denied.
fatal: Authentication failed for 'https://github.com/ddieppa/LineOfBizApp.git/'

回答1:

I found the solution on VSCode document:

Tip: You should set up a credential helper to avoid getting asked for credentials every time VS Code talks to your Git remotes. If you don't do this, you may want to consider Disabling Autofetch in the ... menu to reduce the number of prompts you get.

So, turn on the credential helper so that Git will save your password in memory for some time. By default, Git will cache your password for 15 minutes.

In Terminal, enter the following:

git config --global credential.helper cache
# Set git to use the credential memory cache

To change the default password cache timeout, enter the following:

git config --global credential.helper 'cache --timeout=3600'
# Set the cache to timeout after 1 hour (setting is in seconds)

UPDATE

I installed VS Code and config same above, but as @ddieppa said, It didn't work for me too. So I tried to find an option in User Setting, and I saw "git.autofetch" = true, now set it's false! VS Code is no longer required to enter password repeatedly again!

In menu, click File / Preferences / User Setting And type these:

Place your settings in this file to overwrite the default settings

{
  "git.autofetch": false
}

回答2:

You should be able to set your credentials like this:

git remote set-url origin https://<USERNAME>:<PASSWORD>@bitbucket.org/path/to/repo.git

You can get the remote url like this:

git config --get remote.origin.url

回答3:

Try installing "Git Credential Manager For Windows" (and following instructions for setting up the credential manager).

When required within an app using Git (e.g. VS Code) it will "magically" open the required dialog for Visual Studio Team Services credential input.

回答4:

This has been working for me:
1. Set credential hepler to store
$ git config --global credential.helper store
2. then verify if you want:
$ git config --global credential.helper store

Simple example when using git bash quoted from Here (works for current repo only, use --global for all repos)

$ git config credential.helper store
$ git push http://example.com/repo.git
Username: < type your username >
Password: < type your password >

[several days later]
$ git push http://example.com/repo.git
[your credentials are used automatically]

Will work for VS Code too.

More detailed example and advanced usage here.

Note: Username & Passwords are not encrypted and stored in plain text format so use it on your personal computer only.

回答5:

Use ssh instead of http/https.

You will need to set ssh keys on your local machine, upload them to your git server and replace the url form http:// to git:// and you will not need to use passwords anymore.

If you cant use ssh add this to your config:

[credential "https://example.com"]
    username = me

documents are here.

---

Using ssh key in github

---

Simply follow those steps and you will set up your ssh key in no time:

• Generate a new ssh key (or skip this step if you already have a key)
  ssh-keygen -t rsa -C "your@email"

• Once you have your key set in home/.ssh directory (or Users/<your user>.ssh under windows), open it and copy the content

---

How to add sh key to github account?

• Login to github account
• Click on the rancher on the top right (Settings)
  
• Click on the SSH keys
  
• Click on the Add ssh key
  
• Paste your key and save

And you all set to go :-)

回答6:

All I had to do was to run this command:

git config --global credential.helper wincred

Then I was prompted for password twice.

Next time it worked without prompting me for password.

回答7:

The following steps walk you through how to:

1. Generate SSH keys (without passphrase**)
2. Add the public key generated in step 1 to your Git repository
3. Confirm the above steps have been completed successfully
4. Make your first commit (without having to provide a username / password)

**Generating SSH keys without a passphrase is unwise if your work is particularly sensitive.

OS - Fedora 28 | Editor - VS Code v1.23.0 | Repository - Git

Generate SSH keys:

• ssh-keygen -t rsa -C "[e-mail]"
• Enter file in which to save the key: Press Enter
• Enter passphrase: Press Enter
• Enter same passphrase again: Press Enter

After completing the above steps, the location of your public key is shown in the terminal window. If the currently logged in user is 'bob' the location of your public key would be /home/bob/.ssh/id_rsa.pub

Copy and import public key to GitHub:

• cat /home/bob/.ssh/id_rsa.pub

• Copy the whole public key that is now displayed in your terminal window to the clipboard

• Go to https://github.com and sign in
• Click the user icon in the top right corner of the screen and select Settings
• Click SSH and GPG keys
• Click New SSH key
• Enter a title, paste the public key copied to the clipboard in the first bullet point, and click Add SSH key

Confirm the above steps:

• ssh -T [e-mail]

• yes

• Hi ! You've successfully authenticated, but GitHub does not provide shell access.

First commit / push without having to enter a username / password: - touch test.txt

• git add test.txt

• git commit - opens editor, enter a message and save the file. If vi is your editor, press i once the file opens, enter a message, press esc, and then enter :x to save changes.

• git push

The only hiccup you may encounter is when you attempt to SSH to GitHub. This link will provide some assistance -

• https://help.github.com/articles/error-agent-admitted-failure-to-sign/

Happy hunting!

回答8:

Use an SSH key without a passphrase.

Maybe this is obvious to some (wasn't to me). It also doesn't solve the issue if you absolutely require a passphrase, but this was a decent compromise in my situation on Mac.

回答9:

After fighting with something like this for a little while, I think I came up with a good solution, especially when having multiple accounts across both GitHub and BitBucket. However for VSCode, it ultimately ended up as start it from a Git Bash terminal so that it inherited the environment variables from the bash session and it knew which ssh-agent to look at.

I realise this is an old post but I still really struggled to find one place to get the info I needed. Plus since 2017, ssh-agent got the ability to prompt you for a passphrase only when you try to access a repo.

I put my findings down here if anyone is interested:

回答10:

Following that article:

You may just set GIT_SSH env. var. to the Putty's plink.exe program. (Then use the pageant.exe as a auth. agent)

回答11:

For me I had setup my remote repo with an SSH key but git could not find them because the HOMEDRIVE environment variable was automatically getting set to a network share due to my company's domain policy. Changing that environment variable in my shell prior to launching code . caused VSCode to inherit the correct environment variable and viola no more connection errors in the git output window.

Now I just have to figure out how to override the domain policy so HOMEDRIVE is always pointing to my local c:\users\marvhen directory which is the default location for the .ssh directory.