The NoShip Blog
Field notes on code freezes, change freezes, deployment safety, and release governance for teams shipping through GitHub. Written for the engineers and SREs who own the merge button when the stakes are high.
A code freeze backed by an automated audit trail satisfies SOC 2 CC8.1 change management requirements. Here is what auditors look for, what your logs must contain, and how to enforce it on GitHub.
Change management for software engineering teams is about controlling which changes reach production, and when, without ITIL-style approval overhead. Here is what lightweight looks like.
Friday deploys are risky because weekend response capacity drops, not because the code is worse. Here is when the risk is real and what to do about it.
Scoping a code freeze means freezing only the repositories, branches, and environments that carry real risk, not the whole org. Here is how to draw the line.
How to announce a code freeze: what to include, when to send it, and a ready-to-copy Slack template. Covers timing, channels, and the override process.
A copy-paste code freeze policy template covering scope, schedule, enforcement, overrides, roles, and audit, plus a filled-in example you can adapt today.
The deploy backlog after a code freeze is the most dangerous part of the freeze. Here is how to release the queue in a controlled order instead of all at once.
A recurring code freeze runs on a schedule automatically. Here is how to configure Friday windows, quarterly freezes, and biweekly release patterns in RRULE.
An emergency deploy during a freeze needs a structured approval path, not a workaround. Here is how to design one that is fast enough to use and controlled enough to trust.
Code freeze best practices: scope, duration, automated enforcement, a real override path, and thaw planning. A practical checklist for release managers.
A holiday code freeze protects production during year-end coverage gaps. Here is how to scope it, schedule it, handle emergencies, and lift it cleanly.
Code freezes reduce incident rates during high-risk windows, but only when scoped, automated, and paired with a real override path. Here is what the research supports.
Blocking merges to main in GitHub requires a required status check tied to a service that posts failure during a freeze. Here is how to set it up, scale it, and handle emergency overrides.
Code freeze, change freeze, and deployment freeze each stop something different. Here is how to tell them apart and choose the right one for your situation.
Freezing deployments in GitHub requires two controls: required status checks to block merges and deployment protection rules to block releases. Here is how to set up both.
The best Merge Freeze alternatives for GitHub, compared by enforcement depth, scheduling, override workflows, and migration path from Merge Freeze.
Compare the four main approaches to code freezes on GitHub: branch protection, rulesets, Merge Freeze, and NoShip. Find the right fit for your team.
A code freeze temporarily halts merges and deployments during high-risk windows. Here is what it is, when to use one, and how to run it without blocking your team.