LEARN. PRACTICE. GROW.Concept and mechanism
A go/no-go decision combines technical evidence, operational capacity, and accepted risk. Define service-appropriate criteria in advance: relevant tests, compatibility, monitoring, recovery, dependencies, and available people. If an essential requirement is unmet, a nearby deadline does not turn it into approved evidence. Make the deviation explicit and route the decision to the appropriate authority. Checklists should reflect real risks and learn from previous incidents; copying a long list without understanding context can hide important questions. Also confirm who performs business validation and who can stop the operation. Readiness needs to exist before the team disperses for the weekend.
Guided application
Platform controls work only within their configured scope. In GitHub Actions, environment rules apply to jobs referencing that environment. A required-reviewer list does not demand approval from everyone by default; preventing self-approval is a specific option. In GitLab, a freeze window provides CI_DEPLOY_FREEZE and job rules need to consume that signal to enforce the documented block. A calendar without enforcement does not demonstrate protection. Features vary by plan and configuration. For an emergency, use the agreed accelerated process with a decision maker, criteria, and evidence; record deferred checks and follow them through. Urgency is not a silent waiver of all validation.
An approval rule on an environment does not protect a job that bypasses it.
Common pitfalls
Approval as health; calendar-only freeze; emergency as unrecorded bypass.
Related topics: Scope and coordination · Artifacts and traceability · Exposure and observation
Decide using evidence and confirm controls cover the actual execution path.
Reference: Launch coordination dependencies capacity and operational processes · Release management practices 2026-09; scoped GitLab GitHub CodeDeploy and EF Core documentation