Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
SoureTree seems to choose the first SSH key in Pageant list and attempt to use that with all my repositories. This doesn't work for some which use a different key (the second one in the list).
I'm not sure how to tell SourceTree via the git config to use the second key?
Have you tried to create a /.ssh/config file and add the following:
Host myhostname HostName bitbucket.org IdentityFile ~/.ssh/id_rsa # Default address: email@example.com:accountname/reponame.git # Alias address: git@<Host>:accountname/reponame.git # Usage: git@myhostname:accountname/reponame.git Host somethingelse HostName bitbucket.org IdentityFile /var/www/id_rsa.something # Default address: firstname.lastname@example.org:accountname/reponame2.git # Alias address: git@<Host>:accountname/reponame2.git # Usage: git@somethingelse:accountname/reponame2.git
Please, notice that in the sample above I have created two ssh key-pairs and I have saved them in different locations.
Host myhostname -> git@myhostname:accountname/reponame.git
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs