First of all, thank you for considering contributing to krotoDC! We appreciate your time and effort and are excited to have you join our community. This document serves as a guideline for contributing to our open-source library.
- Fork the repository on GitHub.
- Clone your fork to your local machine.
- Set up your development environment, ensuring that all necessary dependencies are installed.
- Create a new branch for your feature or bugfix.
We follow the Kotlin Coding Conventions for code style. Please make sure your code adheres to these conventions.
Additionally, before committing your code, ensure that the ktlintCheck
passes:
./gradlew ktlintCheck
If there are any issues, you can try to fix them automatically by running:
./gradlew ktlintFormat
When changing the generated code output, include a test for it in the same pull request (PR). Add new .proto
files under src/test/proto
, and they will be automatically generated and accessible from the tests. Ensure that all tests pass before submitting your PR:
./gradlew test
- Commit your changes to your feature or bugfix branch.
- Push your branch to your fork on GitHub.
- Create a pull request from your fork's branch to the original repository's
main
branch. - In the pull request description, provide a clear and concise description of the changes you made, and mention any issues that your PR addresses.
- Await feedback from maintainers. They may request changes or ask questions. Be prepared to iterate on your PR based on their feedback.
We expect all contributors to adhere to the standard Code of Conduct. Please treat everyone with respect and maintain a professional and inclusive environment.
Once again, thank you for your interest in contributing to krotoDC. We look forward to your contributions and to working with you!