WordPress/WordPress-Coding-Standards
1
0
Fork 0
mirror of https://github.com/WordPress/WordPress-Coding-Standards.git synced 2025-08-30 03:11:24 +08:00
Code Issues Projects Packages Wiki Activity Actions 1

Docs: miscellaneous changes

Browse source 
Change `WPCS` to `WordPressCS` in miscellaneous files.
This commit is contained in:
jrfnl 2023-08-17 18:13:41 +02:00
parent 4a33d46882
commit 71dc238e63
No known key found for this signature in database
GPG key ID: 88BCD0973A23BCC6
3 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.gitattributes vendored
View file

@ -1,7 +1,7 @@
#
# Exclude these files from release archives.
# This will also make them unavailable when using Composer with `--prefer-dist`.
# If you develop for WPCS using Composer, use `--prefer-source`.
# If you develop for WordPressCS using Composer, use `--prefer-source`.
# https://blog.madewithlove.be/post/gitattributes/
#
/.gitattributes export-ignore

2
.phpcs.xml.dist
View file

@ -51,7 +51,7 @@
<!-- Linting is done in a separate CI job, no need to duplicate it. -->
<exclude name="Generic.PHP.Syntax"/>
<!-- WPCS still has a PHP 5.4 minimum. -->
<!-- WordPressCS still has a PHP 5.4 minimum. -->
<exclude name="Modernize.FunctionCalls.Dirname"/>
</rule>

6
Tests/RulesetCheck/class-ruleset-test.inc
View file

@ -1,14 +1,14 @@
<?php
/**
* Simple file which should not have any issues when testing against the WPCS rulesets.
* Simple file which should not have any issues when testing against the WordPressCS rulesets.
*
* Most - if not all - sniffs should be triggered by this file.
*
* Used to do a simple CI test on the rulesets.
*
* Currently covered - based on the rulesets as of July 24 2018:
* - Every WPCS native sniff is triggered.
* - Every WPCS + PHPCS sniff within the Core ruleset is triggered.
* - Every WordPressCS native sniff is triggered.
* - Every WordPressCS + PHPCS sniff within the Core ruleset is triggered.
*
* @package WPCS\WordPressCodingStandards
*/