svelte/.github/PULL_REQUEST_TEMPLATE.md

## Svelte 5 rewrite

Please note that [the Svelte codebase is currently being rewritten for Svelte 5](https://svelte.dev/blog/runes). Changes should target Svelte 5, which lives on the default branch (`main`).

If your PR concerns Svelte 4 (including updates to [svelte.dev.docs](https://svelte.dev/docs)), please ensure the base branch is `svelte-4` and not `main`.

### 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 and linting

- [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint`
chore: update PR template (#9397) * chore: update PR template * Update .github/PULL_REQUEST_TEMPLATE.md --------- Co-authored-by: Rich Harris <richard.a.harris@gmail.com> 2023-11-13 00:49:59 +01:00			`## Svelte 5 rewrite`

			Please note that [the Svelte codebase is currently being rewritten for Svelte 5](https://svelte.dev/blog/runes). Changes should target Svelte 5, which lives on the default branch (`main`).

			If your PR concerns Svelte 4 (including updates to [svelte.dev.docs](https://svelte.dev/docs)), please ensure the base branch is `svelte-4` and not `main`.
chore: update PR template with note about rewrite (#9231) 2023-09-20 19:23:27 +02:00
update issue templates to new format and add more detail (#3238) 2019-07-19 20:27:57 +02:00			`### Before submitting the PR, please make sure you do the following`
feat(site-2): Update links, move blog out of SK folder to content (#8289) * Update links * Move blog to site/content * Update site/content/docs/02-component-format.md * Fix docs links * Add global prettierrc * Auto format * Fix git merge artifact * Fix errors * Update html to svelte(remaining ones) * Add 2 blog posts * Modify prettierrc * Minor design fix * Switch package lock to spaces, prettier ignore * Regenerate package lock * prettier format * Update deps * Hack the build into working * add missing blog post --------- Co-authored-by: Rich Harris <richard.a.harris@gmail.com> Co-authored-by: Rich Harris <git@rich-harris.dev> 2023-04-02 17:24:33 +02:00
Better surface RFC process (#5295) 2020-08-21 17:22:50 +02:00			`- [ ] 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`
chore: update PR template (#8255) 2023-02-05 15:20:51 +01:00			- [ ] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`.
Better surface RFC process (#5295) 2020-08-21 17:22:50 +02:00			`- [ ] This message body should clearly illustrate what problems it solves.`
			`- [ ] Ideally, include a test that fails without this PR but passes with it.`

docs: use pnpm and new commands to check the code base (#8667) Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com> 2023-05-30 21:19:51 +02:00			`### Tests and linting`
feat(site-2): Update links, move blog out of SK folder to content (#8289) * Update links * Move blog to site/content * Update site/content/docs/02-component-format.md * Fix docs links * Add global prettierrc * Auto format * Fix git merge artifact * Fix errors * Update html to svelte(remaining ones) * Add 2 blog posts * Modify prettierrc * Minor design fix * Switch package lock to spaces, prettier ignore * Regenerate package lock * prettier format * Update deps * Hack the build into working * add missing blog post --------- Co-authored-by: Rich Harris <richard.a.harris@gmail.com> Co-authored-by: Rich Harris <git@rich-harris.dev> 2023-04-02 17:24:33 +02:00
Merge remote-tracking branch 'origin/version-4' into sites 2023-05-30 21:42:01 +02:00			- [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint`