Practice English vocabulary for responding to PR review feedback as an open-source contributor: addressing changes, rebasing, handling CI failures, and adding tests.
0 / 5 completed
1 / 5
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 / 5
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 / 5
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 / 5
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 / 5
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.