PASSMerge proceedsA FalseGreen Job accepted this exact pull-request head. CI passes and the merge goes through (exit 0).
FalseGreen Gate
Merge only what a FalseGreen Job accepted.
One CI check on every pull request, free with your FalseGreen key.
What Gate does
Gate answers one question in CI: was this code accepted?
When a pull request opens or updates, Gate runs in your CI, finds the FalseGreen Job for that exact code, and reports what it decided. No new dashboard, no new review step — just a check, like any other.
Your rules, enforced
Require the check in branch protection and accepted code merges on its own. Skip the requirement and Gate just informs your reviewers.
Evidence, not human opinion
The verdict comes from a FalseGreen Job that actually ran your build, tests, and checks — not from a reviewer's mood at 5 pm.
Nothing new to babysit
Gate is one command in your existing CI. It costs nothing and never runs your code again.
Setup takes minutes — the exact steps are on the Install page →
What CI sees
Four results, every pull request.
REVIEWA human decidesThe Job for this head is still running, was closed without a verdict, or does not exist yet. CI is not blocked; your reviewers stay in charge (exit 0, non-blocking).
BLOCKMerge is stoppedThe FalseGreen Job for this exact head ended Failed. The merge is blocked until the code is fixed and re-verified (exit 1).
INTEGRITY_ERRORFails closedThe source or the credential cannot be trusted. Nothing passes (exit 3).
Pull requests without a FalseGreen Job
Gate never blocks work you have not verified. If no Job has run on a pull request's code, Gate reports REVIEW — your normal process applies unchanged, and you can decide whether to run a Job or merge on review.
GitHub Actions · GitLab CI · Buildkite · Jenkins · CircleCI · Drone · Azure DevOps · Generic CI