Use Merge Scheduler with Vercel, Netlify or another deploy tool
By default Merge Scheduler follows the GitHub Actions deploy that a merge starts. Vercel, Netlify, Render, Argo CD, Jenkins and similar tools deploy outside GitHub Actions, so there is no run to follow. Health-only mode covers them: it checks that your site is healthy instead.
Set it up
- Open Settings, Repositories, Edit on the repository.
- Under How do we know the deploy worked?, choose Something else.
- Set Wait for the deploy to go live: the minutes your tool normally needs, for example 5 for a Vercel build. 0 to 60.
- Under Health checks, add the branch and a health URL, for example https://app.example.com/health. It is required in this mode.
- Save.
What happens
- The pull request merges at your time, with the same prechecks and pinned commit as always.
- It waits for the deploy to settle, then checks the health URL once a minute for the Watch health for time (5 minutes by default).
- Two failures in a row count as a bad release. With auto-revert on, a revert pull request is opened and merged, then it waits for the health check to pass again. If it does not recover, you get a needs-attention email.
- If the site stays healthy, the release is done.
What it cannot see
- It does not know whether the deploy finished, only whether the site answers. If the deploy is slower than your wait, a healthy old version can look fine while the new one is still building. Set the wait with some margin.
- A health URL that returns 200 while the app is broken hides problems. Make it check something real, such as a database call.
- Health checks are on Pro. A free account gets one release with a health check to try.
Background reading: Why a merged pull request didn't start your deploy workflow
More guides: Add a health check URL to catch bad releases that deploy green · Set up automatic revert for a failed deploy