While working with git you can either enter username and password at each time you perform operations like git pull, push, etc. In the following example, I will be using github repository for remote with local repos on my Mac. I will also be using my own account and company user account to access two different github accounts and their respective repos.
One account only and access to its respective repositories.
Here just modify your ~/local_repo/.git/config file to either use https or ssh connection. Typical config looks like
By default when cloning is done with git clone command the config file generated will have entry of "url = https://github.com" (assuming you are cloning from github repo). See how to switch from https to ssh for a given repo or you can comment out the line as above and enter "ssh" link shown above in the example. Git config (git_config) has too many options and you can control different aspects of git behavior.
Among many but another scenario is when using two or more different github accounts from the same computer/system. Under this ~/.ssh/config file will be useful. Here ssh setup is required and https doesn't help much.
Other variations would be multiple accounts with different service providers not just github. This is little bit easier than having multiple accounts with same service providers.
Example: Github two accounts - doe_work and doe_personal and for each account you create two separate ssh keys with ssh-keygen.
> ssh-keygen -t rsa -f ~/.ssh/id_rsa_doe_work_git -C "Job new_key doe@company.com"
> ssh-keygen -t rsa -f ~/.ssh/id_rsa_doe_personal -C "Personal key"
Now configure both accounts to use ssh and its config - ssh_config. Important section in ssh_config is the "host" which is a string pattern to match in the config file to get it's respective options/ variables. You obviously should add the newly created public keys to github under settings->SSH Keys->Add SSH Key. Sample pub key for above.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDdnbxKkCrYUv3YbutC2Dw6jIhQWLNIzNA3Ec6inlmrngwB33fCaEP4ZiOzPq8A0BRBCyV HYhC3txA9Jn1tRXVZ4tUGEslvN2qF2HNXJhSx8V5Vk1r3LmWe1uehOjAekSK0apELpkafSwigzgkm9oAmbNQ5p0N1e8ar/TXbOOzWVMRu9K G/fILuHf90UZ4H5hOrZov9eZSwabnSMvORirizFXYZPp/FQ30fV3wZJKJoNnmOY+/txjnNc+mikYiezjeA66vWlDGfJQ+Xlb+i1bnXoxBfv hrE/nSuSUVNmGy0bYPOFwbxPrnz0jFGCgdUh7KfKD2yE/gc0abhW0nyxkP Job new_key doe@company.com
The three configuration files discussed are used by git to perform handshake with remote server and authenticate for each of git pull, push, fetch etc.
Simple setup:
One account only and access to its respective repositories.
Here just modify your ~/local_repo/.git/config file to either use https or ssh connection. Typical config looks like
DW Schema Sizes
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true ignorecase = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* # url = https://github.com/USER_OR_ORG_NAME/REPO.git url = ssh://git@github.com/USER_OR_ORG_NAME/REPO.git [branch "master"] remote = origin merge = refs/heads/master ... ...With command line git pull/push and ssh pub-key setup at github.com. See how to provide the pub-key to github. If you already have a ssh key and you would like to use the same just add entry in the ~/.ssh/config file with corresponding entries. See below for more details on how to do this.
By default when cloning is done with git clone command the config file generated will have entry of "url = https://github.com" (assuming you are cloning from github repo). See how to switch from https to ssh for a given repo or you can comment out the line as above and enter "ssh" link shown above in the example. Git config (git_config) has too many options and you can control different aspects of git behavior.
Multiple account setup:
Among many but another scenario is when using two or more different github accounts from the same computer/system. Under this ~/.ssh/config file will be useful. Here ssh setup is required and https doesn't help much.
Other variations would be multiple accounts with different service providers not just github. This is little bit easier than having multiple accounts with same service providers.
Example: Github two accounts - doe_work and doe_personal and for each account you create two separate ssh keys with ssh-keygen.
> ssh-keygen -t rsa -f ~/.ssh/id_rsa_doe_work_git -C "Job new_key doe@company.com"
> ssh-keygen -t rsa -f ~/.ssh/id_rsa_doe_personal -C "Personal key"
Now configure both accounts to use ssh and its config - ssh_config. Important section in ssh_config is the "host" which is a string pattern to match in the config file to get it's respective options/ variables. You obviously should add the newly created public keys to github under settings->SSH Keys->Add SSH Key. Sample pub key for above.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDdnbxKkCrYUv3YbutC2Dw6jIhQWLNIzNA3Ec6inlmrngwB33fCaEP4ZiOzPq8A0BRBCyV HYhC3txA9Jn1tRXVZ4tUGEslvN2qF2HNXJhSx8V5Vk1r3LmWe1uehOjAekSK0apELpkafSwigzgkm9oAmbNQ5p0N1e8ar/TXbOOzWVMRu9K G/fILuHf90UZ4H5hOrZov9eZSwabnSMvORirizFXYZPp/FQ30fV3wZJKJoNnmOY+/txjnNc+mikYiezjeA66vWlDGfJQ+Xlb+i1bnXoxBfv hrE/nSuSUVNmGy0bYPOFwbxPrnz0jFGCgdUh7KfKD2yE/gc0abhW0nyxkP Job new_key doe@company.com
... ServerAliveInterval 60 ServerAliveCountMax 60 ... Host github.com HostName github.com # User doe_work IdentityFile ~/.ssh/id_rsa_doe_work_git ... Host github-mine HostName github.com # User doe_personal IdentityFile ~/.ssh/id_rsa_doe_personal ... Now in each repo change/.git/config to use the above ssh/hosts. [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = ssh://git@github.com/USER_OR_ORG_NAME/REPO.git and [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = ssh://git@github-mine/USER_OR_ORG_NAME/REPO.git
The three configuration files discussed are used by git to perform handshake with remote server and authenticate for each of git pull, push, fetch etc.
