Scheduling a merge: a GitHub Actions cron job vs Merge Scheduler

A scheduled GitHub Actions workflow is the first thing most developers try. It works, and for one repository and a simple merge it can be enough. This page lists what you have to build around it, and where the edges are.

The cron workflow

A workflow with a schedule trigger runs on the default branch at a time you write in cron syntax. A job in it runs gh pr merge for the pull request you name.

Things you have to add yourself

What Merge Scheduler does instead

You pick the pull request and the time in the app. It pins the commit, re-checks everything at merge time, merges, watches the GitHub Actions deploy, emails the result, and can revert a failed deploy. The first 10 releases on the Free plan include auto-revert. Ordered multi-repo releases, health checks and the dashboard are on Pro.

Quick comparison

Cron workflowMerge Scheduler
CostFree (Actions minutes)Free plan; Pro from the pricing page
SetupWrite and maintain a workflowInstall the GitHub App, choose repos
Skips the merge if someone pushes after reviewOnly if you code itYes, the commit is pinned
Watches the deployOnly if you code itYes
Reverts a failed deployOnly if you code itYes (first 10 releases free, then Pro)
Backend then frontend, in orderChain workflows yourselfYes (Pro)
Your code stays in your repoYesYes, it does not store your code

Which to choose

One repository, a merge you rarely schedule and a deploy you are happy to check by hand: the cron workflow is fine. Releases outside working hours that you want merged, watched and rolled back without staying up: that is the case Merge Scheduler was built for. They also work together, since the deploy can stay an ordinary Actions workflow.

Do this in Merge Scheduler: Schedule your first merge

Related: GitHub auto-merge, merge queue and scheduled merge: what each is for · Merge Scheduler vs Merge Freeze: blocking merges vs performing them