Skip to content

Disable Claude Code commit and PR attribution - #136

Draft
Protonmatter wants to merge 1 commit into
masterfrom
mkang/eloquent-ptolemy-ic2wah
Draft

Protonmatter wants to merge 1 commit into
masterfrom
mkang/eloquent-ptolemy-ic2wah

Conversation

@Protonmatter

@Protonmatter Protonmatter commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Outcome

Claude Code sessions in this repository stop adding attribution to commits and pull request descriptions. Today they add a Co-Authored-By trailer, a "Generated with Claude Code" PR footer and a Claude-Session link. After this change they add none of these.

Specification and traceability

  • Requirements: Not applicable (tooling configuration only)
  • RFC: Not required: no product or contract change
  • ADR: Not required: no architectural change
  • Governing specification: Claude Code settings reference, attribution key (https://code.claude.com/docs/en/settings-reference.md)
  • Non-goals: the footer Claude Code adds to GitHub comments and reviews it posts. No setting for that footer is documented.

Correctness and risk

  • Inputs, outputs, and failure behavior: adds attribution: {commit: "", pr: "", sessionUrl: false} to .claude/settings.json. An empty string hides that attribution line.
  • Compatibility or migration: the existing marketplace and plugin entries are unchanged. includeCoAuthoredBy is deprecated and is not used here.
  • Scientific/accuracy/provenance impact: none.
  • Privacy/security/dependency impact: none.
  • Release risk, monitoring, and rollback:
    • The docs say a committed project .claude/settings.json is read in single-repo cloud sessions.
    • They do not explicitly confirm commit/pr behavior in cloud sessions, so confirm on the next session.
    • Rollback: revert this commit.

UI and UX

Not applicable.

Validation evidence

  • Unit tests cover positive, boundary, and negative cases where applicable. (Not applicable)
  • Contract/integration tests cover producer-consumer boundaries where applicable. (Not applicable)
  • Browser end-to-end and visual assertions cover user-visible rendering where applicable. (Not applicable)
  • Deterministic generation/accuracy checks pass where applicable. (Not applicable)
  • Rust, Python, Node, and whole-web coverage gates remain at least 90%. (Unaffected; left to CI)
  • Locally unavailable checks are named and left to required CI.

Commands and results:

python3 -m json.tool .claude/settings.json   -> valid JSON
python3 tools/validate_sdlc.py               -> OK: SDLC, 27 requirements, RFCs, evidence paths, and workflows validate.

Documentation

  • README and contributor instructions remain accurate.
  • Specifications, requirements, RFC/ADR, and implementation plan are updated. (None affected)
  • Operations, readiness, status, roadmap, and handoff are updated when affected. (None affected)
  • User-visible claims and help match implemented behavior.

Note: .claude/ is listed in .gitignore, but settings.json is already tracked, so changes to it are still committed.

Set attribution.commit and attribution.pr to empty strings and
attribution.sessionUrl to false in the shared project settings, so
Claude Code sessions in this repository omit the Co-Authored-By
trailer, the PR footer and the session link.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants