# How do I calibrate a CI gate before I let it block a merge?

Run it in report-only mode first and watch what it would have blocked before you let it block anything. Tessary's CI gate ships with `risk-threshold` at 1.0, which disables the risk trigger outright, and `block-on-regression` at false, so a fresh install posts its verdict on every pull request without stopping a merge. Once you've watched it against enough real PRs to trust the forecast, lower the threshold in your project config so it starts blocking.

You don't have to commit to a number blind, either. A single request to the gate's report endpoint can pass a `gate_threshold` that overrides the config for that one PR, so you can try a stricter bar on one change and see what it would have caught before you redeploy the config for everyone. The gate blocks on two triggers, OR'd: predicted risk clearing your threshold, or a grader measurably regressing once `block-on-regression` is on.

---

Source: https://tessary.ai/answers/deploy-gates/how-to-calibrate-a-ci-gate-before-blocking-merges
More on Deploy gates: https://tessary.ai/answers/deploy-gates
From Tessary, agent reliability for AI agents in production: https://tessary.ai