Repository navigation
ci: repin ci-failure-analyst → @ci-failure-analyst/stable (#1159) - #1166
Conversation
|
Warning Review limit reached
Next review available in: 41 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: Organization UI Review profile: ASSERTIVE 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request deletes the templates/ci-failure-analyst.yml workflow template file. The reviewer noted that this deletion is likely unintended, as the goal should be to repin the workflow to the @ci-failure-analyst/stable channel rather than deleting the file entirely, and provided a suggestion to revert the deletion and update the reference.
| if: >- | ||
| github.event.check_run.conclusion == 'failure' && | ||
| !startsWith(github.event.check_run.name, 'CI Failure Analyst') | ||
| uses: petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml@0ef7b6150516c4fa447700b4902e8ed406bcfb99 # main |
There was a problem hiding this comment.
It appears that the entire templates/ci-failure-analyst.yml file is being deleted in this PR. Based on the PR title and description, the goal is to repin the workflow to the @ci-failure-analyst/stable channel rather than deleting the template. Please revert the deletion and update the uses reference instead.
uses: petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml@ci-failure-analyst/stable![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3568d1554e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -1,46 +0,0 @@ | |||
| # Deploy this file to target repos as: .github/workflows/ci-failure-analyst.yml | |||
There was a problem hiding this comment.
When this template is deployed by copying it to a target repo's .github/workflows/ci-failure-analyst.yml (as documented in docs/aw/ci-failure-analyst.md and referenced by the local lock workflow), the file is now empty, so newly onboarded repos get no check_run trigger, permissions, or uses: call into ci-failure-analyst-reusable.yml. That silently disables CI Failure Analyst instead of repinning the caller to @ci-failure-analyst/stable.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
This PR advances the versioned-release/canary rollout for ci-failure-analyst by repinning the consumer workflow stub away from a raw main SHA to the moving ci-failure-analyst/stable channel tag, enabling gated, rollback-able releases across the fleet.
Changes:
- Repin
ci-failure-analystreusable workflow reference from amainSHA to@ci-failure-analyst/stable. - Add an inline suppression comment to document that this is an approved first-party channel ref.
| github.event.check_run.conclusion == 'failure' && | ||
| !startsWith(github.event.check_run.name, 'CI Failure Analyst') | ||
| uses: petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml@0ef7b6150516c4fa447700b4902e8ed406bcfb99 # main | ||
| uses: petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml@ci-failure-analyst/stable # NOSONAR(githubactions:S7637) first-party channel ref |
|
Dev-Lead — review-changes (applied)Changes committed and pushed. |
Versioning rollout #1159: ci-failure-analyst now has an immutable
v1.0.0+ moving channel tags. Repin this consumer from a rawmainSHA to the@ci-failure-analyst/stablechannel so it gets gated, rollback-able releases.combsmith/.github#659 registered it in canary-rings.json.