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?
Using sourcetree with github windows#
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 '
Using sourcetree with github how to#
If you want to know how to do it, check this post where you can find a guide of the whole process.Writing objects: 100% (3/3), 332 bytes | 332.00 KiB/s, done. Depending on the number of commits you want to amend or if they are already pushed to the repository, you’ll find more useful to rebase your history or directly reset from a good state. I already did some commits with a wrong author… now what?ĭon’t worry these things happens, that’s why Git implements multiple ways to fix this problem. If you followed correctly those previous steps and the emails that you are setting in both computers match, you should be ready to start developing things. This means that you will see two users in the history when you check your commits in GitHub. If you use the second option, you will be signing your commit with an author different than the pusher of the commits. Make sure that you are using the option Use default author and your credentials are correct. The second thing you need to check is the box on the bottom where you can write your commit message: If it’s different from the identity you want to use for this repository, uncheck Use global user settings and add the right information. If you have set another default account, maybe you will have a different user information here. In Windows/Mac, go to Settings (at the top right) and move to the Advanced tab: Then, when you are ready to start committing some work, let’s check if your repository settings are properly set. Once you finish, you can start cloning your repository and work in your project normally. For example, having only one key can shared across multiple devices can be comfortable, but if one of your devices is exposed you will have to remove the key from your account, create a new one and reconfigure that in all of your computers. It’s not important what you choose here, but bear in mind that each options has it’s advantages or disadvantages. About the SSH key you have to take a decision, you can reuse the same key from the first computer in the second computer or create a new one and adding it in your Github account (or other).
0 kommentar(er)
