Gate your launches in CI. The action runs gantry validate against the .gantry/ vault
in your repository and fails the job when the launch is not ready. It also posts a sticky
audit report as a PR comment on every pull request.
# .github/workflows/launch-gate.yml
name: Launch Gate
on: [pull_request]
jobs:
gantry:
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write # required to post PR comments
steps:
- uses: actions/checkout@v4
- uses: trygantry/gantry@v1
with:
workspace: "."
fail-on-no-go: true
comment: trueThe job exits:
- 0 — readiness is Go (all checks pass)
- 1 — launch is blocked (open P0 blockers, incomplete required QA, missing sign-offs, stale or invalid required docs)
- 2 — configuration or environment error
| Input | Default | Description |
|---|---|---|
workspace |
. |
Directory containing the .gantry/ vault. |
token |
github.token |
GitHub token for posting PR comments. |
fail-on-no-go |
true |
Exit 1 when launch is blocked. Set false for reporting only. |
comment |
true |
Post or update a sticky PR comment with the audit report. |
- uses: actions/checkout@v4
- uses: trygantry/gantry@v1
with:
workspace: apps/backend
fail-on-no-go: true
comment: true- uses: trygantry/gantry@v1
with:
fail-on-no-go: false
comment: trueThe Gantry CLI (gantry-cli) is a standalone, GUI-free crate that depends only on
gantry-core — it does not link the Tauri desktop runtime. The action builds it from
source with cargo build -p gantry-cli, so no GUI system dependencies
(libwebkit2gtk, GTK, etc.) are required. Rust build caching (Swatinem/rust-cache)
keeps subsequent runs fast.
Each tagged release also publishes prebuilt CLI binaries (gantry-linux-x86_64,
gantry-macos-aarch64, gantry-macos-x86_64, gantry-windows-x86_64.exe). A future
revision of this action will download the matching prebuilt binary instead of compiling,
eliminating the initial build cost entirely.