Updated the PR template to emphasize reading the CONTRIBUTING.md file.
41 lines
1.1 KiB
Markdown
41 lines
1.1 KiB
Markdown
<!--
|
|
Please follow this template. The PR template applies whether you opened the PR via the web UI, `gh pr create`, or any other tool.
|
|
|
|
You MUST read CONTRIBUTING.md before sending a PR.
|
|
-->
|
|
|
|
### Linked issue
|
|
|
|
Closes #
|
|
|
|
### Type of change
|
|
|
|
- [ ] Bug fix
|
|
- [ ] New feature
|
|
- [ ] Enhancement
|
|
- [ ] Refactor
|
|
- [ ] Docs
|
|
|
|
### What does this PR do
|
|
|
|
<!-- A short description of the change in your own words. What was wrong, what you changed, why it works. If you can't explain this briefly, the PR is probably too big. -->
|
|
|
|
### How did you verify it
|
|
|
|
<!--
|
|
This is the section I read most carefully. I need to see that *you* tested this, not that the diff looks plausible.
|
|
|
|
- For UI changes: a screenshot or short video on every affected platform (mobile, web, desktop). UI claims without visual proof are not enough.
|
|
- For behavior changes: the actual steps you ran, and what you observed.
|
|
- For bug fixes: how you reproduced the bug before, and confirmed it's fixed after.
|
|
-->
|
|
|
|
### Checklist
|
|
|
|
- [ ] One focused change
|
|
- [ ] `npm run typecheck` passes
|
|
- [ ] `npm run lint` passes
|
|
- [ ] `npm run format` passes
|
|
- [ ] QA evidence
|
|
- [ ] Tests added or updated where it made sense
|