Integration

A GitHub Action for multi-model review.

The workflow is ordinary YAML: use a verified action SHA, minimal permissions, protected secrets, and a pull-request event policy that accounts for forks.

Direct answer

The workflow is ordinary YAML: use a verified action SHA, minimal permissions, protected secrets, and a pull-request event policy that accounts for forks.

01Pinned YAML
02Secret handling
03Troubleshooting steps

How it works

Start from a pinned, least-privilege workflow.

The action reference uses a released commit SHA. Store provider keys in GitHub secrets and inspect the first review before you require it.

name: Juror review
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    if: github.event.pull_request.head.repo.fork == false
    runs-on: ubuntu-latest
    steps:
      - uses: Juror-AI/juror@3eb0c88ce1931dd6227d554b2d9707ee4bca123f
        with:
          github-token: ${{ github.token }}
          preset: balanced
          cost-target-usd: "4.00"

How it works

The workflow is ordinary YAML: use a verified action SHA, minimal permissions, protected secrets, and a pull-request event policy that accounts for forks.

For a github action for multi-model review., use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.

Limits to keep in view

Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.