You may then be prompted further when accessing a repo for the first time to navigate to a URL to authorise it for that repo via a browser. Using the Personal Access Tokens were now successful for me across all repos in and Enterprise.Īs a side note, if your GitHub Enterprise uses SSO for authentication then you will need to Enable SSO for you Personal Access Token There’s a clue to some changes during the upgrade process that a new Git Credential Manager will be used:Īfter upgrade there is a different dialogue window when authenticating: Initially I had v2.27.0.windows.1 so upgraded to the latest as of writing this post v2.30.0.windows.2. A later version of git for Windows is required in order to use the new method. This StackOverflow post cleared things up. I couldn’t see why this was causing me an issue since I was trying to use a personal access token. Turns out the GitHub recently deprecated basic authentication using a username and password in favour of a personal access token. Login failed use ctrl+c to cancel basic credential prompt To existing repos on using an existing Personal Access Token or authenticating to a new repo using a different account on an instance of GitHub Enterprise using a new Personal Access Token, I would receive a combination of the following errors: When re-authenticating via the prompted login window: While following this guide to migrate to using multiple GitHub HTTPS accounts on Windows from a single user account I have used for years, I had to remove my existing credentials from Windows Credential Manager.

PowerShell Brickset Module version 2.0.1+: Downloading Lego Instructions.Authenticating to GitHub using Git for Windows and a Personal Access Token fails.

Automating SonarCloud with PowerShell – Part 1 Introduction.

Automating SonarCloud with PowerShell – Part 2 Onboarding a Project.

Automating SonarCloud with PowerShell – Part 3 Onboarding a User.

Sourcetree app git powershell