![]() ![]() So now Sourcetree will give me a single password prompt, and entering the ssh private key password will work. 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. I could push to the other site like GitLab, but I couldn't find a way to change the password for another GitHub account. 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. First time SourceTree ask me to enter password, but when I wanted to push to my other GitHub account it doesn't ask me to enter the password and just show this error: I couldn't find a way to change the password. 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. For more information about it, see this blog post.The problem for me seemed to be the order of setup between SourceTree and GitHub. with git config -system credential.helper manager-core) but is also included in the current Git for Windows 2.28.0. It can be installed standalone (should be activated automatically, otherwise activate e.g. But don't despair, with Microsoft now going Core, there is a shiny new project called GCM Core, which seems to handle password changes correctly. ![]() Update (): GCM4W seems to be more or less abandoned (last release more than a year ago, only one commit to master since then named, I kid you not, "Recreate the scalable version of the GCM Logo"). In Microsoft's Git Credential Manager this is a known issue that may be fixed as soon as early 2019 (so don't hold your breath). Or put this in a batch file for your colleagues: cmdkey /delete:git. You may have a hard time finding it in your localized Windows version, but luckily you can start it from the good old Windows + R run dialog with control keymgr.dll or control /name Microsoft.CredentialManager (or rundll32.exe keymgr.dll, KRShowKeyMgr if you prefer the classic look). The instant solution is to delete or fix your Git entries in the Windows Credential Manager. ![]() FWIW, I stumbled over this very same problem (and my boss too, so it got more intense). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |