Automation and contribution workflow conventions?

[MadeInPierre]

I'd like to automate the following steps in this repo:

• Formatting checks: this project uses pre-commit to run basic tests such as linting (with flake8 and black), both locally before each commit and before releases.
• Tests: Start with a simple dry-run which calls Finary's official API with a fake email and password, just to make sure all dependencies are installed. Discussed in How to check if the PyPI package is complete? #22
• Documentation: Write proper docstrings and automatically deploy a documentation website to readthedocs using sphinx. See docs: write full documentation #32
• Release management: based on the commit messages and PR titles (following the conventional commits naming standard), a new version is calculated on each push to the main branch and the new PyPI package is published.
• PR Management: pre-commit runs when a PR is created/modified and automatically applies the formatting changes in case the contributor forgot to. In addition, another check makes sure PR titles follow the conventional commits standard.

Let me know if that sounds good or if there's something missing/to be improved (tailored to this project's size) 😄

[MadeInPierre]

All done! This repo should have everything needed to start a healthy contribution cycle. Let me know if there's anything to improve 🙂