Thank you for your interest in contributing to pyspry
! We appreciate your help to make this
project better.
Please note that by participating in this project, you are expected to adhere to the Community Code of Conduct. Treat each other with respect to create a positive and inclusive environment. 🥳
There are several ways you can contribute to pyspry
!
If you encounter any bugs while using pyspry
, please
open a new issue using the
bug.md template.
If you have any ideas or suggestions to improve pyspry
, please
open a new issue using the
feature.md template.
Merge requests for bug fixes, enhancements, and new features are very welcome. To contribute code to
pyspry
, follow these steps:
- Create a fork of the repository
- Implement your changes in the fork, ensuring they adhere to the project's linters and formatters
- Open a new merge request from your fork to the
pyspry
repository, and provide a detailed description of your changes.
Note: each contribution must pass all CI/CD and linting tests in order to be considered.
Once your pull request is submitted, it will be reviewed by the project maintainers. Please be patient, as it may take some time to receive feedback.
Refer to the README for details on how to set up a development environment for
pyspry
.
By contributing to pyspry
, you agree that your contributions will be licensed under the project's
OSI approved license.