Git-credential-manager looks at the configuration to determine if these are basic credentials, Visual Studio Team Services, or GitHub; if the request is multi-factor authentication; etc. In the case of basic credentials, git-credential-manager tells git-credential the truth that it does not have any credentials for it.

• Visual Studio For Mac Always Asking For Git Credentials
• Visual Studio For Mac Always Asking For Git Credentials Terminal

I am working with a repo on GitHub and everytime I try to push something, it asks for my GitHub username and password. I don't want it doing that.

I tried the instructions on setting your email in Git, namely set up the Git variables github.user and github.token, but that didn't make any difference.

I don't understand why this is happening.

random♦

Visual Studio For Mac Always Asking For Git Credentials

picardopicardo

12 Answers

You need to set-up an ssh-agent against which you only need to authenticate once. See this answer over at SO for a howto.

Benjamin BannierBenjamin Bannier

Had a similar problem today: I messed things up in my working copy, so I decided to rename the directory and clone my project again from github. But after doing that, I had to enter my password to do any pull/push request, instead of entering the passphrase just once as I used to.

That was because today I used the https protocol to clone the project! To check what protocol you're using just run

and look at the line starting with 'remote.origin.url'.

To switch protocols:

the_repository_username and your_project should be replaced with the appropriate repository name and the owner of that repository. The username will be yours if you own the repository, or the repository owner's username otherwise.

Sergio MorstabiliniSergio Morstabilini

If you are using HTTPS instead of SSH , you can follow this :

1. Find your remote URL (remote.origin.url) with

   thanks to Sergio Morstabilini

2. Your remote URL will be like this : https://{USERNAME}@github.com/{USERNAME}/{REPONAME}.git

3. Execute this command :

ErayEray

I prefer to use HTTPS, I find it easier and more secure than setting up the ssh keys.

Using HTTPS, you can prevent git from asking your username for github remotes with the following:

And you can at least reduce the frequency git asks for your password with:

Where 28800 are 8 hours. I use this setup to enter my password only once, when I start my working day.

After that you will have these entries inside your ~/.gitconfig

Source:

When you set up an ssh key for github, if it's not your default key, you will need to add a section to your ~/.ssh/config

DaenythDaenyth

If you are on Windows using HTTPS, try the Git Credential Store - it uses the Windows Credential Store to hold your name and password.

Then the next time you enter your name and password it will remember them for you.

Also, if you wish to be prompted for your password every-time, but just not your username, then you configure the remote as HTTPS with a username.. Like this..

After this, you will be prompted for your password every time, but not your username.

This is how I prefer it, since I like being forced to type my github password before sharing with the world.

Sathyajith Bhat♦

Things are a little different if you're using 2-factor auth as I am. Since I didn't find a good answer elsewhere, I'll stick one here so that maybe I can find it later.

If you're using 2-factor auth, then specifying username/password won't event work - you get access denied. But you can use an application access token and use git's credential helper to cache that for you. Here are the pertinent links:

• Setting up the command-line to work with 2-factor auth (search for section titled 'How does it work for command-line Git?')

And I don't remember where I saw this but when you're asked for your Username - that's where you stick the application access token. Then leave the password blank. Worked on my mac.

use SSH

To prevent GitHub asking for the password while pushing, ideally you should use SSH (git@github.com:...) instead of HTTPS URL (https://github.com/...) and add your SSH key to your GitHub account. See: Which remote URL should I use?

a credential helper

Otherwise if you really need to use HTTPS, to cache your GitHub password in Git, you should use a credential helper to tell Git to remember your GitHub username and password every time it talks to GitHub.

• Mac: git config --global credential.helper osxkeychain (osxkeychain helper is required),
• Windows: git config --global credential.helper wincred
• Linux and other: git config --global credential.helper cache

.netrc

Another method is to use configure your user/password in ~/.netrc (_netrc on Windows), e.g.

OAuth

Use OAuth token (Personal API token) to push the changes, e.g.

Related:

kenorbkenorb

Also if you are using Windows, you can use:

you just have to sign in one more time and then git will remember.

kenorb

Asking the username is annoying for me, but asking for a password is nice since it ensures you really want to go public with your changes...

So I just add this to my '.gitconfig'

Use Git Credential Manager for Windows, if you're on Windows.

This project includes:

• Secure password storage in the Windows Credential Store
• Multi-factor authentication support for Visual Studio Team Services
• Two-factor authentication support for GitHub
• Personal Access Token generation and usage support for Visual Studio Team Services and GitHub
• Non-interactive mode support for Visual Studio Team Services backed by Azure Directory
• Kerberos authentication for Team Foundation Server
• Optional settings for build agent optimization

Simply download the latest version and install it.

How to use

You don't. It magically works when credentials are needed.

Not the answer you're looking for? Browse other questions tagged logingitgithub or ask your own question.

Visual Studio Code has integrated source control and includes Git support in-the-box. Many other source control providers are available through extensions on the VS Code Marketplace.

Tip: Click on an extension tile to read the description and reviews in the Marketplace.

SCM Providers

VS Code has support for handling multiple Source Control providers simultaneously. For example, you can open multiple Git repositories alongside your TFS local workspace and seamlessly work across your projects. The SOURCE CONTROL PROVIDERS list of the Source Control view (⌃⇧G (Windows, Linux Ctrl+Shift+G)) shows the detected providers and repositories and you can scope the display of your changes by selecting a specific provider.

SCM Provider extensions

If you would like to install an additional SCM provider, you can search on the scm providers extension category in the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)). Start typing '@ca' and you will see suggestions for extension categories like debuggers and linters. Select @category:'scm providers' to see available SCM providers.

