Skip to content
Module
Module 4 of 6Lesson 2 of 3~21 min

Review, checks, preview and merge

Between reviewer comments, automated checks and the merge button, the last step of a pull request often feels intimidating. This lesson helps you handle a review, make sense of a failing check, validate your change on the preview and choose how to merge while knowing the consequences.

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.

Topics covered

  • code review
  • CI checks
  • preview environment
  • squash and rebase
  • merging a pull request

In the glossary

Full glossary

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 this module

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

  • 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.

Related courses