Slide 18
PR Template System
Show PR templates as quality and release-readiness checks.
Source markdown
This page is generated from the canonical slide file in the repository and the supporting references listed below.
Key points
- Template variants match PR intent (feature, bug, release, refactor, docs).
- Prompts enforce clearer change summaries and validation notes.
- PR templates create better review handoffs across teams.
Speaker notes
- Connect template quality to faster approvals and fewer review loops.
- Mention compatibility with automated checks and reviewer workflows.
Accessibility notes
- Keep layout simple: title + 3 bullets + one visual zone.
- Use minimal visuals (one icon, one screenshot, or one simple diagram only).
- Avoid dense process diagrams, nested callouts, and complex animation.
- Keep on-slide text short (roughly 25-40 words total where possible).
- Use high contrast and consistent spacing; prioritise readability over decoration.
References
`.github/PULL_REQUEST_TEMPLATE/README.md` Reference used in this slide `.github/PULL_REQUEST_TEMPLATE/pr_feature.md` Reference used in this slide `.github/PULL_REQUEST_TEMPLATE/pr_bug.md` Reference used in this slide `.github/PULL_REQUEST_TEMPLATE/pr_release.md` Reference used in this slide `docs/PR_CREATION_PROCESS.md` Reference used in this slide