strake-dev/gate-check

Part of Strake — CI-native deploy safety.

Pre-deploy safety check for GitHub Actions. Runs on pull_request (or anywhere you want a verdict), calls the Strake gate engine, and upserts a verdict comment on the PR. Optionally blocks the merge on HOLD or CRITICAL.

Need an account? Sign up free at strake.dev.

Usage

# .github/workflows/strake-gate.yml
name: Strake Gate Check
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  pull-requests: write  # required for the PR comment

jobs:
  gate:
    runs-on: ubuntu-latest
    steps:
      - uses: strake-dev/gate-check@v1
        with:
          strake-deploy-token: ${{ secrets.STRAKE_DEPLOY_TOKEN }}
          service: api-gateway
          fail-on-hold: false   # optional — set true to block HOLD merges

That's three lines after the boilerplate. Generate the token, pick a service, and copy a ready-to-paste workflow from Deploy Gate Setup.

Inputs

Name	Required	Default	Description
service	yes	—	Strake service slug, e.g. api-gateway
strake-deploy-token	yes	—	Deploy token (bearer auth)
service-id	no	—	Deprecated UUID input; use service
strake-api-url	no	https://api.strake.dev	Override only for self-hosted
strake-app-url	no	https://strake.dev	Dashboard link base URL
fail-on-hold	no	false	Exit non-zero on HOLD
post-pr-comment	no	true	Upsert a PR comment with the verdict
github-token	no	${{ github.token }}	Token used to post the comment

Outputs

Name	Description
verdict	go / hold / critical / not_evaluated
reason	Human-readable reason from the gate engine
service	Service slug
checked-at	ISO-8601 timestamp of the evaluation
dep-changes-level	ok / warning / critical / unknown
dep-changes-summary	Human-readable dependency-change summary

PR comment

When the workflow runs on pull_request, the Action upserts one timeline comment containing:

• the deploy-gate verdict and merge enforcement
• the concrete reasons Strake returned, including dependency-change context when available
• the next action a reviewer should take before merging or deploying

Exit codes

Verdict	fail-on-hold=false	fail-on-hold=true
go	0	0
not_evaluated	0	0
hold	0 (warning annotation)	1
critical	1	1

Network errors or malformed responses → exit 2.

Links

• strake.dev — product homepage
• Docs — setup guides and API reference
• Dashboard — view live gate evaluations
• Issues — report bugs or request features

---

© 2026 Strake. MIT licensed.