Check that both of your personal and work account have the correct public keys added for access.Save the private and public keys for later use. Fresh Start: If you want to start from scratch, generate two new keys in PuttyGen.rsa to the file name so you can differentiate from your ppk format private key. Existing Keys: If you previously used Putty, load your ppk into PuttyGen and convert it to Open SSH format using the conversion option.We'll be implementing the scenario where you have 1 work and 1 personal Github/Bitbucket/Gitlab account
Obviously this is Windows and Git specific.
I have recorded the steps I took to guarantee a sure-fire process to achieve functional Windows Sourcetree with Git working on multiple SSH keys.
#Sourcetree github ssh how to#
What I found most interesting was that every document explaining how to do this omitted one or two critical details. This week we have officially adopted two-factor authentication for our revision control so guess what?!Īs the documentation clearly states, this breaks HTTPS login for Git!Īll things considered this is a small issue but getting multi-key SSH configured was surprisingly difficult. You must be a registered user to add a comment. I noticed the one generated with the 'generate ssh key' inside SourceTree is longer than my default key.
To avoid SSH key issues we just use simple HTTPS to clone our repos down instead of hassling with multiple SSH keys. For my setup, the remote origin url must not include ssh://. Sometimes we work from our personal computers and being developers, we have our own projects outside of work that are associated with different credentials. 149150 SSH (Secure Shell), 294, 295 connecting to ESXi console. We use Git and Sourcetree, primarily on the Windows operating system and love it 99% of the time. retrieving entity from, 389 SourceTree client for GitHub, 879 cloning repository.
0 kommentar(er)
