feat: channel-compat posts a per-channel PR-comment section - #75
Conversation
Same sticky-comment convention as build-tests (update_pr_comment.py, section-id channel-<name>): pass / new-breakage / unresolvable-channel states, with the constraints URL and the resolved-stack artifact named. pr_comment input (default true) mirrors build-tests; pull_request events only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 44 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 (1)
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 |
Follow-up to #72/#74, channel-compat.yml only (no existing workflows touched): the reusable workflow now posts a '📡 Channel Compat — ' section into the standard OVOS PR Checks sticky comment, using the same⚠️ failures (new breakage or unrecorded gap, with the artifact named), 🚧 channel unresolvable (fleet finding).
update_pr_comment.pyconvention as build-tests. States: ✅ pass,pr_commentinput defaults true, fires on pull_request events only.Implemented by Claude Fable directly, per maintainer request; merge authority granted for the new channel-compat workflow.
🤖 Generated with Claude Code