Open Source Pull Request Etiquette Language Collocations
Practise the standard verbs for contributing to open source projects respectfully.
0 / 5 completed
1 / 5
Fill in: 'We ___ an issue with a maintainer before submitting a large pull request, so hours of unwanted work aren't spent on a change the project never intended to accept.'
We 'raise an issue' — the standard, simple collocation for opening a discussion before doing significant unsolicited work. The other options are less idiomatic here.
2 / 5
Fill in: 'Sending in a huge, unannounced pull request touching dozens of files can ___ a maintainer with limited review time simply closing it unread.'
We say an unannounced large PR will 'leave' a maintainer closing it unread — the standard, natural collocation for the resulting outcome. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the project's contribution guide closely before opening a PR, since a maintainer's stated conventions on tests and commit style are rarely optional in practice.'
We 'follow a guide' — the standard, simple collocation for adhering to a project's documented contribution rules. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ review feedback promptly and without defensiveness, since a maintainer's time is genuinely limited and a stalled conversation often just gets deprioritised.'
We 'address feedback' — the standard, simple collocation for responding constructively to review comments. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ credit generously to a co-contributor in commit messages and release notes, since open-source work is often the only visible record of someone's effort.'
We 'give credit' — the standard, simple collocation for acknowledging a collaborator's contribution. The other options are less idiomatic here.