Thank you for your interest in contributing! This guide applies to all repositories in this organization.
- Check if the issue already exists
- Use the Bug Report template
- Include steps to reproduce, expected vs. actual behavior
- Use the Feature Request template
- Describe the use case, not just the solution
- Fork the repository (or create a feature branch if you have write access)
- Use branch naming:
feature/,fix/,docs/ - Follow the code style (Python: ruff, JS: prettier)
- Write clear commit messages:
type: description- Types:
feat,fix,docs,refactor,test,chore
- Types:
- Open a Pull Request with the PR template filled out
- Wait for review (usually within 7 days)
- Python: Follow ruff defaults, type hints encouraged
- JavaScript/TypeScript: Follow prettier defaults
- Markdown: One sentence per line for better diffs
- PRs require at least 1 approving review
- All conversations must be resolved before merge
- Keep PRs focused — one feature or fix per PR
- Update documentation if your change affects usage
We follow the Contributor Covenant v2.1. Be respectful, inclusive, and constructive.
Open a Discussion (Q&A category) or create an issue with the Question template.