Stage 6 · Lesson 5 of 8

Giving and receiving review

is how a team shares knowledge and catches problems before they ship. As a reviewer, check that the change does what it claims. Look for bugs and missing tests.

Write comments as questions or suggestions, and make clear which ones must be fixed and which are just preferences. As the author, reply to every comment and push fixes as new commits during the review. Try not to take comments personally.

On , reviewers can suggest exact code changes, then approve or ask for changes. Reviewing other people's is one of the fastest ways to learn a .

Common trapapproving without reading, or arguing in comments when a short call would settle it.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with· follow one of these

BookFree
Pro Git
Scott Chacon and Ben Straub
Chapter 6 covers GitHub itself: forks, pull requests and maintaining a project
GuideFree
Contributing to a Project (GitHub Docs)
GitHub · Beginner
GitHub's own walkthrough of the fork, branch and pull request workflow

Practise

First Contributions
A safe repository built for making your first pull request to someone else's project

Keep handy

Connecting to GitHub with SSH (GitHub Docs)
Official steps for generating, adding and testing SSH keys on each operating system
GitHub CLI
The gh manual for pull requests, issues and CI from the terminal

Also worth your time

Conventional CommitsRead
A widely used commit message convention you will meet in many repositories
roadmap.sh: Git and GitHubGo deeper
The GitHub half of the map: Actions, projects, security features and more