ci: add cron entries at :22, :37, :52 to ensure hourly runs

[don-petry]

Problem

GitHub Actions scheduled workflows are frequently delayed or skipped under load on the shared runner fleet. The single cron entry (7 * * * *) is configured to run hourly but in practice fires every 2–5 hours.

Strategy

Add three additional staggered cron offsets so the scheduler has four chances per clock-hour to fire at least one run:

- cron: "7 * * * *"
- cron: "22 * * * *"
- cron: "37 * * * *"
- cron: "52 * * * *"

Two existing guards ensure this doesn’t cause duplicate work or runaway resource usage:

Guard	Effect
Shared concurrency group (pr-review-scheduled, cancel-in-progress: false)	Serializes runs — at most one executes at a time; extra triggers queue rather than run in parallel
Per-PR idempotency check (head-SHA comparison in review-batch.sh)	Any PR already reviewed at its current head SHA is skipped in O(1); back-to-back queued runs no-op cheaply without producing duplicate reviews

The net effect: if GitHub skips one or two triggers under load, the next offset within the same hour will pick it up. If all four fire, only one run does real work; the rest drain the queue quickly via idempotency short-circuits.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 46 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6e2d113c-22cb-480b-99e5-4ca2be731efb

📥 Commits

Reviewing files that changed from the base of the PR and between 2aedf14 and 3180142.

📒 Files selected for processing (1)

• .github/workflows/pr-review.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/pr-review-hourly-schedule

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR increases the trigger frequency of the PR Review Agent scheduled workflow by adding additional cron offsets, aiming to reduce missed/delayed scheduled runs during GitHub Actions load.

Changes:

• Add three additional on.schedule cron entries (:22, :37, :52) in addition to the existing :07 trigger.
• Update the schedule comment to describe the new cadence and rationale.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud