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. 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.
Sourcetree vs github pdf#
API references, and hundreds of sample code examples on GitHub to help developers precisely create and define PDF workflow solutions.
Sourcetree vs github software#
If I remove the password from the ssh key, this prompt doesn't come up. Compare price, features, and reviews of the software side-by-side to make the best choice for your business.
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. I've heard of other solutions like GitKraken, SourceTree and Smart Git. So I went with VS Code extension GitLens and I find version control much easier now. 1 superpower: A user interface to match GitKraken or SourceTree but built directly into VS Code to avoid context switching. 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). I used GitHub Desktop at first, tho moved away as I wanted some integrated solution. Git Graph has to be the most visually appealing way to interact with Git in VS Code, seeing the commit tree like this can help a lot when performing more complex git operations. 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. GitKraken allows users to create pull requests and click-to-view PRs on GitHub, GitLab, Bitbucket, and Azure DevOps. The problem for me seemed to be the order of setup between SourceTree and GitHub. It seems that you’re out of luck if you’re using Fork with GitLab or Bitbucket repos when it comes to pull requests.
0 kommentar(er)
