Explore >> Select a destination
|
You are here 
|
www.integralist.co.uk | ||
| | | | |
zzamboni.org
|
|
| | | | | via http://www.freshblurbs.com/blog/2013/06/22/github-multiple-ssh-keys.html#tldr Since Github doesn't allow us to reuse an SSH Key, the only sane solution is to jump through some hoops and generate + use multiple keys on the server itself. Let's look at some effective approaches of doing that. Short version: define multiple hosts in the SSH config file for each repository, which use different SSH keys, then you can assign different deploy keys to each repo. But read the whole article for the full details. | |
| | | | |
taylorbrazelton.com
|
|
| | | | | ||
| | | | |
www.micah.soy
|
|
| | | | | Working on many projects across multiple identities can be difficult to manage. This is a procedure for leveraging git aliases to set an identity at the project level. | |
| | | | |
jinyuz.dev
|
|
| | | Suppose that you have a full time job at Amazon, and you want to separate your git commit emails from Amazon and your personal projects. Setting up ~/.gitconfig $ touch ~/.gitconfig For our personal projects, we will use the ~/.gitconfig file with the following content: [user] name = James Banned email = james.banned@gmail.com [includeIf "gitdir:~/Work/"] path = ~/.gitconfig.work The includeIf basically means that include this config if I'm inside the ~/Work/ directory. | ||
