Build/Travis: validate rulesets against XSD and check code style consistency #2187
Conversation
This file contains 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
Notes: * Runs only once per build as the results are independent of the PHP version. * Indent is set at four spaces as per commit 232f7da . * I've elected to add this check to the smallest (fastest) build, so the build time will be spread more evenly. * Not linting the PHPCS native ruleset as it's being run anyway, so is automatically checked.
This was referenced Oct 16, 2018
|
Thanks. You're a 💎 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commit summary
Build: lint the XML rulesets and check for consistent code style
Notes:
Add the XSD schema tags to the XML rulesets
Clean the XML ruleset files/consistent code style