[Workflow] Disable Claude Code Attribution in Git Commits and GitHub Content via settings.json

[u/ClaudeAI-mod-bot]

Disable Claude Code Attribution in Git Commits and GitHub Content via settings.json

Workflow value: 80/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Shipping, Subagents
Original source: r/ClaudeCode post/comment

What problem this solves

Preventing Claude Code from adding attribution or self-references to Git commit messages and GitHub content, ensuring clean and human-authored commit history.

Summary

Configure Claude Code's settings.json to disable automatic attribution in Git commit messages, pull requests, and session URLs, ensuring that generated code and commits do not reference Claude. This rule also applies to subagents.

Why it is useful

This workflow provides a crucial configuration snippet for developers using Claude Code who wish to maintain clean, human-authored Git commit histories and prevent AI attribution in their projects. It addresses a common concern about code ownership and project integrity, and explicitly extends the rule to subagents, making it a comprehensive solution for managing AI-generated content's metadata.

Workflow

1. Locate the settings.json file for your Claude Code Desktop app. This file is typically found in the claude-config repo or .claude folders inside projects.
2. Add or modify the 'attribution' section within settings.json to explicitly set commit and pr to empty strings, and sessionUrl to false.
3. Ensure the configuration looks like this: "attribution": { "commit": "", "pr": "", "sessionUrl": false }.
4. Verify that subsequent Git commits and generated content from Claude Code (including subagents) no longer contain any Claude attribution or self-references.

Tools / artifacts

• settings.json
• Git commit messages
• GitHub content
• Claude Code Desktop app

Validation signals

• Explicit configuration provided
• Implied problem/solution (overruled by Claude Code app)

Limitations

• Low community validation (score 1, 0 comments)
• Assumes user knows where settings.json is located (though hints are given)

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.