If you already have a company repository on your local machine, you must change the git conig file (keep reading).įirst, navigate to your company git project and run nano.

This approach is for newly cloned repositories, and then you are done. A git clone command will look like this: before: git clone after: git clone -airlibi:airlibi/project.git This has no impact on the github URL but tells our computer that the host for the repository is connected to the airlibi key. The last step in this is to tell GitHub to not fetch the company projects from but from -airlibi. Telling GitHub Company projects to use airlibi This config file tells the computer that we want to use the airlibi ssh key when accessing the host -airlibi. So add the following to the newly created config file: # GitHub Company Host -airlibi HostName AddKeysToAgent yes UseKe圜hain yes IdentityFile ~/.ssh/airlibi We only need to define the ones that are non- id_rsa, which is the default if nothing changes. Your computer doesn’t know that there is a new key called airlibi, and even if it knew, it wouldn’t trial and error through all the keys you have in. Now GitHub trusts the airlibi ssh key, but your computer will still send the id_rsa key when running any ssh git commands. Next, we use the airlibi.pub key to create the SSH key pair in our GitHub company account. Your identification has been saved in /Users/matsbauer/.ssh/airlibi Your public key has been saved in /Users/matsbauer/.ssh/airlibi.pub

This command will give us a new key named airlibi (or your company name or whatever you name it). Let’s say you already use this key for your private GitHub account, and you now need a key for your company account. This is the one Git knows to use when connecting to GitHub (or Gitlab). Here you will also find the standard key id_rsa. The error GitHub gives you when trying to use the same SSH key for two accounts Location of the SSH keysįirst, on Mac, we have a single location for SSH keys which is Users/username/.ssh.

Add ssh key to mac