style: apply Rector to read-queue files (green the advisory job)#51
Conversation
The read-queue fix was cherry-picked from a branch predating the curated Rector ruleset, so the advisory Rector CI job was red. Add the closure : void return types it flags (AddClosureVoidReturnTypeWhereNoReturnRector) + Pint import ordering. No behavior change.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
More reviews will be available in 23 minutes and 20 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
Note
|
Adds the closure
: voidreturn types Rector flags on the cherry-picked read-queue files (#49 predated the Rector ruleset). No behavior change — Rector/PHPStan/Pint all clean, full test suite assertions intact.🤖 Generated with Claude Code