Skip to main content
After signals land, GitHub Actions polls Verdikt by commit SHA and fails the check if the gate does not pass. Pair this with branch protection so nothing merges without Verdikt’s permission.

Prerequisites

  1. Release trigger — GitHub App connected; PRs labeled verdikt:rc open a cert window.
  2. Signals — integrations auto-pull and/or your pipeline POSTs signals for that commit.
  3. Secrets in the repo:
    • VERDIKT_API_URL — e.g. https://api.useverdikt.com
    • VERDIKT_API_KEYvdk_live_… from Settings → Agent access
    • VERDIKT_WORKSPACE_IDSettings → General
  4. Branch protection — require the Verdikt gate check (or your job name) before merge.

Copy to .github/workflows/verdikt-gate.yml

Polls up to 12 × 10s (2 minutes) so signals can arrive before the job fails.
Agent-driven flows can use MCP check_gate instead of polling — see MCP setup. GHA + branch protection still enforces merge at the button.

Manual curl (debug)

Exit non-zero when gate.allowed is false.

Gate actions