Skip to content

Conversation

@jrfnl
Copy link
Member

@jrfnl jrfnl commented Mar 14, 2025

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.

jrfnl added 3 commits March 3, 2025 04:13
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
@dingo-d dingo-d merged commit 38168bc into WordPress:develop Mar 14, 2025
40 checks passed
@jrfnl
Copy link
Member Author

jrfnl commented Mar 14, 2025

@dingo-d Thanks, but could I please remind you to only squash-merge when the commits are not atomic ?

@jrfnl jrfnl deleted the feature/ghactions-change-xmllint-validation branch March 14, 2025 13:52
@dingo-d
Copy link
Member

dingo-d commented Mar 14, 2025

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants