Pull Request Review Etiquette Language Collocations
Practise the standard verbs for giving clear, constructive pull request reviews.
0 / 5 completed
1 / 5
Fill in: 'We ___ pull request review etiquette by leaving specific, actionable comments, rather than a critique nobody submitting the code can actually act on.'
We 'follow etiquette' — the standard, simple collocation for observing constructive review norms. The other options are less idiomatic here.
2 / 5
Fill in: 'A vague, unexplained review comment can ___ the author guessing at a fix nobody's actually specified clearly.'
We say a vague comment will 'leave' the author guessing — the standard, natural collocation for the resulting confusion. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ nitpicks separately from blocking issues in a review, rather than a comment thread nobody can actually tell apart.'
We 'label a nitpick' — the standard, simple collocation for distinguishing minor comments from blockers. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every reviewer's comment against the actual diff before requesting changes, rather than feedback nobody's actually re-read in context.'
We 'check a comment' — the standard, simple collocation for confirming feedback matches the real code change. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ review turnaround time across the team weekly, rather than a stalled pull request nobody's actually chased.'
We 'track turnaround' — the standard, simple collocation for monitoring how quickly reviews get done. The other options aren't idiomatic here.