/explore
|
You are here 
|
jamesmead.org | ||
| | | | |
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... | |
| | | | |
lostfocus.de
|
|
| | | | | How do you nice people reading my blog handle your Github account(s)? I've had my "main" account @lostfocus for ages and used it for pretty much everything I needed to do on Github. Now with my current employer our accounts are put into the SSO system, so I created a second account which went through ... | |
| | | | |
raphael.medaer.me
|
|
| | | | | I work on many different Git repositories. For each of them I have a particular email address and sometimes a GPG key. Even the Git flow might be different; always --no-ff (or not), pull --rebase instead of merge,... | |
| | | | |
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. | ||
