Contributing to Testo

May 19, 2026 ยท View on GitHub

Thank you for your interest. Below you'll find everything you need to know before contributing to Testo.

Pull Requests

We respect your time! For code changes beyond a typo or a small fix, we recommend opening an issue first where we can discuss the approach. It is better to have a conversation than reject a finished PR that doesn't fit the roadmap. Don't forget to search for existing issues first.

To submit a pull request follow these steps:

  1. Fork this repository;
  2. Clone forked repository;
  3. Create a new branch and give it a descriptive name, e.g. "add-awesome-feature";
  4. Make changes. Ensure tests and linter are passing by running make from a project root;
  5. Keep a Changelog: describe changes made in CHANGELOG.md under "Unreleased" section.
  6. Commit your changes and push to this branch;
  7. Submit a pull request from "you/testo/your-branch" to "ozontech/testo/main".

Please be aware that the maintainers may ask for changes. This isn't a commentary on the quality of your idea or your code. We need to enforce certain practices and patterns to keep the package easy for others to understand.

Keep pull requests focused on one topic. A PR that adds a feature, fixes an unrelated bug, and reformats documentation should be three PRs.

AI

All AI usage in any form should be disclosed. Please, state the tool you used along with the extent that the work was AI-assisted.

Issues

If you find a bug or think of a useful feature you'd like to see added to Testo, open an issue!

Please provide enough context in the issue description that other members of the community can easily understand what it is that you'd like to see.

License

By contributing you agree your work is licensed under the Apache-2.0.