So my final solution was 1) keep the passwords on the ssh keys 2) make all these passwords the same. 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. It's distributed version control allows developers to visualize code, review changesets, stash, cherry-pick between branches or commit with a single click.
#Sourcetree vs github for mac#
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. Sourcetree, by Atlassian, is a free version control client for Mac and Windows that works with Git and Mercurial repositories. 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. If I remove the password from the ssh key, this prompt doesn't come up. In my case, the password that Sourcetree was asking for was for the ssh private key password. 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 kommentar(er)
