feat: implement issue #723 — [Phase 1] Move all scheduled workflows off the top of the hour - #1215
Conversation
…ff the top of the hour
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 55 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughScheduled GitHub Actions workflows were moved from minute-zero execution to staggered UTC minutes. Related inline comments and workflow documentation were updated to match, with cadence and other cron fields preserved. ChangesCron schedule staggering
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related issues
Possibly related PRs
Suggested labels: 🚥 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 |
![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 cron schedules for several GitHub Actions workflows to introduce minute offsets. The review feedback correctly identifies that the accompanying comments describing the execution times in 'content-twin-audit.md', 'docs-health-check.md', and 'standards-sync.md' were not updated and are now out of sync with the new cron schedules.
There was a problem hiding this comment.
Pull request overview
This PR implements issue #723 Phase 1 by moving scheduled GitHub Actions workflows (and matching agentic/docs examples) off the top-of-hour (:00) to reduce missed/delayed cron runs during GitHub’s busiest minute.
Changes:
- Updated multiple
.github/workflows/*.ymlschedule.cronentries to use non-zero, staggered minutes while preserving hour/day cadence. - Kept the stale-manager workflow spec (
.github/workflows/stale-manager.md) aligned with its workflow file. - Updated
docs/aw/*examples that documented the previous:00schedules.
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 17 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/aw/standards-sync.md | Updates documented cron example off :00. |
| docs/aw/docs-health-check.md | Updates documented cron example off :00. |
| docs/aw/content-twin-audit.md | Updates documented cron example off :00. |
| .github/workflows/token-report.yml | Moves weekly token report schedule off :00. |
| .github/workflows/standards-sync.yml | Moves standards-sync schedule off :00. |
| .github/workflows/stale-manager.yml | Moves stale-manager schedule off :00. |
| .github/workflows/stale-manager.md | Keeps stale-manager spec cron in sync with workflow. |
| .github/workflows/skill-eval-report.yml | Moves daily skill-eval report schedule off :00. |
| .github/workflows/readme-refresh.yml | Moves weekly README refresh schedule off :00. |
| .github/workflows/premature-closure-audit.yml | Moves weekly audit schedule off :00. |
| .github/workflows/idea-triage.yml | Moves weekly idea-triage schedule off :00. |
| .github/workflows/feature-ideation.yml | Moves weekly feature-ideation schedule off :00. |
| .github/workflows/docs-health-check.yml | Moves weekly docs health-check schedule off :00. |
| .github/workflows/daily-pr-review-health.yml | Moves daily PR-review health schedule off :00. |
| .github/workflows/content-twin-audit.yml | Moves daily content-twin audit schedule off :00. |
| .github/workflows/auto-rebase-health.yml | Moves daily auto-rebase health schedule off :00. |
| .github/workflows/actions-fleet-monitor.yml | Moves daily fleet monitor schedule off :00. |
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 — rate-limited (intent: review-changes)PR: #1215 |
|
Note @don-petry I received your request but all AI engines are currently rate-limited. I'll retry automatically once the rate limit clears. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
Dev-Lead — review-changes (applied)Changes committed and pushed. |
Dev-Lead — rate-limited (intent: on-mention)PR: #1215 |
Dev-Lead — on-mention (applied)Changes committed and pushed. |
Dev-Lead — waiting on PR blockers (intent: review-changes)PR: #1215 |
|
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. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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.
Inline comments:
In @.github/workflows/reviewer-report.yml:
- Around line 23-25: Update the schedule description in docs/reviewer-report.md
to state that reviewer-report runs weekly on Monday at 09:53 UTC, matching the
cron schedule in the workflow and preserving the existing documentation
structure.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 568502d7-1053-4ae1-8023-b518649f7af3
📒 Files selected for processing (3)
.github/workflows/feature-ideation.yml.github/workflows/initiative-driver-canary.yml.github/workflows/reviewer-report.yml
Dev-Lead — fix-reviews (applied)Changes committed and pushed. |
|
Dev-Lead — waiting on PR blockers (intent: review-changes)PR: #1215 |
|
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. |
donpetry-bot
left a comment
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: e6c03a90bd5d30666169275ca7245509de3367a4
Review mode: triage-approved (single reviewer)
Summary
Mechanical cron-minute stagger implementing issue #723 Phase 1: moves 14 scheduled workflows (plus matching agentic source and docs) off the top of the hour. Verified repo-wide at head SHA that no minute-0 cron remains, all minutes are distinct and off-peak, only minute fields changed (cadence/day guards preserved), agent-shield.yml and thin-caller stubs untouched, and all CI checks pass. Confirms the triage low-risk assessment.
Linked issue analysis
Issue #723 acceptance criteria all satisfied: (1) no schedule.cron at minute 0 anywhere in .github/workflows at head SHA — verified by scanning every workflow file; (2) only minute fields changed — hour/day-of-week preserved everywhere, so standards-sync's first-Monday guard and idea-triage's Monday cadence remain intact; (3) 14 distinct staggered minutes (07,11,13,19,21,27,29,34,37,41,43,49,51,53) with no shared minute and none adjacent to :00; (4) agent-shield.yml unmodified and no thin-caller stub touched; idea-enhancer.yml from the issue's target list no longer exists at head, so it is not a gap; (5) Lint, ShellCheck, gh-aw-compile, and AW spec validation all green. stale-manager.yml and stale-manager.md are kept identical (29 9 * * 1). docs/aw/standards-sync.md's illustrative cron was also aligned with the real workflow, as the issue suggested.
Findings
No blocking findings. Cross-reference comments in workflow headers (auto-rebase-health, reviewer-report, skill-eval-report, initiative-driver-canary) were updated consistently with the new times. Non-blocking nit: docs/reviewer-report.md's closing paragraph still says the scorecard runs 'one hour after the token report (Mon 08:00 UTC)' — now 09:53 vs 08:34; the table above it was updated correctly. Secret scanning MCP tool was not available in this run; the gitleaks CI check passed. No unresolved review threads; earlier CodeRabbit changes-requested reviews (stale comment cross-references) were addressed and dismissed.
CI status
All checks green at e6c03a9: Lint, ShellCheck (x3), CodeQL (actions+python), SonarCloud, gitleaks secret scan, Agent Security Scan, agent-shield, holdout-guard, template-drift, unit-tests, bats, gh-aw-compile, AW spec validation, agent-profile/persona validation all SUCCESS. One superseded 'review / review' run shows CANCELLED; its replacement succeeded. Dependency-audit language jobs skipped (no matching ecosystems).
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.
Closes #723
Implemented by dev-lead agent. Please review.
Summary by CodeRabbit