-
-
Notifications
You must be signed in to change notification settings - Fork 522
GH Actions: use the xmllint-validate action runner and enhance checks #2522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dingo-d
merged 3 commits into
WordPress:develop
from
jrfnl:feature/ghactions-change-xmllint-validation
Mar 14, 2025
Merged
GH Actions: use the xmllint-validate action runner and enhance checks #2522
dingo-d
merged 3 commits into
WordPress:develop
from
jrfnl:feature/ghactions-change-xmllint-validation
Mar 14, 2025
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
The intention is for there to be a dedicated action runner available at some point for XML code style checking, so let's move this to a separate job. Also see: PHPCSStandards/PHPCSDevTools#145
Instead of doing all the installation steps for xmllint validation in the workflow, use the ✨ new dedicated `phpcsstandards/xmllint-validate` action runner instead. Ref: https://github.com/marketplace/actions/xmllint-validate
... for dev tool files.
dingo-d
approved these changes
Mar 14, 2025
GaryJones
approved these changes
Mar 14, 2025
Member
Author
|
@dingo-d Thanks, but could I please remind you to only squash-merge when the commits are not atomic ? |
Member
|
I thought I had the squash merge on for this repo 😬 Sorry, probably shouldn't be merging anything while under a temperature 🤒 |
dsntdxs0
pushed a commit
to dsntdxs0/WordPress-Coding-Standards
that referenced
this pull request
May 11, 2025
…WordPress#2522) * GH Actions: split XML code style check off from "Run code sniffs" check The intention is for there to be a dedicated action runner available at some point for XML code style checking, so let's move this to a separate job. Also see: PHPCSStandards/PHPCSDevTools#145 * GH Actions: use the xmllint-validate action runner Instead of doing all the installation steps for xmllint validation in the workflow, use the ✨ new dedicated `phpcsstandards/xmllint-validate` action runner instead. Ref: https://github.com/marketplace/actions/xmllint-validate * GH Actions: add some additional XML validation checks ... for dev tool files. --------- Co-authored-by: jrfnl <[email protected]>
lesterchan
added a commit
to lesterchan/WordPress-Coding-Standards
that referenced
this pull request
Jun 8, 2025
* upstream/develop: (428 commits) Rulesets: update schema URL GH Actions: use the xmllint-validate action runner and enhance checks (WordPress#2522) AbstractFunctionParameterSniff: fix first class callables and function imports (WordPress#2518) DontExtractStandard.xml file creation (WordPress#2456) Add documentation for WordPress.NamingConventions.ValidVariableName (WordPress#2457) Remove unused variables from a few sniffs (WordPress#2514) I18nTextDomainFixer: remove unnecessary variable initialization (WordPress#2513) GH Actions: Bump codecov/codecov-action from 4 to 5 (WordPress#2510) GH Actions: PHP 8.4 has been released CS/QA: remove redundant condition GH Actions: use explicit PHPStan major Various sniffs: simplify skipping the rest of the file GH Actions: always quote variables Release checklist: add new action item AbstractClassRestrictionsSniff: fix insufficient defensive coding (WordPress#2500) ✨ New WordPress.WP.GetMetaSingle sniff (WordPress#2465) Fix typo in AbstractFunctionRestrictionsSniff::is_targetted_token() DocBlock (WordPress#2477) Fix typos (WordPress#2472) Documentation: capitalization consistency fixes (WordPress#2469) [Documentation]: WordPress.DB.PreparedSQL (WordPress#2454) ...
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.
GH Actions: split XML code style check off from "Run code sniffs" check
The intention is for there to be a dedicated action runner available at some point for XML code style checking, so let's move this to a separate job.
Also see: PHPCSStandards/PHPCSDevTools#145
GH Actions: use the xmllint-validate action runner
Instead of doing all the installation steps for xmllint validation in the workflow, use the ✨ new dedicated
phpcsstandards/xmllint-validateaction runner instead.Ref: https://github.com/marketplace/actions/xmllint-validate
GH Actions: add some additional XML validation checks
... for dev tool files.