Repository navigation
ci: skip grok review on release PRs - #392
Conversation
Release PRs only bump versions and the changelog, so a review finds nothing to act on and spends a Grok run on every push to the release branch. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚡ Grok Review
Reviewed commit: d75cff864a
❌ Patch is incorrect: 1 finding.
The new job-level if skips the review job, so GitHub never creates the required review check and release-please pull requests stay blocked.
Report success when the review is skipped (
.github/workflows/grok-review.yml#L16-L23)
![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: d75cff864a
ℹ️ 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".
Refuted: Grok review is not a required check, and a job skipped by a job-level if still reports a skipped check run. See the thread reply.
Agent summary
The Grok review ran on every push to the release-please PR (#362) and reviewed version bumps and changelog entries, which never carry anything to act on.
The review job now skips PRs whose head branch starts with
release-please--. A skipped job still satisfies a required check, so release PRs stay mergeable.Proof
actionlintpasses on the edited workflow, andyqreads the job condition as... && !startsWith(github.event.pull_request.head.ref, 'release-please--').🤖 Generated with Claude Opus 5.5 via Claude Code