4 ms·
As soon as work or personal is more than one repo, that's annoying, and gets more annoying the more it is. You could also say 'why does global git config exist
by OJFord 5y ago
As soon as work or personal is more than one repo, that's annoying, and gets more annoying the more it is.
You could also say 'why does global git config exist at all, you can always just use .git/config on a per-repo basis'.
- selfhoster11 5y agoI'm pretty sure that it's a 10-20 minute job to write a Git subcommand wrapper that checks out a work vs personal project, and then symlinks the correct config file for the repo, if someone chose to go this route.
- shawxe 5y agoBut... how is this easier than the solution proposed by OP?
- selfhoster11 5y agoIt's not, but it's my response to the problem discussed by the parent comment.
- OJFord 5y agoSure, but that's more like a solution for implementing something like in OP for if it didn't exist in git itself, not the 'why not just use per-repo config' that I responded to.