CI/CD gates: checks before the merge and checks after the deploy

A change goes through two different kinds of gate on its way to production. They answer different questions, and teams often rely on the first and forget the second.

Gate 1, before the merge: should this change go in?

These run on the proposed change and GitHub enforces them if you mark them required. They are good at catching mistakes that tests can find.

Gate 2, after the deploy: did it work in production?

These run on the real system. They catch what tests cannot, such as a missing environment variable, a failed migration on real data or a service that starts and then crashes.

Why you need both

Where scheduled merges fit

A scheduled merge adds timing: it decides when the change goes through gate 1 and into gate 2. The risk is that nobody is watching gate 2 at that time. That is why the watch and the revert matter more for out-of-hours releases than for daytime ones.

How Merge Scheduler covers both

Do this in Merge Scheduler: Set up automatic revert for a failed deploy · Add a health check URL to catch bad releases that deploy green

Related: How to automatically revert a failed deploy (and when not to) · GitHub checks explained: check runs, commit statuses and required checks · Releasing outside business hours: a checklist for small teams