Git support

VS Code ships with a Git source control manager (SCM) extension. Most of the source control UI and work flows are common across other SCM extensions, so reading about the Git support will help you understand how to use another provider.

Note: If you are new to Git, the git-scm website is a good place to start with a popular online book, Getting Started videos and cheat sheets. The VS Code documentation assumes you are already familiar with Git.

Note: VS Code will leverage your machine's Git installation, so you need to install Git first before you get these features. Make sure you install at least version 2.0.0.

Tip: VS Code will work with any Git repository. If you don't already have a private hosted Git provider, Azure DevOps Services is a great free option. You can sign up at Get started with Azure DevOps.

The Source Control icon on the left will always indicate an overview of how many changes you currently have in your repository. Clicking it will show you the details of your current repository changes: CHANGES, STAGED CHANGES and MERGE CHANGES.

Clicking each item will show you in detail the textual changes within each file. Note that for unstaged changes, the editor on the right still lets you edit the file: feel free to use it!

You can also find indicators of the status of your repository in the bottom left corner of VS Code: the current branch, dirty indicators and the number of incoming and outgoing commits of the current branch. You can checkout any branch in your repository by clicking that status indicator and selecting the Git reference from the list.

Tip: You can open VS Code in a sub-directory of a Git repository. VS Code's Git services will still work as usual, showing all changes within the repository, but file changes outside of the scoped directory are shaded with a tool tip indicating they are located outside the current workspace.

Visual Studio For Mac Always Asking For Git Credentials Terminal

Commit

Staging (git add) and unstaging (git reset) can be done via contextual actions in the files or by drag-and-drop.

You can type a commit message above the changes and press Ctrl+Enter (macOS: ⌘+Enter) to commit them. If there are any staged changes, only those will be committed, otherwise all changes will be committed.

We've found this to be a great workflow. For example, in the earlier screenshot, only the staged changes to gulpfile.js will be included in the commit. A consecutive commit action could commit later changes to gulpfile.js, the deletion of yarn.lock, and changes to tests.js in a separate commit.

More specific Commit actions can be found in the More Actions... menu on the top of the Git view.

Cloning a repository

You can clone a Git repository with the Git: Clone command in the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)). You will be asked for the URL of the remote repository (for example on GitHub) and the parent directory under which to put the local repository.

For a GitHub repository, you would find the URL from the GitHub Clone or download dialog.

You would then paste that URL into the Git: Clone prompt.

Branches and Tags

You can create and checkout branches directly within VS code through the Git: Create Branch and Git: Checkout to commands in the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

If you run Git: Checkout to, you will see a drop-down list containing all of the branches or tags in the current repository.

The Git: Create Branch command lets you quickly create a new branch. Just provide the name of your new branch and VS Code will create the branch and switch to it.

Remotes

Given that your repository is connected to some remote and that your checked out branch has an upstream link to a branch in that remote, VS Code offers you useful actions to push, pull and sync that branch (the latter will run a pull command followed by a push command). You can find these actions in the More Actions... menu.

VS Code is able to periodically fetch changes from your remotes. This enables VS Code to show how many changes your local repository is ahead or behind the remote. Starting with VS Code 1.19, this feature is disabled by default and you can use the git.autofetchsetting to enable it.

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 automatic fetching via the git.autofetchsetting to reduce the number of prompts you get.

Git Status Bar actions

There is a Synchronize Changes action in the Status Bar, next to the branch indicator, when the current checked out branch has an upstream branch configured. Synchronize Changes will pull remote changes down to your local repository and then push local commits to the upstream branch.

If there is no upstream branch configured and the Git repository has remotes set up, the Publish action is enabled. This will let you publish the current branch to a remote.

Gutter indicators

If you open a folder that is a Git repository and begin making changes, VS Code will add useful annotations to the gutter and to the overview ruler.

• A red triangle indicates where lines have been deleted
• A green bar indicates new added lines
• A blue bar indicates modified lines

Merge conflicts

Merge conflicts are recognized by VS Code. Differences are highlighted and there are inline actions to accept either one or both changes. Once the conflicts are resolved, stage the conflicting file so you can commit those changes.

