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

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

Quick comparison

MergifyMerge Scheduler
Merge only inside a time windowYes, with a schedule conditionNo-merge windows per repo (windows over midnight are allowed)
Merge one pull request at a chosen dateNot its main modelYes
Freeze merges for a periodYes, scheduled freezesYes, no-merge windows
Merge queue for many pull requests a dayYesNight queues of up to 10
Watches the deployNot described in the pages readYes
Reverts on failureNot described in the pages readYes (Pro)
SetupA rule file in the repository, plus a dashboardForms in the dashboard, API or AI assistant

When to choose which

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