fix: disable Claude/CodeRabbit check-suite auto-trigger; fix label settings#261
fix: disable Claude/CodeRabbit check-suite auto-trigger; fix label settings#261don-petry wants to merge 34 commits into
Conversation
…ttings - Applied PATCH to repos/petry-projects/google-app-scripts/check-suites/preferences to set auto_trigger_checks=false for Claude (app_id 1236702) and CodeRabbit (app_id 347564), eliminating orphaned queued suites that block auto-merge. - Updated .github/settings.yml: fix security label color (e4e669→d93f0b) and description; add all six missing standard labels per org label standards. Closes #257 Co-authored-by: Don Petry <don-petry@users.noreply.github.com>
|
Warning Review limit reached
Your plan includes 1 review of capacity. Refill in 59 minutes and 47 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, 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 trial, open-source, and free plans. In all cases, review capacity refills continuously over time. 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)
📝 WalkthroughWalkthroughThe PR updates the repository label configuration in ChangesRepository Label Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
|
@petry-projects/org-leads — CI is running on this compliance fix PR. The change:
Please review and merge when CI passes. |
There was a problem hiding this comment.
Pull request overview
Tracks compliance remediation work for this repository: aligning repo labels with the org standard set and (per PR description) addressing orphaned Claude/CodeRabbit check suites that block auto-merge.
Changes:
- Updates the
securitylabel color/description to match the referenced standard. - Adds the missing standard labels:
dependencies,scorecard,bug,enhancement,documentation,in-progress.
| # Labels — standard set | ||
| # Reference: https://github.com/petry-projects/.github/blob/main/standards/github-settings.md#labels--standard-set | ||
| labels: | ||
| - name: security | ||
| color: e4e669 | ||
| description: Security vulnerability or concern | ||
| color: d93f0b | ||
| description: Security-related PRs and issues |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/settings.yml (1)
10-27: 💤 Low valueLGTM — six new labels are well-formed.
All required fields (
name,color,description) are present and valid. Quoting hex values that start with digits ('0075ca') is correct YAML practice.One optional note:
scorecard(Line 14) andsecurity(Line 8) share the same colord93f0b. If this is intentional per org standard to visually group security-related labels, no action needed. If unintentional, consider a distinct color forscorecardto differentiate them at a glance in the GitHub UI.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/settings.yml around lines 10 - 27, The labels file defines both scorecard and security with the same color d93f0b; if you want them visually distinct, update the scorecard label's color value in the settings YAML (the scorecard entry's color field) to a different hex code (ensure you quote the hex if it begins with a digit, e.g., 'aabbcc') and keep the security label unchanged; if the identical color is intentional, leave the scorecard color as-is.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/settings.yml:
- Around line 10-27: The labels file defines both scorecard and security with
the same color d93f0b; if you want them visually distinct, update the scorecard
label's color value in the settings YAML (the scorecard entry's color field) to
a different hex code (ensure you quote the hex if it begins with a digit, e.g.,
'aabbcc') and keep the security label unchanged; if the identical color is
intentional, leave the scorecard color as-is.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f72f1c0c-0b5f-4609-a83f-809ef78ac4dc
📒 Files selected for processing (1)
.github/settings.yml
|
Summary
repos/petry-projects/google-app-scripts/check-suites/preferencesto setauto_trigger_checks: falsefor Claude (app_id1236702) and CodeRabbit (app_id347564). This eliminates orphanedqueuedcheck suites created on every push that permanently blocked GitHub auto-merge..github/settings.yml— corrected thesecuritylabel color (e4e669→d93f0b) and description, and added all six missing standard labels (dependencies,scorecard,bug,enhancement,documentation,in-progress) per the org label standard.Closes #257
Test plan
check-suite-auto-trigger-1236702for this repoGenerated with Claude Code
Summary by CodeRabbit