5 collocation exercises on contributing to open-source projects.
0 / 5 completed
1 / 5
To report a bug upstream, you ___ an issue.
You open an issue — creating a tracked report of a bug or feature request in a project's issue tracker. Open collocates with issue, PR and ticket (the opposite is close an issue). Crack off, start up and launch out are not idiomatic. Opening a clear, well-described issue with reproduction steps is the first step in most open-source contributions and helps maintainers respond effectively.
2 / 5
To propose a code change, you ___ a PR.
You submit a PR (pull request) — proposing your changes for the maintainers to review and merge. Submit collocates with PR and patch (you also open or raise a PR). Send off, post up and lodge out are not the standard collocation. Submitting a focused PR with a clear description and passing tests greatly improves the chance maintainers will review and accept it.
3 / 5
After opening a PR, you may ___ a review.
You request a review — explicitly asking specific maintainers or teammates to look at your PR. Request collocates with review, changes and feedback. Beg off, ask up and seek out are not idiomatic. Requesting a review notifies the right reviewers and moves your PR forward; without it, a contribution can sit unnoticed in a busy project's queue for a long time.
4 / 5
Once approved, maintainers ___ your changes upstream.
Maintainers merge your changes upstream — integrating your branch into the main project repository. Merge collocates with PR, branch and changes (merge upstream). Fuse off, join up and blend out are not idiomatic. Merging upstream is the goal of a contribution: your code becomes part of the canonical project, available to everyone who uses it going forward.
5 / 5
To publish a new version, maintainers ___ a release.
Maintainers cut a release — tagging a version and publishing it (the idiom comes from cutting a tag or branch). Cut is the standard collocation here (cut a release, cut a tag). Slice off, carve up and chop out are not idiomatic. Cutting a release bundles merged changes into a versioned, downloadable artifact, often with release notes summarising what is new for users.