Explore >> Select a destination
|
You are here 
|
raphael.medaer.me | ||
| | | | |
blog.kulman.sk
|
|
| | | | | I use the same machines to work on both personal and work projects. I usually have to use a different Git identity for the work projects than for my personal projects. Previously I had my personal Git identity set globally and then used local Git configs to override it in work projects. This worked just fine but it was too much work. There is a better solution. Git config allows you to use, or better to say include, another Git config for a specific directory and all its subdirectories. I have all my pro... | |
| | | | |
garrit.xyz
|
|
| | | | | Generalist software developer writing about scalable infrastructure, fullstack development and DevOps practices. | |
| | | | |
jamesmead.org
|
|
| | | | | Using conditional includes in your git configuration | |
| | | | |
www.integralist.co.uk
|
|
| | | Introduction The Problem? The Solution Creating a new Key SSH Config Optional Shell Function Alternatives? Another Alternative Introduction I recently had an issue with my GitHub set-up which has since prompted me to write this post. The issue I had was dealing with multiple GitHub accounts via SSH on a single laptop. So I have a GitHub account under the username Integralist. This is a personal account, and up until recently I was also using it to access my work's private repos (BBC and BBC-News). | ||
