Learn to write effective PR templates and PR description language.
0 / 5 completed
1 / 5
What is the purpose of a pull request template (.github/PULL_REQUEST_TEMPLATE.md)?
A PR template pre-fills the PR description with a structure — e.g., Summary, Changes, Testing, Screenshots — guiding contributors to provide context reviewers need.
2 / 5
What is a 'checklist' in a PR template?
A checklist (using - [ ] syntax in Markdown) in a PR template prompts authors to verify: 'Tests pass', 'Documentation updated', 'Breaking changes documented' — improving PR quality.
3 / 5
What is a 'draft pull request' on GitHub?
A draft PR (draft: true or using the 'Draft' button) signals work in progress — CI runs, collaborators can comment, but reviewers know not to do a final review until it is marked 'Ready for review'.
4 / 5
What does 'breaking change' mean in a PR description?
A breaking change is a modification that removes or changes an existing interface in a non-backward-compatible way — requiring downstream consumers to update their code. Must be clearly documented in the PR.
5 / 5
What is a 'review decision' on GitHub?
A review decision is the formal outcome of a GitHub review: Approve (ready to merge), Request changes (must be addressed before merging), or Comment (non-blocking feedback).