/explore
|
You are here 
|
ianduffy.ie | ||
| | | | |
themythicalengineer.com
The Big Problem Imagine you have two GitHub accounts: one for personal use and one for work. You might be working on personal projects from your work laptop, but switching between these projects often requires manually updating your GitHub configuration: |
|
| | | | | ||
| | | | |
memo.mx
Be very carrefull in your setup : any misconfiguration make all the git config to fail silently ! Setup multiple git ssh identities for git Generate your SSH keys as per your git provider documentation. Add each public SSH keys to your git providers acounts. In your ~/.ssh/config, set each ssh key for each repository as in this exemple: Host github.com HostName github.com User git IdentityFile ~/.ssh/github_private_key IdentitiesOnly=yes Host gitlab.com Hostname gitlab.... |
|
| | | | | ||
| | | | |
jamesmead.org
Using SSH keys stored in 1Password on MacOS |
|
| | | | | ||
| | | | |
ryanharter.com
This is the second post in my Start to Finish series. You can check out my first post introducing the series and my tools here. What is SCM? SCM, or source code management, is a system that helps developers manage the source code for their projects. They have been around forever, things like CVS, Subversion (SVN) and now Git are the popular ones. SCMs allow you to version your source code, which is why they are also called Version Control Systems. |
|
| | | |||
