ci(#614): repin feature-ideation onto ring channels - #434
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
Next review available in: 48 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
There was a problem hiding this comment.
Pull request overview
Updates this repository’s feature-ideation workflow to consume the ring-based “stable” channel of the upstream first-party reusable workflow, aligning with the completed ring rollout described in the PR.
Changes:
- Switch
.github/workflows/feature-ideation.ymlfrom a pinned SHA (# v1) to@feature-ideation/stable(ring channel ref) and annotate withNOSONAR(githubactions:S7637)to document the intentional non-SHA pin.
|
ci: repin feature-ideation → @feature-ideation/stable (#614)



Completes the feature-ideation ring rollout (#614): channels ring0/ring1/stable were cut at v1.1.0 and it's registered in canary-rings.json (petry-projects/.github#661). Repin this consumer from its old ref onto the ring-appropriate feature-ideation channel.