cancel-workflow-action VS PHP CS Fixer

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.

PHP-CS-Fixer automatically fixes PHP coding standard issues, maintaining a clean codebase and adhering to coding standards. It can be integrated into the development workflow to ensure all code complies with defined standards.

friendsofphp/php-cs-fixer

While you're at it, also include code-style checkers like phpcs, phpmd and/or php-cs-fixer

I run two tools for this - php-cs-fixer on PHP 5.6 and the built-in syntax checker(php -l).

You can use this library to help automate this: https://github.com/FriendsOfPHP/PHP-CS-Fixer 😊

To be bit a elaborate and for a proper updated installtion process, here is what I did: I used the [latest versio]n(https://github.com/FriendsOfPHP/PHP-CS-Fixer/releases/tag/v3.10.0) of php cs fixer then entered the command that followed to install php-cs-fixer.

PHP CS Fixer is able to generate a GitLab formatted report which GitLab can use to show you any new violations in the code or even if code style violations have been tackled.

Laravel Pint is an opinionated PHP code style fixer for minimalists. Pint is built on top of PHP-CS-Fixer and makes it simple to ensure that your code style stays clean and consistent. Pint is a new addition to the Laravel framework.