|
You are here |
blog.kulman.sk | ||
| | | | |
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. | |
| | | | |
blog.bdw.li
|
|
| | | | | Using different machines to work on some git files can result in missing signign keys and some headache. | |
| | | | |
wittchen.io
|
|
| | | | | Short introduction Sometimes people need to specify multiple values for single .gitconfig file or they want to share just part of the configuration between two machines. There are different approaches for that. I can show you mine. Different configs for different Operating Systems On my private computer, I use Linux. I use Git for my private projects and I use my private e-mail address there. At the same time, I use Git at work on macOS with exactly the same Git configuration, but with a different e-mail... | |
| | | | |
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. | ||