Merge Scheduler vs Automergic: scheduling a merge, with and without the deploy
Both tools schedule a GitHub pull request to merge at a time you choose. This page describes Automergic from its public website and documentation as read on 2 November 2026. Details change, so check its current pages before you decide.
Automergic
A web service that merges a pull request at a scheduled time. You sign in with GitHub, pick a pull request, a time and a merge method, and it merges then.
- Minute-level scheduling with time zone support.
- Merge, squash or rebase.
- Alerts by email, Slack or Discord, and an audit log.
- Sign-in uses GitHub OAuth. Its documentation lists the requested permissions as repo and read:user.
- It has a free plan and paid plans. Its pricing page has the current limits and prices.
Merge Scheduler
The same first step, plus what happens after the merge. It merges at the time you pick, watches your deploy, and reverts if the deploy fails.
- Prechecks run again at merge time, and the commit is pinned: a push after you scheduled is skipped, not merged.
- It waits for required checks that are still running and skips with a reason when they fail.
- It watches a GitHub Actions deploy, or a health URL if you deploy another way, and opens a revert pull request on failure.
- Ordered releases across repositories, such as backend then frontend.
- Alerts by email, Slack, Discord and phone alarm, plus webhooks, an API and an MCP server.
- Access is a GitHub App installed only on the repositories you choose, or an optional fine-grained token.
Quick comparison
| Automergic | Merge Scheduler | |
|---|---|---|
| Merges at a set time | Yes | Yes |
| Merge methods | Merge, squash, rebase | Merge, squash, rebase |
| Re-checks at merge time | Open and mergeable | Conflicts, approvals, checks, pinned commit |
| Watches the deploy | Not described | Yes |
| Reverts on failure | Not described | Yes (Pro) |
| Access | OAuth, repo scope | GitHub App on chosen repos, or a fine-grained token |
| Alerts | Email, Slack, Discord | Email, Slack, Discord, phone alarm, webhooks |
| API | Not described | REST API, webhooks, MCP |
When to choose which
- You only need a pull request merged at a set time, and you are happy to check the deploy yourself: Automergic is simple and does that.
- The merge starts a deploy, and you want it watched and reverted for you, or you release in a set order: Merge Scheduler.
- Access matters to you: with a GitHub App you choose the repositories, while the repo OAuth scope covers every repository your account can reach.
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: How to schedule a GitHub pull request merge (4 ways) · Merge Scheduler vs merge-schedule-action and Mergify schedules · How to automatically revert a failed deploy (and when not to)