Viewing diffs

Our Git tooling supports viewing of diffs within VS Code.

Tip: You can diff any two files by first right clicking on a file in the Explorer or OPEN EDITORS list and selecting Select for Compare and then right-click on the second file to compare with and select Compare with 'file_name_you_chose'. Alternatively from the keyboard hit ⇧⌘P (Windows, Linux Ctrl+Shift+P) and select File: Compare Active File With and you will be presented with a list of recent files.

Diff editor review pane

There is a review pane in the Diff editor which presents changes in a unified patch format. You can navigate between changes with Go to Next Difference (F7) and Go to Previous Difference (⇧F7 (Windows, Linux Shift+F7)). Lines can be navigated with arrow keys and pressing Enter will jump back in the Diff editor and the selected line.

Note: This experience is especially helpful for screen reader users.

Git output window

You can always peek under the hood to see the Git commands we are using. This is helpful if something strange is happening or if you are just curious. :)

To open the Git output window, run View > Output and select Git from the drop-down list.

Initialize a repository

If your workspace isn't under Git source control, you can easily create a Git repository with the Initialize Repository command. When VS Code doesn't detect an existing Git repository, you will see a No source control providers registered. message in the Source Control view and the Initialize Repository command will be available on the title bar. You can also run the Git: Initialize Repository command from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

Running Initialize Repository will create the necessary Git repository metadata files and show your workspace files as untracked changes ready to be staged.

VS Code as Git editor

When you launch VS Code from the command line, you can pass the --wait argument to make the launch command wait until you have closed the new VS Code instance. This can be useful when you configure VS Code as your Git external editor so Git will wait until you close the launched VS Code instance.

Here are the steps to do so:

1. Make sure you can run code --help from the command line and you get help.
   • if you do not see help, please follow these steps:
     • macOS: Select Shell Command: Install 'Code' command in path from the Command Palette.
     • Windows: Make sure you selected Add to PATH during the installation.
     • Linux: Make sure you installed Code via our new .deb or .rpm packages.
2. From the command line, run git config --global core.editor 'code --wait'

Now you can run git config --global -e and use VS Code as editor for configuring Git.

VS Code as Git diff tool

Add the following to your Git configurations to use VS Code as the diff tool:

This leverages the --diff option you can pass to VS Code to compare 2 files side by side.

To summarize, here are some examples of where you can use VS Code as the editor:

• git rebase HEAD~3 -i do interactive rebase using VS Code
• git commit use VS Code for the commit message
• git add -p followed by e for interactive add
• git difftool <commit>^ <commit> use VS Code as the diff editor for changes

Working with pull requests

Visual Studio Code also supports pull request workflows through extensions available on the VS Code Marketplace. Pull request extensions let you review, comment, and verify source code contributions directly within VS Code.

Tip: Click on an extension tile to read the description and reviews in the Marketplace.

Next steps

• Intro Video - Git Version Control - An introductory video providing an overview of VS Code Git support.
• Basic Editing - Learn about the powerful VS Code editor.
• Code Navigation - Move quickly through your source code.
• Debugging - This is where VS Code really shines
• Tasks - Running tasks with Gulp, Grunt and Jake. Showing Errors and Warnings
• Source Control API - If you want to integrate another Source Control provider into VS Code, see our Source Control API.

Common questions

I initialized my repo but the actions in the ... menu are all grayed out

To push, pull, and sync you need to have a Git origin set up. You can get the required URL from the repository host. Once you have that URL, you need to add it to the Git settings by running a couple of command-line actions. For example:

My team is using Team Foundation Version Control (TFVC) instead of Git. What should I do?

Use the Azure Repos extension and this will light up TFVC support.

Why do the Pull, Push and Sync actions never finish?

This usually means there is no credential management configured in Git and you're not getting credential prompts for some reason.

You can always set up a credential helper in order to pull and push from a remote server without having VS Code prompt for your credentials each time.

How can I sign into Git with my Azure DevOps organization which requires multi-factor authentication?

There are now Git credential helpers that assist with multi-factor authentication. You can download these from Git Credential Manager for Mac and Linux and Git Credential Manager for Windows.

I have GitHub Desktop installed on my computer but VS Code ignores it

VS Code only supports the official Git distribution for its Git integration.

I keep getting Git authentication dialogs whenever VS Code is running

VS Code automatically fetches changes from the server in order to present you with a summary of incoming changes. The Git authentication dialog is independent from VS Code itself and is a part of your current Git credential helper.

One way to avoid these prompts is to set up a credential helper which remembers your credentials.

Another option is to disable the auto fetch feature by changing the following setting: 'git.autofetch': false.

Can I use SSH Git authentication with VS Code?

Yes, though VS Code works most easily with SSH keys without a passphrase. If you have an SSH key with a passphrase, you'll need to launch VS Code from a Git Bash prompt to inherit its SSH environment.