Update WordPress Coding Standards #65
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This release only contains a fix for a fatal error when using `PHPCS 3.x` and a specific configuration variable. Because of this, `0.13.0` should never run to avoid ever running into this issue.
…hpcodesniffer # Conflicts: # composer.lock
| Some of the commits in this diff are pretty old and I think most are already merged onto master. Would you mind rebasing down to just 3ccdd89 ? |
| Thanks @larkinscott! |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The WordPress Coding Standards PHP_CodeSniffer rules have been updated to version
0.14.0.This updates the Composer dependency to use the new version.