Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docker container based github actions to test code instead of makefile which for example relies on components being available locally. Plus get added automatic code scan on any PRs
key is in action so publicly visible but no reason couldn't utilise github secrets for key
this is more a demo of what can be done
Results look like this:
https://github.com/DominicWatts/magento2-module-url-data-integrity-checker/actions
You don't have to use container approach e.g. https://github.com/DominicWatts/Menu/blob/master/.github/workflows/standards.yml
However the reason I use container based approach is it's easier to switch php version and also for phpstan in particular not to throw false positives if components from M2 required modules are used : php_intl - e.g. IntlDateFormatter not found etc.
https://github.com/DominicWatts/PHPStan
But certainly container based unit tests are difficult