Repository navigation
ci(dev-lead): enable dev-lead-issue-retry dispatch type (#781) - #292
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
More reviews will be available in 47 minutes and 2 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy 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)
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 |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
|
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-19T23:59:00Z. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: 664e7faa0e97c9076c27a3a2f2afe96b2d322195
Review mode: triage-approved (single reviewer)
Summary
One-line CI change to the dev-lead.yml caller stub: adds two repository_dispatch trigger types (dev-lead-reviews-retry, dev-lead-issue-retry) so the dev-lead-retry cron's dispatches are handled. Re-syncs the stub with the canonical petry-projects/.github template. permissions: {} stays empty; pin, agent_ref, and concurrency contract are untouched.
Linked issue analysis
No formal closingIssuesReferences. The PR references combsmith/.github-private#781 as motivation (bounded auto-retry of failed initial issue implementations) and is a companion to .github#494 and .github-private#810. The change is a CI-infra template sync, not an issue fix; the diff matches the stated intent exactly.
Findings
- No security-relevant changes. The diff only widens the repository_dispatch
typesarray by two entries; permissions remain{}, and the action pin/agent_ref/concurrency are unchanged. - repository_dispatch events require an authenticated API call to emit, so the added trigger types do not broaden the external attack surface.
- Secret-scanning MCP unavailable (GitHub Advanced Security not enabled for this repo); the gitleaks CI check passed.
- No unresolved human-review threads; advisory-bot comments are rate-limit/usage notices, not findings.
CI status
Genuine quality gates green: Lint, Format, Test, Secret scan (gitleaks), CodeQL/Analyze (actions), SonarCloud, AgentShield, dependency-audit (Detect ecosystems), pr-auto-review, review. Two dev-lead self-jobs (dispatch, ci-relay) are CANCELLED by normal per-PR concurrency management — expected, non-blocking. mergeStateStatus=BLOCKED only because org-leads review is required.
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.
CI Failure: SonarCloud Code AnalysisStep: SonarCloud Quality Gate (main branch post-merge analysis) SonarCloud reported 14 new Security Hotspots on the Suggested fix: Open the SonarCloud Security Hotspots dashboard, review each of the 14 flagged hotspots, and mark them as Safe (if not exploitable) or create follow-up issues for any that are genuine risks — this will resolve the Quality Gate failure. |



Summary
Re-syncs this repo's
dev-lead.ymlcaller stub with the updated canonical template (petry-projects/.github →standards/workflows/dev-lead.yml).Adds the two missing
repository_dispatchtypes thedev-lead-retrycron emits:dev-lead-issue-retry— bounded auto-retry of a failed initial issue implementation (dev-lead retry doesn't cover failed initial issue implementations (only rate-limited PRs) — issues silently stall .github-private#781). Without this, a labeled-issue run that fails at the engine step (e.g. a transient timeout) silently stalls here with no retry.dev-lead-reviews-retry— auto-retry of rate-limited PR-review runs (closes a pre-existing template drift).This is the only change — a one-line trigger addition. The pin,
agent_ref, permissions, and concurrency contract are untouched. Companion to combsmith/.github#494 (template + docs) and combsmith/.github-private#810 (implementation).🤖 Generated with Claude Code