@r2d2 agreed! By default I think most people code review PRs as a whole, and look at the file diffs one by one. To avoid this question's scenario, sometimes I purposefully do PR's with a largish number of commits because they need to all land together, and in those cases I instruct the reviewers to review each commit in order, rather than all the files separately for the entire PR. This enables the reviewer to keep some mental context for each change and is less daunting of a review. That said, when necessary I'll still branch off of a teammate's incomplete branch knowing it's gonna change... —
TTT 6 secs ago