Making changes to a fork and submitting from there usually ends up being easier for both you and us.
We use poetry to manage our dependencies.
To install them you would need to run the following command:
poetry installRun all tests beforehand and make a note of the coverage percentage
We use pytest and flake8 for quality control. To run all tests:
pytestWe use wemake-python-styleguide to lint our code. To run it use:
flake8 .We mypy to check our code. To run it use:
mypy dotenv_linterWrite your code. Make your changes.
Any changes you have made that require documentation, make sure to document them! Add your docstrings (if applicable), and let future users and contributors know what your changes do and how they should be used
Make sure that everything you've done hasn't broken anything that we've done! If you have added new functionality or features, make sure you have added a test for that functionality or feature
Submit a PR for your changes. Make sure to include in the commit/PR message what issue you are addressing (if fixing a bug or feature request).
You can contribute by spreading a word about this library. It would also be a huge contribution to write a short article on how you are using this project. What are your best-practices?