Thanks for your interest in contributing to inators projects!
- Fork the repository
- Create a feature branch from
main - Make your changes
- Submit a pull request
- Use a clear, descriptive title following conventional commits (e.g.,
feat: add user authentication) - Fill out the PR template completely
- Ensure CI passes before requesting review
- Keep changes focused — one feature or fix per PR
We use conventional commits enforced on PR titles (squash merge). Valid prefixes:
feat, fix, docs, chore, refactor, test, perf, ci, build, revert
- All PRs require review before merging
- Address review feedback or explain why you disagree
- Be respectful and constructive in reviews
- Use the issue templates provided
- Search existing issues before creating a new one
- Include reproduction steps for bugs
Open a discussion in the Q&A category on the org's Discussions tab.