Every developer participates in code review, but do you use the right collocations? Raise a PR, request changes, and rebase onto main are the standard professional phrases. These exercises will ensure you sound fluent and precise in pull request workflows.
0 / 5 completed
1 / 5
Once you've committed your changes locally, the next step is to ___ against the main branch.
Raise a PR is the standard British English collocation in professional software teams. While 'open a PR' is also common (particularly in US English), 'raise' is the professional standard in many enterprise and UK engineering contexts — similar to 'raise a ticket'.
2 / 5
The reviewer felt the error handling was insufficient and decided to ___ with detailed comments.
Request changes is the exact terminology used by GitHub, GitLab, and Bitbucket for the review action that blocks a merge. It is the formal collocation for a reviewer indicating that work is required before approval.
3 / 5
After addressing all feedback, the senior engineer was happy to ___ and unblock the deployment.
Approve the PR is the standard collocation matching the review status in all major version control platforms. Reviewers approve pull requests — this is both the platform action and the professional vocabulary.
4 / 5
Once two reviewers approved, the feature was ready to ___ and trigger the CI/CD pipeline.
Merge to main is the standard Git workflow collocation. 'Merge' is the specific Git operation of integrating one branch into another. 'Push to main' is a different action (sending commits to a remote), and 'combine'/'join' are not idiomatic in Git contexts.
5 / 5
Before submitting the PR, she needed to ___ to incorporate the latest bug fixes.
Rebase onto main is the correct Git collocation. 'Rebase' is a specific Git operation that moves or replays commits on top of another branch. The preposition 'onto' is standard with rebase. 'Sync' and 'update' describe the goal but not the Git operation.