fix: improve '.bgevents' status feedback#15
Conversation
|
Warning Review limit reached
Next review available in: 14 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe change centralizes queue eligibility and battleground bracket resolution in ChangesQueue eligibility and status reporting
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
There was a problem hiding this comment.
Pull request overview
This PR improves the .bgevents player-facing status output by reporting actual auto-queue eligibility (including bracket resolution) and by providing clearer reasons when auto-queueing is unavailable, while also deduplicating queue-pass eligibility logic in BgAutoQueue.
Changes:
- Updated
.bgevents(no-arg) to show eligibility vs. scheduled-event state separately and to provide a specific per-player ineligibility reason. - Introduced
BgAutoQueue::IsQueueEligible()to unify “pass-time eligibility” checks (including the reference-map bracket check) and reused it inRunQueuePass(). - Added player-facing skip-reason messaging distinct from operator-oriented labels.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/cs_bg_auto_queue.cpp | Reworks .bgevents status messaging and adds player-facing skip-reason strings. |
| src/BgAutoQueue.h | Exposes a new public IsQueueEligible() API to share queue-pass eligibility logic. |
| src/BgAutoQueue.cpp | Implements IsQueueEligible() and uses it to simplify/standardize RunQueuePass() filtering. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary by CodeRabbit