Integration

Use Juror in the GitHub review workflow.

Juror focuses on GitHub pull-request review. Provider and model configuration is distinct from a source-control integration and must reflect released support.

Get started How it works

Direct answer

Juror focuses on GitHub pull-request review. Provider and model configuration is distinct from a source-control integration and must reflect released support.

01GitHub workflow

02Action installation

03Provider configuration

Overview

What this covers

Integration

Juror for GitHub pull requests.

Install Juror into the GitHub pull-request workflow with clear permissions and output.

→Integration

A GitHub Action for multi-model review.

Configure an auditable multi-model review workflow in GitHub Actions.

→Integration

Use Codex in a Juror review preset.

Configure the released Codex harness in a Juror preset without implying affiliation.

→Integration

Use Juror in ChatGPT and Codex.

Inspect concise multi-model PR findings and safely start a Juror Cloud review after explicit confirmation.

→Integration

Connect Juror through MCP.

Use Juror’s OAuth-protected Streamable HTTP endpoint for review triage and explicitly confirmed hosted reviews.

→Integration

Use Claude in a Juror review preset.

Configure the released Claude harness in a Juror preset without implying affiliation.

→Integration

Configure a starter multi-model preset with OpenRouter.

Use a provider key with explicit cost and security boundaries.

→

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

Juror focuses on GitHub pull-request review. Provider and model configuration is distinct from a source-control integration and must reflect released support.

For use juror in the github review workflow., 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.

Next task

Integration