We welcome contributions to kickable-rs! Whether you want to report a bug, request a new feature, or submit a code change, your input is valuable and appreciated.
Before making any contributions, please review the guidelines below to ensure that your contributions are consistent with our project's goals and expectations.
If you encounter a bug in kickable-rs, please report it by opening a new issue in the repository's issue tracker. When reporting a bug, please provide as much information as possible, including:
- A description of the bug and the expected behavior
- Steps to reproduce the bug
- Any error messages or other relevant information
If you have a feature request for kickable-rs, please open a new issue in the repository's issue tracker. When requesting a feature, please provide a clear description of the feature and its expected benefits.
We welcome code changes from anyone in the community. To ensure that your code changes are accepted and integrated smoothly, please follow these guidelines:
-
Before starting work on a code change, please discuss the proposed changes with the project maintainers by opening a new issue or commenting on an existing issue.
-
Fork the repository and create a new branch for your changes.
-
Make sure your changes are consistent with the project's coding style and guidelines.
-
Write tests to cover any new code that you add.
-
Submit a pull request to the repository's main branch with a clear description of your changes and why they are necessary.
-
Your pull request will be reviewed by the project maintainers, who will provide feedback and request changes if necessary.
-
Once your pull request is approved, it will be merged into the main branch and included in the next release of kickable-rs.
All contributors to kickable-rs are expected to adhere to the project's Code of Conduct, which can be found in the file CODE_OF_CONDUCT.md.
Thank you for contributing to kickable-rs!