Schedule the merge. If the deploy fails, it reverts itself.

Pick a pull request and a time. Merge Scheduler merges, watches your GitHub Actions deploy, and if the deploy fails it opens and merges a revert pull request — then tells you why it failed.

Features

• Merge at a set time with prechecks and a pinned commit
• Deploy watch with email
• Automatic revert on a failed deploy
• Ordered releases across backend and frontend repositories
• Why-it-failed reports, revert-risk and conflict checks, health checks
• Manager dashboard and weekly summary

Questions

What does Merge Scheduler do?

You pick a GitHub pull request and a time. It merges at that time, watches your GitHub Actions deploy, and if the deploy fails it opens and merges a revert pull request and tells you why it failed.

Does it need access to my code?

No. It is a GitHub App installed only on the repositories you choose. It uses pull request, workflow and checks metadata to merge and watch deploys. It does not store your source code.

Is there a free plan?

Yes. Free covers 2 repositories and 30 scheduled releases a month with deploy watch and email. Viewers are always free. Auto-revert, ordered multi-repo releases, health checks and the dashboard are on Pro.

What happens if someone pushes after I schedule a merge?

The pull request's commit is pinned when you schedule. If new commits appear, the release is skipped instead of merging code nobody reviewed.

Can I release a backend and a frontend in order?

Yes. Group several repositories into one release and choose when each step starts: after the previous deploy succeeds, a few minutes after it merges, or timed so both finish together.