Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 949 Bytes

File metadata and controls

39 lines (26 loc) · 949 Bytes

Contributing

Thanks for considering a contribution! Here's how to get started.

Quick start

  1. Fork the repo
  2. Create a feature branch: git checkout -b feat/my-feature
  3. Make your changes with tests
  4. Commit with conventional commits: feat: add X, fix: handle Y
  5. Push and open a PR

Code style

  • Run the formatter before committing
  • Add tests for new code
  • Keep PRs focused — one concern per PR

What gets accepted

✅ Bug fixes with reproduction steps ✅ Features with clear use case + tests ✅ Documentation improvements ✅ Performance improvements with benchmarks

What gets rejected

❌ "Refactor for the sake of refactor" ❌ Untested code ❌ Breaking changes without discussion ❌ Style-only changes (formatter handles those)

Need help?

Open a Discussion before starting work on something ambitious.

Code of Conduct

Be kind. Be specific. Help newcomers. Disagreement is fine; disrespect isn't.