Guide

How to review a large pull request on GitHub

Hide the noise, review in passes, and track what you have read.

1. 1Read the description first

   Decide what changes and where the risk is. A few files usually carry the decision.

2. 2Hide the noise

   Shift-click .lock and other generated types. Open Smart filters for categories and busy folders.

3. 3Review in passes

   Core logic, then tests, then the rest. Short sessions catch more than one long one.

4. 4Mark what you read

   Tick Viewed on files or folders and turn on Hide viewed. A new push brings changed files back.

5. 5Keep doubts private

   Write notes, ask your AI about them, then post only what still matters.