ci: bump both AI-review caller pins to ai-review-prompts@128656e4#82
Merged
Conversation
Symmetric pin across `claude-review.yml` and `gemini-review.yml`. Both callers now reference the same ai-review-prompts SHA — easier to audit "are we current?" without per-file checks, and matches the "single pin per repo upgrade motion" the caller comment already promises. `claude-review.yml` (was @3278ce4e, post-#20) → @128656e4. Picks up: - Shared-script refactor (#22): provider-agnostic find-prior-review-comment.sh + log-review-to-ai-review-log.sh with explicit MARKER / MODEL env vars. Behavior for Claude unchanged (PROVIDER_LABEL stays empty → legacy title format preserved). New body fields: `**Run:**` link to the workflow run page (visible in ai-review-log entries). - authorize-claude-workflow.sh → authorize-ai-workflow.sh rename (handled inside the reusable; consumer caller untouched). - Auth-gate validator generalization to pattern-based glob. `gemini-review.yml` (was @9471cd80, post-#22) → @128656e4. Picks up: - Architectural fix (#24): workflow posts the Gemini response via a new post step, since run-gemini-cli's single-shot mode doesn't give the agent tool access to call `gh pr comment` itself. - Output-name fix (#25): post step now references the action's caller-facing output (`summary`) instead of the action's internal step output (`gemini_response`). Without this fix the post step was always skipped silently — discovered on this PR's first run (after #24's artifact-upload addition let us see the agent's actual response in stdout.log). - Artifact upload enabled on the Gemini step for post-mortem visibility. - Default model flipped to `gemini-3-flash-preview` (#23) — Google's current-gen mid-tier Flash, the apples-to-apples peer of Claude Sonnet 4.6. No `model:` override needed here. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
heskew
force-pushed
the
ci/bump-ai-review-prompts-d9274252
branch
from
16529ec to
ca6385a
Compare
heskew
changed the title
Contributor
|
Reviewed; no blockers found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Symmetric pin across
claude-review.ymlandgemini-review.yml— both now referenceai-review-prompts@128656e4. Easier to audit "are we current?" without per-file checks, and matches the "single pin per repo upgrade motion" the caller comment already promises.What each caller picks up
claude-review.yml(was @3278ce4e → @128656e4)find-prior-review-comment.sh+log-review-to-ai-review-log.shwith explicitMARKER/MODELenv vars. Behavior for Claude is unchanged —PROVIDER_LABELstays empty so the legacy title format is preserved.**Run:**link in the ai-review-log issue body (one click to the workflow run, where token usage / estimated cost is visible).authorize-claude-workflow.sh→authorize-ai-workflow.shrename, handled inside the reusable (consumer caller doesn't reference the script directly).gemini-review.yml(was @9471cd80 → @128656e4)run-gemini-cli's single-shot mode doesn't give the agent shell tools to callgh pr commentdirectly.summary) instead of the action's internal step output (gemini_response). Without this fix the post step was silently skipped — discovered on this PR's first run, after the artifact upload addition surfaced the agent's actual response (which was correct all along).gemini-3-flash-preview— Google's current-gen mid-tier Flash. Nomodel:override needed.Expected first-run quirk
The Claude step on this PR's branch will fail with a GitHub-side App-token 401 from claude-code-action's workflow validation ("workflow file must exist and have identical content to the version on the default branch"). This is a known gotcha for workflow-modifying PRs and the message itself says to ignore it. After this PR merges, subsequent PRs review normally.
Test plan
claude[bot]with<!-- claude-review:v1 -->(resumes normal operation)github-actions[bot]with<!-- gemini-review:v1 -->(was always silently skipped before)🤖 Generated with Claude Code