![]() Try again, you should have another opportunity to enter authentication credentials. Until Sourcetree is updated to include a later version of it's embedded version of Git (2.26.2 is several releases behind now), I recommend installing Git for Windows standalone, and then set Sourcetools to use the "system version" of Git. Go to Tools -> Options in SourceTree and then go to the Authentication tab on the Options popup. 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 ' Remote: Invalid username or password.Writing objects: 100% (3/3), 332 bytes | 332.00 KiB/s, done. ![]() An error occurred while sending the request. Push -v -tags origin master:master fatal: HttpRequestExceptionĮncountered. no-optional-locks -c credential.helper= -c credential.helper="C:/Users//AppData/Local/ATLASS~1/SOURCE~1/GIT_EX~1/GIT-CR~1.EXE" ![]() I also created an app password and tried using that as the password with combinations of the username and email, but no joy. I have tried using the username and email, I've even changed the password of the account but still no joy. To clarify I can log in to the repo using my browser just fine but when I push to it from Sourcetree and I enter the same details into the prompt box it fails to authenticate. This may seem like a bit of a rudimentary issue, but I cannot seem to push from Sourcetree (windows) to a bitbucket repo for which my user is the owner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |