Thanks for contributing.
- Create a feature branch from
main - Implement focused, reviewable changes
- Run local checks
- Open a PR and request review
Use the repository's standard verification command (typically one of):
bun verify
bun run verifyIf the repository includes Rust code, also run:
cargo fmt --all
cargo test- Prefer Bun tooling over npm/pnpm
- Prefer Biome for formatting/linting where configured
- Keep TypeScript strict and avoid
anyunless justified - Add/update tests for behavior changes
- Update docs when behavior or public API changes
- Keep PR scope small and explicit
- Link related issue(s)
- Document any breaking change
- Resolve all review comments before merge
For vulnerabilities, do not use public issues. Follow SECURITY.md.
See CODE_OF_CONDUCT.md.