| file_type | documentation | |
|---|---|---|
| description | PR template router | |
| name | Which PR template should I use? | |
| about | Branch-to-template routing for consistent PR governance | |
| title | PR: {short summary} | |
| labels |
|
Use this file as a router. Copy the matching template from the GitHub
.github/PULL_REQUEST_TEMPLATE/ folder based on your branch prefix, then
replace this body with that template.
| Branch prefix | Template |
|---|---|
feat/ |
pr_feature.md |
fix/ |
pr_bug.md |
hotfix/ |
pr_hotfix.md |
refactor/ |
pr_refactor.md |
chore/ |
pr_chore.md |
docs/ |
pr_docs.md |
test/ |
pr_chore.md |
perf/ |
pr_feature.md |
ci/ |
pr_ci.md |
build/ |
pr_ci.md |
deps/ |
pr_dep_update.md |
security/ |
pr_bug.md |
design/ |
pr_feature.md |
a11y/ |
pr_feature.md |
release/ |
pr_release.md |
research/ |
pr_feature.md |
Correct template selection improves label automation, changelog quality, and
review consistency. The routing rules are defined in
.github/PULL_REQUEST_TEMPLATE/config.yml.
Closes #
Risk Level:
Potential Impact:
Mitigation Steps:
- Step 1:
- Step 2:
- Step 3:
- All AC met and demonstrated
- Tests added/updated (unit/E2E as appropriate)
- Docs/readme/changelog updated (if user-facing)
- Risk assessment completed above
- Testing instructions provided above
- Contribution Guidelines
- Branching Strategy
- Automation & Workflows
- PR template routes
- Pull Request Labelling
- Saved Replies
- Labeler Config
- Labels
- Issue Types