> I really wish someone would come up with some kind of "accept remote config" policy or some such thing. But there is a workaround: centralising the .gitconfi

> I really wish someone would come up with some kind of "accept remote config" policy or some such thing. But there is a workaround: centralising the .gitconfig in a repo, then symbolically linking it to your home directory, so it gets updated on every pull. I haven't done the experiment, but you might be able to do the same with your .git/hooks. If need be, you could even cron a git pull in that repo, or add it to your .bashrc, $profile for PowerShell or schedule a task. I agree, it is a bit of a pain.