Where does the PR template live?

The default location is .github/PULL_REQUEST_TEMPLATE.md at the repository root inside the .github folder. GitHub also accepts it in the repo root or a docs folder, but the .github path is the convention.

How do the Type of Change checkboxes work?

They are Markdown task-list items written as dash, space, open bracket, space, close bracket. GitHub renders them as clickable checkboxes the author ticks to classify the change as a fix, feature, docs update, or refactor.

Can I have more than one PR template?

Yes. Put multiple files under .github/PULL_REQUEST_TEMPLATE/ and select one via the template query parameter on the compare URL. A single root file applies to every PR automatically.

Why include a testing section?

Asking the author to spell out how they verified the change shortens review. Reviewers can re-run the listed steps instead of guessing, which catches regressions before merge.

Does the checklist enforce anything?

Checkboxes are advisory, not blocking, by themselves. To enforce them you would add a status check via a GitHub Action, but even unenforced they nudge authors to self-review against your standards.

GitHub Pull Request Template Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

A pull request template pre-fills every PR description with the structure your reviewers expect: what changed, how it was tested, and a self-review checklist. This builder assembles a clean PULL_REQUEST_TEMPLATE.md from the sections you turn on.

How it works

GitHub looks for a Markdown file at .github/PULL_REQUEST_TEMPLATE.md and copies its contents into the description box whenever someone opens a pull request. The “Type of Change” block uses Markdown task-list syntax, which GitHub renders as interactive checkboxes:

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Documentation update
- [ ] Refactor / chore

Headings (##) divide the template into sections, and a checklist of - [ ] items lets authors confirm they ran tests, updated docs, and removed debug logging before requesting review.

Tips and notes

Keep the template short — a wall of mandatory sections gets deleted rather than filled in. The Testing section pays for itself by letting reviewers reproduce verification steps. For multiple templates (feature, hotfix, release), use a .github/PULL_REQUEST_TEMPLATE/ directory and pass ?template=name.md on the compare URL. To actually block merges on the checklist, wire a GitHub Action status check.