attribution settings should also govern the CI-monitor PR reply footer

Open 💬 0 comments Opened Jul 2, 2026 by kim-liedtke

Summary

attribution.pr: "" in settings.json hides the attribution block in PR descriptions, but the CI monitor's review-comment flow still instructs the model to append an attribution footer to every PR thread reply:

_🤖 Addressed by Claude Code_

There is no documented setting that suppresses this footer. It is injected via the ci-monitor event prompt ("End each reply with the line ..."), so it bypasses the attribution settings entirely.

Steps to reproduce

  1. Set in ~/.claude/settings.json:

``json
{ "attribution": { "commit": "", "pr": "" } }
``

  1. Open a PR from a session, receive a bot/reviewer inline comment, and let the CI-monitor event drive the fix.
  2. The model addresses the comment and, following the event instruction, posts a thread reply ending with the "Addressed by Claude Code" footer.

Expected: with attribution.pr set to empty, no Claude Code branding is appended to anything posted to GitHub on the user's behalf, including thread replies.
Actual: the footer is appended because the instruction comes from the event template, not from the attribution-aware code path.

Why it matters

Thread replies post under the user's own GitHub account. Appending vendor branding the user explicitly disabled overrides their disclosure choice; whether and how to label AI-written replies should follow the same setting that governs commits and PR bodies.

Suggested fix

Have the CI-monitor event template respect attribution.pr (or a dedicated attribution.reply) and omit the footer instruction when it is set to an empty string.

Checked docs (settings, code-review, github-actions, channels) for an existing switch; none found.

View original on GitHub ↗