

- GIT WINDOWS ISSUES TO RUNNINGSOMEONEELSE SCODE CODE
- GIT WINDOWS ISSUES TO RUNNINGSOMEONEELSE SCODE PASSWORD
That way you will avoid having to type your password all the time and since it already seems to work, that’s what you should be using. The alternative is actually to use SSH for authentication. So you will have to use your username instead. Since you used Git will try to log in using the git username for which your password of course doesn’t work. If you use then you have preset the username Git will use for authentication: something. , and Git would then prompt you to enter both a username (your GitHub username) and your password. Usually, you would just use the URL without a username, e.g. When using the URL to connect to your remote repository, then Git will not use SSH as authentication but will instead try a basic authentication over HTTPS. That applies only for HTTPS URLS, SSH is not affected by this limitation. In that case, the password should be a PAT (personal access token) as seen in " Using a token on the command line". So make sure you are in the repo path when doing the git remote set-url command.Īs noted in Oliver's answer, an HTTPS URL would not use username/password if two-factor authentication (2FA) is activated. You could check git config -l in your repo: that url should be declared in the local config: /.git/config.

That's what I did in my ~/.gitconfig file that contains currently the following entries should not be in your global config (the one in ~/). Try to use or just git remote set-url origin OP Pellegrini Eric adds: Related is not an ssh url, it is an https one (which would require your GitHub account name, instead of ' git'). Re-attempt the command you were trying and use Personal Access Token in the place of your password.(Detailed guide on Creating a personal access token for the command line.) The command line prompt won't specify that you should enter your personal access token when it asks for your password.
GIT WINDOWS ISSUES TO RUNNINGSOMEONEELSE SCODE CODE
Password for Invalid username or password.Īfter 2FA is enabled you will need to enter a personal access token instead of a 2FA code and your GitHub password.įor example, when you access a repository using Git on the command line using commands like git clone, git fetch, git pull or git push with HTTPS URLs, you must provide your GitHub username and your personal access token when prompted for a username and password. After enabling Two Factor Authentication (2FA), you may see something like this when attempting to use git clone, git fetch, git pull or git push: $ git push origin master
