5 collocation exercises on giving and receiving review feedback.
0 / 5 completed
1 / 5
Which verb completes: "Could you ___ this comment before we merge?"
In code review, you address a comment — meaning you act on the reviewer's feedback by changing the code or replying with a justification. Address is the conventional collocation in pull-request workflows on GitHub, GitLab and similar platforms. You would not say answer a comment in this technical sense, and solve or fix up sound informal and imprecise. Once every comment is addressed, the reviewer can re-review and the branch becomes eligible to merge.
2 / 5
A reviewer who is not happy with a PR will ___.
The formal review state in most tools is request changes. When a reviewer selects this option, the pull request is blocked until the author updates the code and the reviewer re-approves. The phrasing is fixed: we say request changes, never demand edits or order fixes, which sound aggressive and unprofessional. This collocation appears directly on the review UI, so learners encounter it constantly in day-to-day engineering work.
3 / 5
To offer a small improvement inline, you ___ a suggestion.
You leave a suggestion on a specific line of code. GitHub even has a suggestion block that lets the author commit your proposed change with one click. The natural verb is leave (you also leave a comment or leave feedback). Plant and post out are not idiomatic, and drop down means something different. Leaving suggestions is a polite, low-friction way to nudge improvements without blocking the merge.
4 / 5
Once a discussion is settled, the reviewer should ___ the thread.
You resolve a thread when a review conversation has reached its conclusion and no further action is needed. Marking threads as resolved keeps the pull request tidy and signals which discussions are still open. The collocation is fixed: resolve a thread or resolve a conversation. Close off, finish and seal are not used here. Many teams require all threads resolved before a PR can be merged.
5 / 5
To signal a PR is ready to merge, you ___ it.
The standard verb is to approve a pull request. Approval is the positive review state that unblocks merging, the opposite of request changes. We say approve a PR or approve the changes. While green-light exists informally, green-light off is wrong, and accept up and pass through are not collocations. Once enough reviewers approve, branch protection rules typically allow the merge to proceed.