Runs JetBrains' Junie agent on every PR into main or develop, using the
action's built-in `code-review` prompt rather than a free-form instruction.
Details worth keeping:
- `use_single_comment` plus a `concurrency` group keyed on the PR number, so a
burst of pushes leaves one review of the final state rather than a queue of
reviews of intermediate ones.
- Skipped explicitly on fork PRs. `pull_request` does not expose secrets to
them, so the job would otherwise fail on an empty API key — a skipped job
reads as "not applicable", a failed one as "broken".
- `contents: read`. This workflow reviews; it does not push.
- Not a required check, on purpose. CI gates merges; a review that can block
one on a judgement call is a review that gets rubber-stamped.
Needs a JUNIE_API_KEY repository secret before it will do anything but fail.
Pinned to @v1, whose action.yml declares each of the three inputs used here.
actionlint clean across all three workflows.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SAcqrz3FcadkYr3xG32CjK
