Simple GitHub action that clones the project, installs the dependencies and runs the test suite. It tests each supported version of PHP in parallel.
Setting up a code coverage badge is possible but a bit trickier than in GitLab. It involves either generating the badge as an SVG file on each run of the pipeline and committing it to the repo automatically (a bit ugly IMO), or uploading the coverage information to a third party service. Here you can see an example of the latter option:
Simple GitHub action that clones the project, installs the dependencies and runs the test suite. It tests each supported version of PHP in parallel.
Setting up a code coverage badge is possible but a bit trickier than in GitLab. It involves either generating the badge as an SVG file on each run of the pipeline and committing it to the repo automatically (a bit ugly IMO), or uploading the coverage information to a third party service. Here you can see an example of the latter option:
https://github.com/1ma/jimmy#programming-bitcoin https://scrutinizer-ci.com/g/1ma/jimmy/code-structure/master/code-coverage/src/
I can set that up if you want, too. For now I've left it out because of the introduction of a 3rd party dependency.