Why
When someone opens a PR there is no template guiding them on what to include. This leads to inconsistent PR descriptions and makes review harder.
What to add
Create .github/PULL_REQUEST_TEMPLATE.md with sections like:
- What — brief description of the change
- Why — motivation / linked issue
- How — implementation approach
- Checklist:
Also consider adding issue templates (.github/ISSUE_TEMPLATE/) for bug reports and feature requests. The default GitHub ones are fine as a starting point.
Why
When someone opens a PR there is no template guiding them on what to include. This leads to inconsistent PR descriptions and makes review harder.
What to add
Create
.github/PULL_REQUEST_TEMPLATE.mdwith sections like:forge fmtpassesAlso consider adding issue templates (
.github/ISSUE_TEMPLATE/) for bug reports and feature requests. The default GitHub ones are fine as a starting point.