4 ms·
I don't mean to be a fuddy-duddy, but I don't get it... How is this better/worse than doing... git config user.name Foobar git config user.emai
by 32bitkid 11y ago
I don't mean to be a fuddy-duddy, but I don't get it... How is this better/worse than doing...
git config user.name Foobar
git config user.email foo@bar.com
...which will set that config variable for the current repository only -- not global. I ended up do the a similar thing for a simple git pairing tool[1] that would let you set your name to two people, so that one could discern the pair from the commit logs
[1]:https://github.com/32bitkid/git-working-with https://github.com/32bitkid/git-working-with
- prydonius 11y agoI built karn to avoid situations where I've forgotten to update the config after cloning a new repository. With karn, any repository under `~/Work`, for example, will automatically be configured to use the correct identity. Also, since it's all in one configuration file, that makes it really easy to maintain and keep it in sync with multiple machines.
- detaro 11y agoIt stops you from forgetting to do that. Especially for small, quick things like spell-fix PRs to random github projects it has happened to me that I forgot to set the right user before making and publishing commits.