Loading…
Open-Policy Exchange
~4 min to deploy
GitHub Deploy Approval Gate
Blocks production deploys during a freeze, escalates out-of-hours releases, and stamps the verdict on the PR.
For: CI/CD owners gating deploys, releases, and infra changes
SOC 2 CC8.1ISO 27001 A.8.32Change evidence
What it enforces
Change-freeze block
Blocks a production deploy while a change freeze is active.
Out-of-hours escalation
Escalates any production deploy outside business hours to a human approver.
Green-CI allowance
Allows deploys that carry a green CI run and an approved pull request.
github-deploy-approval-gate.yaml
# GitHub Deploy Approval Gate
# Fork: mirrors the DECIONIS_POLICY.md shipped in apps/github/examples.
# Start with mode: shadow — the step records every verdict and never fails.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: github-deploy-approval-gate
surface: github
workflow_key: github_deploy_approval
standards: [SOC2-CC8.1, ISO27001-A.8.32]
defaults:
mode: shadow # shadow | enforce
emit_dossier: true
comment_pr: true
rules:
- name: change_freeze_block
when: "decision_type == 'production-deploy'"
decision: |
BLOCK IF context.change_freeze == true
ALLOW OTHERWISE
reason_code: deploy_during_change_freeze
- name: out_of_hours_escalation
when: "decision_type == 'production-deploy'"
decision: |
ESCALATE IF context.business_hours == false
ALLOW OTHERWISE
reason_code: deploy_outside_business_hours
- name: green_ci_allowance
when: "decision_type == 'production-deploy'"
decision: |
ALLOW IF context.ci_status == 'success' AND context.pr_approved == true
ESCALATE OTHERWISE
reason_code: missing_green_ci_or_approval
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Drops into any workflow YAML in one line. Verdicts surface on the PR + the run summary.
GitHub Action — shadow mode
# .github/workflows/deploy.yml
- uses: decionis/govern@v1
with:
api-key: ${{ secrets.DECIONIS_API_KEY }}
org-id: ${{ secrets.DECIONIS_ORG_ID }}
workflow-key: github_deploy_approval
mode: shadow # ← every verdict recorded; step never fails
comment-pr: 'true' # ← post verdict + verify URL on the PR
Ships in shadow mode — every verdict is recorded, nothing is blocked.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.