Skip to content

feat: channel-compat posts a per-channel PR-comment section - #75

Merged
JarbasAl merged 1 commit into
devfrom
feat/channel-compat-pr-comment
Aug 1, 2026
Merged

feat: channel-compat posts a per-channel PR-comment section#75
JarbasAl merged 1 commit into
devfrom
feat/channel-compat-pr-comment

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Aug 1, 2026

Copy link
Copy Markdown
Member

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 update_pr_comment.py convention as build-tests. States: ✅ pass, ⚠️ failures (new breakage or unrecorded gap, with the artifact named), 🚧 channel unresolvable (fleet finding). pr_comment input 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

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>
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ef3bd956-9c24-4fe1-9702-9883299eca90

📥 Commits

Reviewing files that changed from the base of the PR and between 5fe1bb7 and e9fa15f.

📒 Files selected for processing (1)
  • .github/workflows/channel-compat.yml

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

Comment @coderabbitai help to get the list of available commands.

@JarbasAl
JarbasAl merged commit 46e6a73 into dev Aug 1, 2026
1 check passed
@JarbasAl
JarbasAl deleted the feat/channel-compat-pr-comment branch August 1, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant