docs: update CONTRIBUTING.md with lint and test steps, remove duplicate PR template

This commit is contained in:
Nicolas Varrot
2026-02-13 07:10:33 +00:00
parent 141bc4e8fc
commit 41f3952548
2 changed files with 9 additions and 27 deletions

View File

@@ -1,25 +0,0 @@
## Description
<!-- What does this PR do? Why is it needed? -->
## Type of Change
- [ ] 🐛 Bug fix
- [ ] ✨ New feature
- [ ] 💅 Style / UI change
- [ ] ♻️ Refactor (no behavior change)
- [ ] 📝 Documentation
- [ ] 🧪 Tests
- [ ] 🔧 Build / CI / tooling
## Checklist
- [ ] `npm run build` passes with zero errors
- [ ] Tested in browser (dev server or production build)
- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)
- [ ] No secrets or credentials included
- [ ] Translations updated in `src/lib/i18n.ts` if UI text changed
## Screenshots
<!-- If this changes the UI, add before/after screenshots or a short GIF -->

View File

@@ -26,8 +26,10 @@ Thanks for your interest in contributing! 🦞
## Development ## Development
- **Build:** `npm run build` — must pass with 0 errors before submitting a PR
- **Dev server:** `npm run dev` — starts Vite with hot reload - **Dev server:** `npm run dev` — starts Vite with hot reload
- **Lint:** `npm run lint` — must pass with 0 errors and 0 warnings
- **Test:** `npm test` — runs Vitest unit tests (must all pass)
- **Build:** `npm run build` — must pass with 0 errors before submitting a PR
- **Preview:** `npx vite preview` — serve the production build locally - **Preview:** `npx vite preview` — serve the production build locally
### Project Structure ### Project Structure
@@ -48,7 +50,12 @@ src/
1. Create a feature branch: `git checkout -b feat/my-feature` 1. Create a feature branch: `git checkout -b feat/my-feature`
2. Make your changes 2. Make your changes
3. Ensure `npm run build` passes with no errors 3. Ensure all checks pass:
```bash
npm run lint # 0 errors, 0 warnings
npm test # all tests pass
npm run build # 0 errors
```
4. Commit using [Conventional Commits](https://www.conventionalcommits.org/): 4. Commit using [Conventional Commits](https://www.conventionalcommits.org/):
- `feat:` — new feature - `feat:` — new feature
- `fix:` — bug fix - `fix:` — bug fix