Module
Module 4 of 6Lesson 2 of 3~21 min

Review, checks, preview and merge

Lesson 2 of the module "Take a pull request all the way to merge" in the course "Git for PMs: ship as a team without putting production at risk".

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

Lesson objective

By the end of this lesson, you will be able to respond to a review, interpret required checks, use the preview as an acceptance test and choose a merge method (merge commit, squash, rebase), knowing its effect on history.

Where it fits

Take a pull request all the way to merge

How do I get a fast review, pass the checks and merge without surprises?

Lessons in this module

  1. Open a pull request the team wants to review
  2. Review, checks, preview and merge (this lesson)
  3. Resolve a conflict without panicking

What you will learn in the course

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

  • Read an existing repository and its pipeline (README, CONTRIBUTING, CODEOWNERS, CI workflows, environments) to know who reviews what, what gets checked and what goes to production, and when.
  • Work on a short-lived branch with everyday Git commands (or their GitHub equivalents), small commits named by convention, and stay in sync with main.
  • Open a small, well-described pull request, get the right review, pass the required checks, validate the preview and choose the merge method.
  • Resolve a simple merge conflict calmly, on the command line or in GitHub, and know when to ask for help.
  • 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.
  • Keep an AI coding agent under control in a team repository (dedicated branch, written rules, protected secrets, proof of verification, human review before merge).
  • Tie merged changes to a release (tag, semantic versioning, changelog) and write release notes that help users.

Related courses