Claude
f4c5e214f9
Checked against the action repo itself rather than assumed: git ls-remote shows v1.7.4 is the newest release tag and the moving v1 tag points at the same commit (c2ae82f), so this changes which ref is named, not which code runs — today. What it buys is that the version running stays the version that was reviewed here, instead of silently following wherever v1 moves. There was never a v0 reference in this workflow, and there is no api-key presence check to remove — the action is invoked directly and fails loudly if JUNIE_API_KEY is absent, which is the intended behaviour. For the record, since this commit will re-trigger the job on PR #12: the two failures there today are neither the workflow nor the Junie balance. Both died in under ten seconds at the action's GitHub permission pre-check with GitHub's own 503 body ("No server is currently available to service your request"), before any Junie API call was made. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SAcqrz3FcadkYr3xG32CjK
51 lines
2.1 KiB
YAML
51 lines
2.1 KiB
YAML
name: Junie Review
|
|
|
|
# Automated PR review by Junie, JetBrains' coding agent. Advisory only: it posts a
|
|
# summary and inline comments, and is deliberately not a required check — CI is what
|
|
# gates a merge, and a review that can block one on a judgement call is a review that
|
|
# gets rubber-stamped.
|
|
#
|
|
# Requires a JUNIE_API_KEY repository secret (Settings → Secrets and variables →
|
|
# Actions). Without it the action fails at the first step rather than skipping, so
|
|
# add the secret before merging this file.
|
|
|
|
on:
|
|
pull_request:
|
|
types: [ opened, synchronize, reopened ]
|
|
branches: [ main, develop ]
|
|
|
|
# A PR that gets three pushes in a minute should end up with one review of the final
|
|
# state, not three reviews of intermediate ones. Combined with use_single_comment
|
|
# below, each PR keeps exactly one review comment, rewritten as the diff changes.
|
|
concurrency:
|
|
group: junie-review-${{ github.event.pull_request.number }}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
review:
|
|
name: Junie
|
|
runs-on: ubuntu-latest
|
|
|
|
# Secrets are not exposed to `pull_request` runs originating from a fork, so a
|
|
# fork PR would fail on an empty API key rather than review anything. Skip those
|
|
# explicitly — a skipped job reads as "not applicable", a failed one as "broken".
|
|
if: github.event.pull_request.head.repo.full_name == github.repository
|
|
|
|
permissions:
|
|
contents: read # read the diff; Junie does not push from this workflow
|
|
pull-requests: write # post the review summary and inline comments
|
|
issues: write # the PR conversation is an issue timeline to the API
|
|
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
- name: Review the pull request
|
|
# Pinned to the newest release rather than the moving v1 tag, so the version
|
|
# running is the version reviewed here. Bump deliberately.
|
|
uses: JetBrains/junie-github-action@v1.7.4
|
|
with:
|
|
junie_api_key: ${{ secrets.JUNIE_API_KEY }}
|
|
# Built-in structured review prompt, as opposed to a free-form instruction.
|
|
prompt: "code-review"
|
|
# Update one comment across re-runs instead of appending a new one per push.
|
|
use_single_comment: "true"
|