GitHub for reviews, CI for gating, and Slack or email so the right people see the verdict.
Install the app once and review pull requests on demand. Analysis runs least-privilege and sandboxed, and the app key never touches your code.
Trigger with the shipguarde label or an @shipguarde comment
A status check, inline review comments, and a sticky summary
Reply to a finding to dismiss or verify it. The app responds in-thread
Run it from CI and gate the job on the verdict, independently of the GitHub check.
Drop in shipguarde/review-action@v1 with an sg_pat_… key
Choose when to fail: fail-on: block | block_or_warn | never
Or call POST /api/runs directly and poll for the verdict
Version-control your gate policy so a change to it is reviewed in the same pull request.
failCheckOnBlock: true turns a block into a failing check
In-repo settings win over the dashboard, and unknown keys are ignored
Read from the PR head commit, so the policy travels with the branch
Keep the team in the loop without leaving chat.
Verdict notifications to a channel via an incoming webhook
Get pinged on a block, or when a fixed issue regresses
A signed clearance certificate in the inbox when a run finishes.
Send to the recipients you pick per run
Org mailing lists for stakeholders who only want the result
Code review checks the diff. ShipGuarde also checks the running product, so a release does not ship on the hope that nothing broke.
NO CREDIT CARD · CONNECT GITHUB IN UNDER FIVE MINUTES · CANCEL ANY TIME
RELEASE CLEARANCE BUREAU
ISSUING AUTHORITY FOR SOFTWARE RELEASES
[email protected]