Some assumptions/opinions made for the development of the tool are:
Minimum PHP version 8.1, given that is the only PHP version in security support (or greater)
PHPUnit for unit testing; fairly strongly opinionated on this, but again, is a preference.
Psalm for static analysis; not strongly opinionated here, but I have more experience working with Psalm, so this is my preference
doctrine/coding-standard for CS; I feel this CS is comprehensive and fixes most code in a predictable way, and I am most familiar with phpcs (over say, php-cs-fixer).
I have used laminas/workflow-continuous-integration to run the CI workflow, as it is ludicrously easy to get up and running. Should we need to expand out of these realms in the future for static analysis/CS/linting/testing etc., we can of course
Some assumptions/opinions made for the development of the tool are:
doctrine/coding-standardfor CS; I feel this CS is comprehensive and fixes most code in a predictable way, and I am most familiar withphpcs(over say, php-cs-fixer).laminas/workflow-continuous-integrationto run the CI workflow, as it is ludicrously easy to get up and running. Should we need to expand out of these realms in the future for static analysis/CS/linting/testing etc., we can of course