Contributing
Getting set up
Branch naming
| Prefix | Purpose | Example |
|---|---|---|
feat/ | New features | feat/color-picker-plugin |
fix/ | Bug fixes | fix/icon-render-crash |
chore/ | Maintenance | chore/update-dependencies |
docs/ | Documentation | docs/add-api-guide |
Commit messages
Use conventional commits:
Pull request workflow
- Create a feature branch:
git checkout -b feat/my-feature - Make your changes
- Run checks:
bun run build && bun run test && bun run lint - Add a changeset:
bun changeset(if your change affects users) - Push and open a PR against
master - CI runs automatically — wait for green checks
- Pre-commit hooks auto-format your code via Biome
CI pipeline
Every push and PR runs:
- Biome linting
- TypeScript type-checking
- Vitest tests (27+ tests)
- Plugin build
- Storybook build
Code style
- Biome handles formatting and linting automatically
- Pre-commit hooks run on every commit via Husky
- TypeScript strict mode is enabled everywhere
- Use
@repo/*imports for cross-package references