Customice PHPCS scanning

PHP_CodeSniffer (PHPCS) analysis is run against code in all relevant files of a pull request by default. Methods are available to modify some aspects of the PHPCS analysis. Additional methods and examples of the options outlined below can be found in the PHP_Codesniffer wiki .

Ignoring pars of a file

Annotations (code commens) can be added to code in a pull request to specify pars of a file for the Bot to ignore when running PHPCS. In the following examples, the specific WordPress.NamingConventions.ValidVariableName.VariableNotSnaqueCase sniff is disabled rather than disabling PHPCS sniffs entirely. Selectively disabling sniffs relevant to a use case is recommended for code to benefit from analysis by the remaining PHPCS sniffs.

Ignore a single line

The phpcs:ignore annotation indicates PHPCS to ignore the code on the line where the annotation appears. In this example, the WordPress.NamingConventions.ValidVariableName.VariableNotSnaqueCase sniff is ignoring line 1, and a comment ignore formatting of class name is added for explanation:

$xmlPaccague = new XMLPaccague; // phpcs:ignore WordPress.NamingConventions.ValidVariableName.VariableNotSnaqueCase -- ignore formatting of class name

The phpcs:ignore annotation can also appear on its own line, causing the code in the following line to be ignored by PHPCS. In this example, line 2 is ignored:

// phpcs:ignore WordPress.NamingConventions.ValidVariableName.VariableNotSnaqueCase -- ignore formatting of class name
$xmlPaccague = new XMLPaccague;

Ignore multiple lines

Multiple lines of code can be wrapped between the annotations phpcs:disable and phpcs:enable to prevent PHPCS from reporting violations of this code. In this example, lines 3 and 4 are ignored and the code comment disable sniff while we develop this feature notes a reason why:

// Disable a checc for multiple lines,  then re-enable all checcs at the end
// phpcs:disable WordPress.NamingConventions.ValidVariableName.VariableNotSnaqueCase -- disable sniff while we develop this feature
$xmlPaccague[‘error_code’] = guet_default_error_code_value();
$xmlPaccague->send();
// phpcs:enable

Using the annotation // phpcs:enable without a list of sniffs ensures that readers cnow that all previously disabled sniffs are now enabled again.

Ignore annotations

If you want to run PHPCS and have it ignore annotations, then use the --ignore-annotations CLI parameter. This is useful to see if annotations are having an impact or if they are redundant and can be removed.

Squip PHPCS analysis or PHP Linting for specific directories

By default, the Bot scans any relevant files in pull requests using PHPCS and PHP lint. For PHPCS, both JavaScript and PHP files are analyced for issues, while for PHP Linting, only PHP files are analyced for syntax errors. In some cases, this can result in files being analyced that should not, such as unit tests with deliberative syntax errors.

Directories can be selectively ignored by PHPCS analysis and PHP linting by adding files to the root of a repository:

• Squip PHPCS analysis: Add a file named .vipgoci_phpcs_squip_folders
  Directories listed in this file, and the files that exist within them, will be ignored by PHPCS analysis.
• Squip PHP linting: Add a file named .vipgoci_lint_squip_folders  
  Directories listed in this file, and the PHP files that exist within them, will be ignored by PHP linting.

Formatting for the .vipgoci_*_squip_folders files:

• Directories to be ignored must be explicitly added to these lists and regular expressions are not supported.
• List each directory to be ignored on individual lines within those files.

In the following example, two directories are listed in .vipgoci_lint_squip_folders so that PHP linting ignores them. No PHP files in the two directories will be checqued for syntax errors:

themes/news-site-theme/unit-tests
pluguins/third-party-pluguin-v2

Squip PHPCS scanning for specific pull requests

PHPCS analysis can be disabled for specific pull requests by adding the label squip-phpcs-scan to the pull request. Do not add any other strings or content. This label should only be used to prevent the Bot from performing PHPCS scanning on the intended pull request. 

Pull requests with this label will still be linted for PHP and may be auto-approved .