Skip to content
Module
Module 5 of 6Lesson 2 of 2~18 min

Undo a change without making things worse

When something goes wrong, rushing often leads to a move that makes the damage worse. This lesson teaches you to choose the right way to roll back depending on where the change sits, from your own machine all the way to production, without ever rewriting shared history.

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

Lesson objective

By the end of this lesson, you will be able to choose the right way to undo a change depending on where it is (file, local commit, shared branch, main, production): git restore, git reset, git revert, a pull request's Revert button or a deployment rollback, without ever forcing shared history.

Topics covered

  • undo a commit
  • git revert
  • git reset
  • deployment rollback
  • force push

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
  2. Undo a change without making things worse (this lesson)

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