svelte/.github/PULL_REQUEST_TEMPLATE.md

### Before submitting the PR, please make sure you do the following
- [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
- [ ] Prefix your PR title with `[feat]`, `[fix]`, `[chore]`, or `[docs]`.
- [ ] This message body should clearly illustrate what problems it solves.
- [ ] Ideally, include a test that fails without this PR but passes with it.

### Tests
-  [ ] Run the tests with `npm test` and lint the project with `npm run lint`
update issue templates to new format and add more detail (#3238) 5 years ago			`### Before submitting the PR, please make sure you do the following`
Better surface RFC process (#5295) 4 years ago			`- [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs`
Update PR template to ask for PR category (#6475) 3 years ago			- [ ] Prefix your PR title with `[feat]`, `[fix]`, `[chore]`, or `[docs]`.
Better surface RFC process (#5295) 4 years ago			`- [ ] This message body should clearly illustrate what problems it solves.`
			`- [ ] Ideally, include a test that fails without this PR but passes with it.`

update issue templates to new format and add more detail (#3238) 5 years ago			`### Tests`
Better surface RFC process (#5295) 4 years ago			- [ ] Run the tests with `npm test` and lint the project with `npm run lint`