Github sourcetree windows8/14/2023 GCM Core supports OAuth-based authentication which is the requirement from GitHub now. GitHub recently () changed their authentication mechanisms to remove username/password-based authentication, that GCM4Windows used. This explains why you're seeing the older GCM4Windows prompts, and not GCM Core.Īs to why the older GCM4Windows no longer works with GitHub. The latest embedded version used by Sourcetools appears to be Git for Windows 2.26.2, which only includes the older, and now deprecated Git Credential Manager for Windows, not GCM Core. Is it the embedded version, or the system version? Which version of Git is being used by Sourcetools? Hi you open Sourcetools and go to: Tools > Options > Git, and scroll down to the "Git Version" section. The new GCM (GCM Core, this project) supports the new authentication mechanism GitHub now require, however Sourcetree isn't using it.Ĭan you please set the following environment variables, restart Sourcetree, and then upload the resulting log file? If that's the case, then the reason is that GitHub has removed the username/password-based authentication the older GCM for Windows used to use to create authentication tokens (see here). I assume that these are images of authentication prompts you're getting whilst using SourceTree, and that entering username/password(/2FA code) in these no longer works? Something went wrong in your reply of images with GitHub - I cannot see them. That error message comes from GCM for Windows: It looks like Sourcetree is using an old version of GCM (GCM for Windows). Logon failed, use ctrl+c to cancel basic credential prompt. no-optional-locks push -v -tags -set-upstream GitHub_Git_Test ![]() Git -c diff.mnemonicprefix=false -c core.quotepath=false This is what I get from Sourcetree when I try to push to To use Sourcetree, because that gives me much better visibility of branchesĪnd commits. Total 3 (delta 0), reused 0 (delta 0), pack-reused 0īranch 'master' set up to track remote branch 'master' from ' Voila – you can now clone, pull and commit into your Private GitHub repository, using Sourcetree.Writing objects: 100% (3/3), 332 bytes | 332.00 KiB/s, done. Edit your account – change Auth Type from OAuth to Basic and enter the token from the previous steps into the Password field.Now go back to the Accounts section in Sourcetree.Then copy the newly generated token as you make sure to use the Copy button on the right (as you might copy some space character if you do it manually).Give the permissions you would like Sourcetree to have, but make sure repo is checked (with all the sub-menus).Go to Personal Account Settings and create a new token, using the “Generate new token” button.Go to Account settings > Developer Settings.The problem seemed to be in the way the account is linked in Sourcetree. I spent some time reading the Atlassian forums (Sourcetree is an Atlassian product) and found a whole bunch of people dealing with the same problem. ![]() Now to the best part – resolving the issue. With this setup in place however, you can’t clone your Private repository, if you already have it in place – you cannot pull from it, and you also can’t push any changes. You can see thaht the Auth Type is set to OAuth by default. Then the account setup is done and you can see it in Sourcetree > Preferences > Accounts. When you do the initial setup of Sourcetree, you enter your GitHub account, a browser window opens automatically, you are logged into your GitHub account and grant access for Sourcetree.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |