Module 2 · Git and how code actually ships Lesson 5 of 15

Pull requests and code review

Worked example

A PR with fourteen unrelated changes cannot be reviewed and will be approved unread, which is worse than no review. Ten small PRs get read.

Your practice task

Open a PR against one of your own repositories with a proper title and description, then review it as if you were the reviewer and leave two comments.

Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.

Key takeaway

A pull request is how a change gets discussed before it lands. One small change, a title that says what it does, and a short description of why — that is a good PR, and nobody cares how much code it contains.

Almost there

15 lessons left of 15

Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.