We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
4.0 dev upgrade guide: fix formatting issue Looks like the call out blocks don't work within a list.
4.0 dev upgrade guide: fix tabs vs spaces
4.0 | User upgrade guide: add information about (upcoming) branch rename and impact
Update schema URL in example code
4.0 | Document the new (and old) exit codes and the `ignore_non_auto_fixable_on_exit` flag
4.0-beta | Add upgrade guides for upgrading to PHPCS 4.0
About Standards: add section about how PHPCS determines the standard to use
Fixing errors/Reporting: move Diff report info The information about the `Diff` report was included in the "Fixing errors automatically" page, but is kind of dated as the `phpcbf` script has by now existed for a fair number of years. This changes the "Fixing errors" page to focus on the `phpcbf` tool and moves the information about the "Diff" report to the "Reporting" page.
Configuration Options: improve readability and clarity
Usage, Advanced Usage: improve readability and clarity
Home: improve readability and clarity
Remove ablist language and other textual improvements
Update/add table of contents for various pages Generated table of contents using https://bitdowntoc.derlin.ch/ Includes adding additional "back to top" links.
CS/markdownlint: various whitespace fixes
CS/markdownlint: improve table style
CS/markdownlint: consistent emphasis style
CS/markdownlint: consistent list item indentation
CS/markdownlint: code blocks should always specify language When the code block contains plain text, use `text`.
CS/markdownlint: use fenced codeblocks everywhere This makes it easier to copy/paste updated output to the wiki docs.
Usage: update help output for PHPCS 3.13.0
Merge progress reporting sections When I created the new section about progress reporting on the "Reporting" page, I'd overlooked that the "Usage" page already contained a section on progress reporting. This commit now removes the section from the "Reporting" page again and merges some of the information which was contained in that section, into the information about progress reporting on the "Usage" page. Includes various tweaks and updates to the pre-existing information: * Make it explicit how progress reporting can be enabled. * Shorten the example output for progress. * Mention the name of the configuration option to enable progress reporting by default. * Refresh the example output for the verbose example.
Reporting: add section about progress reporting
Annotated-Ruleset: fix typo
Fix file line endings
Fixing Errors: update the "help" output Oops... forgot to update this when the new help screen was released. Fixed now. Includes updating the "Usage" page with the latest changes which will be included in PHPCS 3.12.0.
Requirements: fix typo
Configuration Options: update php_version example
Update new "About Standards" page Make it explicit that a category should not be called "Sniffs".
Update new "About Standards" page * Syntax highlighting PHP samples. * Make it clearer which examples are invalid. * Spelling/grammar fixes.
Add new "About Standards" page This new page contains more generic information about: * The difference between a project ruleset and a standard. * Requirements for a standard. * Naming conventions for sniffs.