ci: let the claude bot trigger the PR audit workflows - #4392
Conversation
claude-code-action rejects any non-human actor unless it is named in allowed_bots, so PRs opened by the claude app failed both the agent instructions audit and the REVIEW.md drift audit before Claude ran, and landed with two permanently red checks and no audit coverage. Allowlists the bot by name rather than "*", so other bots (dependabot in particular) still cannot trigger these workflows. Both jobs already skip PRs whose head is not in this repo, so fork PRs remain excluded.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🧰 Additional context used🧠 Learnings (1)📚 Learning: 2026-05-12T14:34:38.795ZApplied to files:
🔇 Additional comments (2)
WalkthroughUpdated the Claude Code action configuration in two GitHub Actions workflows to include 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
PRs opened by the claude GitHub app fail both the agent instructions audit and the REVIEW.md drift audit before Claude gets a chance to run.
claude-code-actionrefuses any actor whose account type is notUserunless the actor is listed inallowed_bots:So those PRs land with two permanently red checks and no audit coverage at all. Both workflows already allowlist Devin; this adds the claude app alongside it.
Why this does not open the workflows up to outside contributors
allowed_botsis only consulted for non-Useractors. Humans, contributor or maintainer, take the separate write-permission path and are unaffected by what is in the list.Beyond that, both jobs are guarded by
github.event.pull_request.head.repo.full_name == github.repository, so a fork PR skips the job entirely, and they trigger onpull_requestrather thanpull_request_target, so a fork-triggered run would get no API key and a read-only token anyway.The bot is named explicitly instead of using
"*", which would let every bot trigger these audits, dependabot's PR stream included.