Skip to content
Module
Module 5 of 6Lesson 1 of 2~17 min

The safety nets that protect production

A mistake that reaches production is expensive, and good intentions do not stop it, the safeguards in place do. This lesson helps you assess the protections of a repository, from platform rules to controlled rollouts, and propose to the team the ones that are missing most.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to audit a repository's safety nets (branch protection or rulesets, required checks, mandatory review, preview and staging, feature flags, progressive rollout) and propose, with a metric, the ones it lacks most.

Topics covered

  • branch protection
  • feature flags
  • progressive rollout
  • staging
  • protecting production

In the glossary

Full glossary

Where it fits

Safety nets and rollback

What stops a mistake from reaching users, and what do I do if it gets through anyway?

Lessons in this module

  1. The safety nets that protect production (this lesson)
  2. Undo a change without making things worse

What you will learn in this module

This lesson is part of the course Git for PMs: ship as a team without putting production at risk

  • Assess a repository's safety nets (branch protection, required checks, mandatory review, feature flags, staging, progressive rollout) and propose the missing ones.
  • Choose the right way to undo a change (restore, revert, reset, deployment rollback) depending on whether it is local, pushed, merged or already in production.

Related courses