Every developer who manages more than one GitHub account knows this moment. You push code. GitHub accepts it. Then you check the commit history and see it was pushed under your personal account — not your work one. Or worse, a client's repository now has your personal email baked into the commit forever. You run git config user.email and realize you forgot to set it for this repo. Again. This happens because Git doesn't know which "you" is working right now. It just uses whatever global config you last set. If you're switching between a personal project, a day job, and a freelance client in the same day — you're one distracted moment away from a messy commit history. I've been that developer. Many times. The Workarounds Are Painful The common solutions exist, but none of them feel right: Per-repo config — You have to remember to run git config user.email every single time you start working in a new repo. One forgotten step and you've already made a dirty commit.…