Thank you for considering a contribution. This is the organization-wide guide;
individual repositories may add project-specific instructions in their own
CONTRIBUTING.md, which takes precedence.
- Bugs: open an issue on the affected repository with a minimal reproduction.
- Features: open an issue describing the problem you want solved before writing code — it saves everyone time if we agree on the direction first.
- Security: never via public issues; see SECURITY.md.
- Fork the repository and create a branch from
main. - Keep the change focused — one concern per pull request.
- Match the existing code style; run the project's formatter and linters
(most repositories expose them via
composer,make, ornpmscripts). - Add or update tests for behavior you change; the test suite must pass.
- Update documentation (
README.md,docs/) when behavior or usage changes. - Write commit subjects in the imperative mood, 72 characters or fewer, with the body explaining why.
- Default license is MIT; contributions are accepted under the repository's license.
- Be kind and constructive — all participation is covered by our code of conduct.
opensource@simtabi.com, or the issue tracker of the repository concerned.