[BUG] Claude Code ignores git.includeCoAuthor setting in settings.json

Resolved 💬 2 comments Opened Jan 20, 2026 by alexattia Closed Jan 20, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code is not respecting the git.includeCoAuthor and git.includePRFooter configuration settings when creating commits and pull requests. Despite explicitly setting these to false in the settings file, Claude Code still adds co-author attribution lines.

What Should Happen?

When git.includeCoAuthor is set to false, Claude Code should:

NOT add any Co-Authored-By: lines to commit messages
Respect the user's preference for attribution

When git.includePRFooter is set to false, Claude Code should:

NOT add attribution footers to PR descriptions
Respect the user's preference for attribution

The settings in ~/.claude/settings.json should be checked and honored before creating any commits or PRs.

Error Messages/Logs

Steps to Reproduce

Create/edit ~/.claude/settings.json with the following configuration:

json{
"git": {
"includeCoAuthor": false,
"includePRFooter": false
}
}

Launch Claude Code from a git repository:

bashcd /home/alex/MyRepo
claude code


3. Ask Claude to implement a feature and create a commit/PR

4. Observe that the commit message includes:

Co-Authored-By: Claude <noreply@anthropic.com>

And the PR description includes attribution footer, despite the settings explicitly disabling this.

<img width="1282" height="298" alt="Image" src="https://github.com/user-attachments/assets/4861cf41-0449-4825-a41a-00026fa90f27" />

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.12

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Xterm

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