Multiple Git Configs Per Directory

Mon, 30 Mar 2026 00:00:00 +0000

The Problem

You have a personal GitHub and a work GitLab (or multiple work accounts). Your global ~/.gitconfig has your personal email. You clone a work repo, make a commit, push — and now your personal email is in the company git history. haha-haha classic..

You could run git config user.email in every new repo you clone. But you’ll forget. You always forget. But this is a boring routine, why do this?

Disable Co-Authored-By Claude in Git Commits

Fri, 27 Feb 2026 00:00:00 +0000

Solution

Open ~/.claude/settings.json with your favorite editor and add this to your json config. This is taken from Claude docs¹

{
 // ...
 "attribution": {
 "commit": "",
 "pr": ""
 }
}

Why

This actually makes no sense and I agree with Rob Pike’s take on that². It just adds non-readable boilerplate that does not add any value to the git commit. If it was committed by some guy I expect him to take responsibility of that commit, not some excuse like “that was written by Claude, sorry I didn’t check”. So it makes no sense at all, we are blind to that string anyway. Git commits should be atomic, simple and readable, not overwhelmed by nonsense. The trick above will help you with that.

Git on @zhisme :: signal over noise

Multiple Git Configs Per Directory

The Problem

Disable Co-Authored-By Claude in Git Commits

Solution

Why