PCOV VS cancel-workflow-action

Though additional modifications are recommended in the official link of PCOV, we commented on those entries in php.ini, as we witnessed issues when using php-code-coverage with PCOV.

https://github.com/krakjoe/pcov but only via workflow_dispatch, it takes too long to run regularly

XDebug is a debugger that can do coverage too. PHPdbg is another alternative to Xdebug. Pcov is built for PHPUnit code coverage, not something else.

Workflows that interact with the Github API heavily will fail as they're not available in act e.g. actions like https://github.com/styfle/cancel-workflow-action. Dealing with secrets is also a bit cumbersome. You can throw the following on actions that are not compatible with act in order to skip them:

if: ${{ !env.ACT }}

That said, despite it's limitations, I've been using both act and tmate in combination for a couple of years. Gets the job done.

For Github Actions, can highly recommend https://github.com/styfle/cancel-workflow-action which we use to cancel exists runs on same branch when never commits (push or force-push) arrives.