Thanks for considering a contribution. Keep it simple and helpful.
- Search existing issues/PRs before filing a new one.
- Small, focused PRs are easier to review and merge.
- Be respectful. See our CODE_OF_CONDUCT.md.
- Fork the repo and create a branch:
git checkout -b feat/<short-name>. - Code and add tests. Keep changes narrow; explain tradeoffs.
- Run tests
- Commit with a descriptive message.
- Open a PR describing what changed and why. Add screenshots/benchmarks if relevant.
- Use the issue template.
- Repro or it didn't happen: include versions, OS, logs, minimal code sample.
- We prioritize clarity and rollback safety.
- If your PR grows > ~300 lines, split it.
- Add a brief entry to CHANGELOG.md under "Unreleased".