![]() So now Sourcetree will give me a single password prompt, and entering the ssh private key password will work. In this tutorial, were using OSX 10.9.5 and SourceTree 2.0.4. So my final solution was 1) keep the passwords on the ssh keys 2) make all these passwords the same. SourceTree is a powerful Git and Mercurial desktop client for developers on Mac or Windows. In fact, I am guessing Sourcetree is doing exactly the same in the background. In fact, if you add passwords to the dialog in the same order as you would in the shell to an ssh-add, this would work. Think of it this way - if you have a fresh shell in your system, and you just started ssh-agent up, and ran ssh-add, what are the password prompts that you get? For every such password prompt, Sourcetree will give you this dialog box. If you have multiple ssh private keys which have different passwords, Sourcetree will give you a password prompt for each password. However since I wanted the password to be there, I kept investigating why it wasn't accepting my ssh key password. View topic Pull changes from your repository on Bitbucket Next on your list of space station administrator activities, you need to file out a request for new supplies. If I remove the password from the ssh key, this prompt doesn't come up. Use Sourcetree to clone your repository to your local system without using the command line. Set the environment variables GCMTRACE1 and GITTRACE1 and re-run your Git command. In my case, the password that Sourcetree was asking for was for the ssh private key password. Sourcetree with github Issue 238 git-ecosystem/git-credential-manager GitHub git-ecosystem git-credential-manager on petegoz commented on edited From a terminal, run git remote -v to show your remote URL. Re-install SourceTree using all the correct credentials, point to the right repository and such.Īfter all this, SourceTree asked for my GitHub credentials twice, with two different dialog boxes, then stopped and worked! No more endless loop. Make sure your GitHub is setup the way you desire (for me, I also created and saved an SSH key that I used for SourceTree setup). Go up one level to ".\Local" and delete the "Atlassian" folder as well. I eventually ended up at "C:\Users\myusername\AppData\Local\SourceTree". Mine forked at "C:\Users\myusername\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Atlassian" where the shortcut pointed to another shortcut. The non-obvious bit was needing to delete the actual program files manually.įrom any "SourceTree.exe" shortcut, open file location. I setup SourceTree first and just clicked all the "setup later" options.Īn easy fix - Uninstall and re-install SourceTree. The problem for me seemed to be the order of setup between SourceTree and GitHub.
0 Comments
Leave a Reply. |