Practice English vocabulary for responding to PR review feedback as an open-source contributor: addressing changes, rebasing, handling CI failures, and adding tests.
0 / 10 completed
1 / 10
The maintainer left review comments asking you to change your code. You have made the changes. What do you write in your follow-up comment?
'The reviewer requested changes — addressing them now' is the standard phrase to signal that you have seen the feedback and are actively working on the requested modifications.
2 / 10
The maintainer asked you to sync your branch with the latest main branch commits before they merge. You have done this. What do you say?
'I've rebased on main as requested' means you used git rebase to replay your commits on top of the latest main branch. Maintainers often prefer rebase over merge to keep a clean commit history.
3 / 10
The CI pipeline shows a failing test, but the test was already failing before your changes — it is an unreliable test. How do you explain this?
'A flaky test' is the standard term for an intermittently failing test — one that fails non-deterministically, not due to your change. Always clarify this distinction to maintainers.
4 / 10
The maintainer asked you to add a unit test for the new function you introduced. You have written the test. What do you comment?
'Adding it now' signals that you are actively implementing the requested test. This is the standard pattern for acknowledging a specific review request and confirming compliance.
5 / 10
You have addressed all the reviewer's comments and pushed the updates. What do you write to let them know the PR is ready for re-review?
'All comments addressed — ready for re-review' is the standard message to ping the reviewer after responding to all their feedback, inviting them to take another look at the PR.
6 / 10
You've just received a comment from Sarah regarding a potential bug in your new function. She highlights a scenario where the input data might cause unexpected behavior. What's the best way to respond directly in a PR comment?
The key here is to acknowledge the feedback and request clarification. Option 2 reflects a common response – acknowledging that it's not clear enough and requesting more information before proceeding with changes. Options A and D are dismissive or overly proactive; option B is an inappropriate reaction to constructive criticism.
7 / 10
During a code review, David points out that your variable names aren't descriptive enough. He suggests using more specific names for better readability. How should you respond in a Slack message to him?
A good response shows you're open to suggestions. Option 3 demonstrates a willingness to learn and understand David's perspective by asking for specific examples. Options A and B are too brief; option D is dismissive.
8 / 10
The CI pipeline fails after you've pushed your changes. The error message indicates a missing dependency. You've confirmed the dependency is correctly installed in your environment. What should you state in the PR description to update the reviewer?
Transparency is crucial. Option 3 communicates the issue effectively, showing you've investigated and are aware of the solution. It provides context for the reviewer and demonstrates your proactive approach to debugging. Options A and B are unhelpful; option D is a bad practice.
9 / 10
You've completed all changes requested by the reviewer and pushed them to your branch. You want to signal that you're ready for another review. What would be a suitable message to include in the PR description?
Option 3 is professional and informative. It explicitly states that you've resolved the concerns and indicates your availability for continued collaboration. Options A and B are too terse; option D is a critical error.
10 / 10
During a standup meeting, you briefly mention that you're addressing feedback from a recent code review. Your team lead asks for more details about the changes you made. How should you respond?
A standup is about updates, not technical deep dives. Option 3 provides a high-level overview that satisfies the team lead's curiosity without overwhelming them with details. Options A and B are too vague; option D avoids collaboration.
What will I practise in "PR Review as a Contributor"?
This module focuses on Open Source Contribution — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Open Source Contribution exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around open source contribution — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Open Source Contribution exercises?
See the Open Source Contribution hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.