Mergify scheduled merges vs Merge Scheduler: a window or a date
Mergify is a merge automation tool for GitHub. It can limit when pull requests merge. This page describes that from its public documentation as read on 15 November 2026. Plans and features change, so check its current docs before you decide.
How Mergify handles time
- A schedule condition allows merging only inside a window, for example Monday to Friday, 09:00 to 17:00, in a time zone you name. The time zone defaults to UTC.
- Used in a merge queue rule, the condition keeps pull requests waiting until the window opens.
- A window must start and end within one day, so a window over midnight is written as two parts.
- A scheduled freeze blocks merges for a chosen period. It covers one window. For a repeating block, such as weekends, its docs suggest a rule with a schedule condition.
- A freeze or condition only stops merges that Mergify evaluates. To stop merges made outside Mergify, its docs say the Mergify check must be required in GitHub.
Two different jobs
Mergify works as a rule: merge pull requests that pass, only in these hours. It is strong when many pull requests flow through a queue every day. Merge Scheduler works as an appointment: merge this one pull request at 02:00 tomorrow, then watch what happens. Teams that release at fixed times, often at night, usually think in appointments.
What Merge Scheduler adds
- You pick the pull request, the date, the time and the time zone in a form. No rule file is needed.
- Prechecks run again at merge time, and the commit is pinned: a push after you scheduled is skipped, not merged.
- It watches a GitHub Actions deploy, or a health URL if you deploy another way.
- If the deploy fails, it opens a revert pull request and tells you why (Pro).
- Ordered releases, such as backend then frontend, and night queues of up to 10 pull requests.
- No-merge windows per repo. A merge that comes due inside one is skipped and the team is emailed.
- Alerts by email, Slack, Discord and phone alarm, plus webhooks, an API and an MCP server.
Quick comparison
| Mergify | Merge Scheduler | |
|---|---|---|
| Merge only inside a time window | Yes, with a schedule condition | No-merge windows per repo (windows over midnight are allowed) |
| Merge one pull request at a chosen date | Not its main model | Yes |
| Freeze merges for a period | Yes, scheduled freezes | Yes, no-merge windows |
| Merge queue for many pull requests a day | Yes | Night queues of up to 10 |
| Watches the deploy | Not described in the pages read | Yes |
| Reverts on failure | Not described in the pages read | Yes (Pro) |
| Setup | A rule file in the repository, plus a dashboard | Forms in the dashboard, API or AI assistant |
When to choose which
- Many pull requests merge every day and you want rules, a queue and freezes: Mergify.
- You release at set times and want each merge watched and reverted if the deploy fails: Merge Scheduler.
- You want to set a merge for tomorrow night without writing a rule: Merge Scheduler.
- You can also use both. Mergify for daily flow, Merge Scheduler for the planned releases.
Neither tool replaces your own safeguards. Keep reviews, tests and a way to roll back by hand. Merge Scheduler reduces the risk of late-night releases but cannot undo data, such as a database migration.
Do this in Merge Scheduler: Connect GitHub and add your first repository · Schedule your first merge
Related: Merge Scheduler vs Merge Freeze: blocking merges vs performing them · Scheduled-PR alternative: merge at a set time, then watch the deploy · GitHub auto-merge, merge queue and scheduled merge: what each is for