chore: overhaul ignore configs
Update git, Prettier, and ESLint ignore files.
- Sort items alphabetically.
- Categorize items into OS, Vite, and Lockfiles.
- Remove the leading
/- match the style with thenode_modulesentry. - Follow the Vite's
.envfile rules - only the*.localfiles are ignored by git. - Remove items from
.eslintignorethat are not handled by ESLint, such as.DS_STORE. - Add items to
.eslintignore, such asdistwhich is generated in the library template. - Add
Thumbs.dbfor Windows users.
Please don't delete this checklist! 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
- [x] 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
pnpm testand lint the project withpnpm lintandpnpm check
Changesets
- [x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running
pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.
Edits
- [x] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.
⚠️ No Changeset found
Latest commit: 41bb2c0fc752843651e00de133da618884c2c5ee
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@benmccann I am really sorry, I badly messed up my git branching.
Should I create a new PR with the above mentioned suggestions?
Go for it @hyunbinseo