A new set of coding requirements will be introduced, which will be automated by .github runs, and would consist of
mypy, with agreed-upon enforcement rules;
pylint, with agreed-upon enforcement rules;
black, with an agreed-upon line length and other code format tweaks available;
yamllint, with an agreed-upon file format;
pytest, which would be implemented only when automated module and component unit testing is included in CLOVER.
All GitHub workflows can be overridden using Admin permissions, but implementing the workflows would ensure that a red flag was placed on all pull requests that would, after merging with the master branch, result in the code failing any of the enforced checks. An automated email would also be sent out to administrators of the repository, informing them that a failed run of the automated tests was carried out.
A new set of coding requirements will be introduced, which will be automated by .github runs, and would consist of
mypy, with agreed-upon enforcement rules;pylint, with agreed-upon enforcement rules;black, with an agreed-upon line length and other code format tweaks available;yamllint, with an agreed-upon file format;pytest, which would be implemented only when automated module and component unit testing is included in CLOVER. All GitHub workflows can be overridden using Admin permissions, but implementing the workflows would ensure that a red flag was placed on all pull requests that would, after merging with the master branch, result in the code failing any of the enforced checks. An automated email would also be sent out to administrators of the repository, informing them that a failed run of the automated tests was carried out.