Hootsuite - PHP Pre-commit Hooks

Pre-commit scripts appropiate for any PHP project. These hooks are made as custom plugins under the pre-commit git hook framework.

Setup

Just add to your .pre-commit-config.yaml file with the following

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-lint
- id: php-unit
- id: php-csfiles: \.(php)$args: [--standard=PSR1 -p]
- id: php-cbffiles: \.(php)$args: [--standard=PSR1 -p]

Supported Hooks

php-lint

<<<<<<< HEAD
- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-lint

A bash script that runs php -l against stage files that are php. Assumes php is a global executable command. Will exit when it hits the first syntax error.

php-lint-all

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-lint-all

A systems hook that just runs php -l against stage files that have the .php extension. Add the args: [-s first] in your .pre-commit-config.yaml to enable it to exit on the first error found.

php-unit

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-unit

A bash script that will run the appropriate phpunit executable. It will assume

• Find the executable to run at either vendor/bin/phpunit, phpunit or php phpunit.phar (in that exact order).
• There is already a phpunit.xml in the root of the repo

Note in its current state, it will run the whole PHPUnit test as along as .php file was committed.

php-cs

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-csfiles: \.(php)$args: [--standard=PSR1 -p]

Similar pattern as the php-unit hook. A bash script that will run the appropriate PHP Code Sniffer executable.

It will assume that there is a valid PHP Code Sniffer executable at these locations, vendor/bin/phpcs, phpcs or php phpcs.phar (in that exact order).

The args property in your hook declaration can be used for pass any valid PHP Code Sniffer arguments. In the example above, it will run PHP Code Sniffer against only the staged php files with the PSR-1 and progress enabled.

If you have multiple standards or a comma in your args property, escape the comma character like so

php-cbf

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-csfiles: \.(php)$args: [--standard=PSR1 -p]

Similar pattern as the php-cs hook. A bash script that will run the appropriate PHP Code Sniffer executable and will try to fix errors if it can using phpcbf.

It will assume that there is a valid PHP Code Beautifier and Fixer executable at these locations, vendor/bin/phpcbf, phpcbf or php phpcbf.phar (in that exact order).

The args property in your hook declaration can be used for pass any valid PHP Code Sniffer arguments. In the example above, it will run PHP Code Sniffer against only the staged php files with the PSR-1 and progress enabled.

If you have multiple standards or a comma in your args property, escape the comma character like so

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-csfiles: \.(php)$args: ["--standard=PSR1/,path/to/ruleset.xml", "-p"]

To install PHP Codesniffer (phpcs & phpcbf), follow the recommended steps here.

php-cs-fixer

- repo: git@github.com:hootsuite/pre-commit-php.gitsha: 1.1.0hooks:
- id: php-cs-fixerfiles: \.(php)$args: [--level=PSR2]

Similar pattern as the php-cs hook. A bash script that will run the appropriate PHP Coding Standards Fixer executable and to fix errors according to the configuration. It accepts all of the args from the php-cs-fixer command, in particular the --level, --config, and --config-file options.

The tool will fail a build when it has made changes to the staged files. This allows a developer to do a git diff and examine the changes that it has made. Remember that you may omit this if needed with a SKIP=php-cs-fixer git commit.

php-pint

- repo: git@github.com:hootsuite/pre-commit-php.gitrev: 1.3.0hooks:
- id: php-pint

This uses Laravel Pint (which uses PHP-Cs-Fixer under the hood) to lint and automatically fix the files (if desired). It allows for the following arguments:

• [-n|--no-verify] to disable the Pint analysis
• [-y|--yes-fix] to try automatically fixing failed files

This tool respects the default pint.json config in the project directory, however, the files are passed as command line arguments to pint, and it appears that this by-passes the exclude and notPath options in pint.json.

Blade files are excluded as they are not yet supported.

Can use touch .skip_pint to skip the pint hook for the next commit (file is deleted after commit).