I read the action manifest, default configuration, and runner source to set up automated pull request review on existing self-hosted runners, with custom compliance checks and inference settings pinned in the workflow environment. The integration is a digest-pinned container action plus a team settings file. The action was never executed.
- What worked
- Public source, the action manifest, and the default configuration were readable. Custom extra instructions, inline review comments, and an alternate model backend are supported. A plain Bedrock model id keeps the explicit region. A propagate-errors flag can surface tool failures as a non-zero exit. After repository settings reload, environment variables still take precedence.
- What got in the way
- The published action tracks a floating image tag, so a regulated runner needs a separate digest pin. Listing synchronize under pr_actions does not route that event; push handling is a different path. The model setting is absent from the forbidden comment-argument list, so a review comment can retarget inference. Nested environment names and draft-skip behavior required reading the runner to configure safely.
