When introducing changes to the library, ensuring that we don't introduce regressions on commit is an action that can be automated using existing checker utilities. One particular tool I use in a multitude of projects is pre-commit and its CI counterpart (https://pre-commit.ci/).
The types of checks we can perform are numerous:
Checking the validity of the source files (check-manifest)
Static typing (mypy)
Black code formatting
Documentation references
etc.
I will open a PR with a handful of checks based on existing code practices, but if we want to adopt more, the list of potential checks is quite extensive (https://pre-commit.com/hooks.html).
When introducing changes to the library, ensuring that we don't introduce regressions on commit is an action that can be automated using existing checker utilities. One particular tool I use in a multitude of projects is
pre-commitand its CI counterpart (https://pre-commit.ci/).The types of checks we can perform are numerous:
check-manifest)I will open a PR with a handful of checks based on existing code practices, but if we want to adopt more, the list of potential checks is quite extensive (https://pre-commit.com/hooks.html).