Scheduled-PR alternative: merge at a set time, then watch the deploy
Scheduled-PR is a tool that merges a pull request at a time you choose, on GitHub and Azure DevOps. This page describes it from its public website as read on 11 November 2026. Plans and features change, so check its current pages before you decide.
How Scheduled-PR works
- It runs as a GitHub app, or as an extension on Azure DevOps.
- You set the merge time with a slash command in a pull request comment, with a label, or in its dashboard.
- At that time it merges only if the pull request is still healthy: open, no conflicts, checks green, approvals in place.
- It keeps one bot comment on the pull request and updates it with the status and the reason for any delay.
- A config file in the repository can set blackout windows, such as no merges on Friday afternoons or at weekends.
- Its site lists a free tier with a small monthly limit on scheduled pull requests, and paid plans for personal and organization use.
Why people look for an alternative
- The free tier limit is reached quickly if you release often.
- The merge is where the work starts for most teams: the deploy follows. Its public pages describe the merge, not the deploy that follows.
- Releases that need two repositories in order, such as backend then frontend, are not described.
- You may want to set merges from a form, a script or an AI assistant instead of a comment.
What Merge Scheduler adds
- You pick the pull request and a time zone in a form, not in a comment.
- 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).
- No-merge windows per repo, set in the dashboard. A merge that comes due inside one is skipped and the team is emailed.
- Ordered releases and night queues of up to 10 pull requests.
- Alerts by email, Slack, Discord and phone alarm, plus webhooks, an API and an MCP server.
Quick comparison
| Scheduled-PR | Merge Scheduler | |
|---|---|---|
| Merges at a set time | Yes | Yes |
| How you set the time | Comment command, label or dashboard | Form, API or AI assistant |
| Re-checks at merge time | Yes: conflicts, checks, approvals | Yes, and the commit is pinned |
| No-merge windows | Yes, in a config file in the repository | Yes, in the repo settings: a merge due inside one is skipped and you are emailed |
| Watches the deploy | Not described | Yes |
| Reverts on failure | Not described | Yes (Pro) |
| Backend then frontend in order | Not described | Yes |
| Azure DevOps | Yes | No, GitHub only |
| Free plan | Yes, with a monthly limit | Yes, for small teams |
When to choose which
- You use Azure DevOps, or you want the no-merge windows kept as a file in the repository: Scheduled-PR.
- You only need the merge at the right time, for a few pull requests a month: Scheduled-PR is simple and does that.
- Each merge starts a deploy and you want it watched and reverted for you, or you release in a set order: Merge Scheduler.
- You want to set merges from a form, a script or an AI assistant: Merge Scheduler.
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: PR Scheduler alternative: when a timed merge is not enough · Merge Scheduler vs Merge Freeze: blocking merges vs performing them · Deploy on Fridays? Freeze merges, not deploys