Deploy on Fridays? Freeze merges, not deploys

Many teams ban Friday deploys. The thinking is simple: if something breaks, nobody is around to fix it on the weekend. The ban solves a real problem. It also creates one.

What a deploy freeze costs

If merges keep happening but deploys stop, changes pile up and go out together on Monday. Bigger releases are harder to understand, harder to test and harder to roll back. Engineers such as Charity Majors have argued that a blanket Friday freeze can hide risk instead of removing it, and that if you want to protect people's time off, you should hold the merge, not the deploy.

Freeze merges instead

The idea: keep deploying small changes continuously, and decide when each change is allowed to become part of main. A pull request that is approved on Thursday evening waits. It merges on Monday morning when people are at their desks, and deploys right away as a small, understood change.

How to do it

Blocking versus doing

There are two separate jobs here. Blocking merges at certain times is done by freeze tools and branch rules. Making a merge happen at a chosen time is scheduling. You can use both: block ad hoc merges on Friday afternoon, and schedule the ones you want for Monday.

A small checklist

Where Merge Scheduler fits

Merge Scheduler merges the exact approved commit at the time you choose, watches the GitHub Actions deploy, emails the result, and on paid plans reverts a failed deploy automatically.

Do this in Merge Scheduler: Schedule your first merge

Related: Merge Scheduler vs Merge Freeze: blocking merges vs performing them · Releasing outside business hours: a checklist for small teams · Why a scheduled merge should pin the commit you approved