chore(compliance): run re-trigger sweep hourly (one issue per repo per hour)#445
Conversation
Change the schedule from daily (05:00 UTC) to hourly (0 * * * *). The per-run one-engagement-per-repo throttle is unchanged, so this yields at most one issue re-triggered per repo per hour — draining each repo's backlog ~24x faster while still avoiding concurrent dev-lead runs in a single repo. Update the script docstring/comments to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 16 minutes and 59 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation comments in scripts/compliance-retrigger.sh to reflect that the compliance-retrigger script now runs on an hourly cadence instead of a daily cadence. There are no review comments, and I have no feedback to provide.
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
There was a problem hiding this comment.
Pull request overview
Adjusts the compliance “re-trigger stale issues” sweep cadence from daily to hourly to drain stale compliance-audit backlogs faster, while preserving the existing one-engagement-per-repo per run throttle introduced in #432.
Changes:
- Updated the scheduled trigger in the compliance re-trigger workflow to run hourly (
0 * * * *). - Updated
scripts/compliance-retrigger.shheader/comments to reflect the new hourly cadence.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/compliance-retrigger.yml |
Changes the cron schedule from daily to hourly while keeping existing concurrency/permissions setup. |
scripts/compliance-retrigger.sh |
Updates documentation/comments to describe the hourly schedule and retry behavior. |
Dev-Lead — review-changes (applied)Changes committed and pushed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Dev-Lead — waiting on PR blockers (intent: review-changes)PR: #445 |
|
Note @don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically. |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
|
Summary
Change the compliance re-trigger sweep from daily (
0 5 * * *) to hourly (0 * * * *).The per-run one-engagement-per-repo throttle (added in #432) is unchanged, so the net effect is at most one issue re-triggered per repo per hour. This drains each repo's stale-issue backlog ~24× faster while preserving the property that matters: never more than one concurrent dev-lead engagement per repo (no rebase storms, no token-burst).
Changes
.github/workflows/compliance-retrigger.yml:cron: '0 5 * * *'→'0 * * * *'.scripts/compliance-retrigger.sh: docstring/comments updated (daily → hourly).Why this is safe
dev-lead/issue-*PR or a freshin-progresslabel are skipped (dl_dev_lead_active), so an actively-worked issue is never re-cycled hour-to-hour.STALE_DAYS=2) are eligible, so this does not re-trigger fresh findings.Note
Worst-case dev-lead invocations rise from ~1/repo/day to ~1/repo/hour while a backlog exists per repo; it self-limits to zero once a repo's eligible issues are cleared. The previous off-peak (12 AM Central) rationale is moot — hourly inherently spreads load.
Context
Follow-up to #431/#432 (sweep unbroken + throttled) and #438/#442 (Step 1 removed). Part of the Compliance program initiative.