Skip to content
Module
Module 4 of 6Lesson 1 of 3~18 min

Open a pull request the team wants to review

A pull request that is too big or poorly described sits waiting and ends up reviewed in a rush. This lesson teaches you to propose a small, well-presented change, with the context reviewers need, addressed to the right reviewers and ready to be tested.

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

Lesson objective

By the end of this lesson, you will be able to open a small, complete pull request: clear title, description (why, what, how to test, risks), link to the ticket, draft or ready status, and the right reviewers thanks to CODEOWNERS.

Topics covered

  • pull requests
  • PR description
  • code review
  • CODEOWNERS
  • GitHub

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 (this lesson)
  2. Review, checks, preview and merge
  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