You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Recently my team moved to GitLab and i have stumbled upon a blocker that prevents me from using SourceTree al all.
When trying to add GitLab account with SSH access to repository, sourcetree only supposes that name of an ssh RSA keypair will be id_rsa.pub / id_rsa. The problem is, id_rsa is already taken by another keypair on my computer that is used to connect to hundreds of systems. I have dedicated keypair for git access with different name, say git_rsa/git_rsa.pub and looks like SourceTree cannot allow me to use any custom name for a keypair.
To make it clear:
- i am NOT going to default id_rsa to gitlab for security reasons
- i am NOT going to make any symlinks, it's inconvenient
What i need is to be able to force SourceTree to use a keypair with name _different_ from id_rsa
Is there any kind of solution for that?