I don't post my code to Github because I still couldn't figure out how to switch SSH keys for 2 different git servers smoothly.
If you're using OpenSSH, the
IdentityFileconfiguration directive selects the SSH key to use.Add something like this to your SSH config file (
~/.ssh/config):Host github.com IdentityFile ~/.ssh/github_rsa Host gitlab.com IdentityFile ~/.ssh/gitlab_rsaThis will use the
github_rsakey for repositories hosted atgithub.com, and thegitlab_rsakey for repositories hosted atgitlab.com. Adjust as needed for your key names and hosts, obviously.you dont have to switch
git will automatically select one that works
I have the same password protected ssh key for every git site i am on tho. The sites only know the public key so its fine.
I don't know how to switch keys
"just use the same key"
bruh the Stack Overflow energy
have at it!
taken from Gitlab's manual page for creating a key, but i wonder what else could be done to expand on it.
#~/.gitconfig [includeIf "hasconfig:remote.*.url:https://gitlab.com/**"] path = /path/to/gitlab.gitconfig [includeIf "hasconfig:remote.*.url:https://github.com/**"] path = /path/to/github.gitconfig
#example gitlab gitconfig from the included path [user] name = Your Name email = [email protected] signingkey = 0000999988887777 [commit] gpgsign = true
if all works well, Git should be able to automatically use the selected key depending on the repo's stated remote server.
Companies spend a lot of time documenting and reviewing and discussing to release one feature in the meantime you release 100. And if it's too much spaghetti, you can rerelease new 100.
And lazy. Maybe that's why my code is not so good.
