chore: enable Claude issue trigger per org CI standard#53
Conversation
Add issues:[labeled] event trigger and claude label support so Claude can work issues autonomously — reading the issue, creating a branch, implementing the fix, and opening a PR. Matches the standard defined in petry-projects/.github#24. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 1 minutes and 25 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
There was a problem hiding this comment.
Pull request overview
Updates the repository’s Claude Code GitHub Actions workflow to match the org CI standard by enabling issue-label triggering and the permissions needed for issue-driven automation.
Changes:
- Add
issues: [labeled]trigger and gate execution on theclaudelabel. - Add
label_trigger: "claude"input for the Claude action to run autonomously on labeled issues. - Increase
contentspermission towriteand pinanthropics/claude-code-actionto v1.0.89 (commit SHA).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| permissions: | ||
| contents: read | ||
| # write required for issue-triggered branch creation | ||
| contents: write | ||
| id-token: write | ||
| pull-requests: write | ||
| issues: write |
There was a problem hiding this comment.
contents: write is granted for all workflow triggers (pull_request / issue_comment / review_comment / issues). Since write access is only needed for issue-triggered branch creation, consider splitting into a separate job for issues:labeled with contents: write, keeping contents: read for the comment/PR-triggered job(s) to preserve least-privilege and reduce blast radius if the action is compromised.



Summary
issues: [labeled]event trigger to the Claude Code workflowlabel_trigger: "claude"input so Claude can work issues autonomously (read issue, create branch, implement fix, open PR)contentspermission fromreadtowrite(required for issue-triggered branch creation)6e2bd52842c65e914eba5c8badd17560bd26b5de)Matches the org CI standard defined in petry-projects/.github#24. Same change as petry-projects/broodly#69.
Test plan
claudecheck will fail as expected since the workflow file differs from main)claudelabel exists on the repoclaudeand confirm a workflow run triggers🤖 Generated with Claude Code