From bf0e337b33d9bdfedce3532aee9f54a8b7a6d4bf Mon Sep 17 00:00:00 2001 From: jrfnl Date: Tue, 14 Jun 2022 04:18:23 +0200 Subject: [PATCH] XSD: minor touch up --- PHPCSDebug/Docs/Debug/TokenListStandard.xml | 6 +++++- README.md | 6 +++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/PHPCSDebug/Docs/Debug/TokenListStandard.xml b/PHPCSDebug/Docs/Debug/TokenListStandard.xml index 1f11fad..72b6b37 100644 --- a/PHPCSDebug/Docs/Debug/TokenListStandard.xml +++ b/PHPCSDebug/Docs/Debug/TokenListStandard.xml @@ -1,4 +1,8 @@ - + + ``` @@ -194,7 +194,7 @@ If your IDE or editor supports automatic validation of XML files, you will be no #### Validating your docs against the XSD -You can validate your PHPCS XML documentation against the XSD file using [xmllint](https://gnome.pages.gitlab.gnome.org/libxml2/xmllint.html). This validation can be run locally if you have xmllint installed, as well as in CI (continuous integration). +You can validate your PHPCS XML documentation against the XSD file using [xmllint](http://xmlsoft.org/xmllint.html). This validation can be run locally if you have xmllint installed, as well as in CI (continuous integration). An example of a workflow job for GitHub Actions CI looks like this: @@ -217,7 +217,7 @@ jobs: run: xmllint --noout --schema vendor/phpcsstandards/phpcsdevtools/DocsXsd/phpcsdocs.xsd ./YourRuleset/Docs/**/*Standard.xml ``` -You'd need to replace the `YourRuleset` with the name of your ruleset of course. +:point_right: You'll need to replace the `YourRuleset` within the command with the name of your ruleset (of course). Contributing -------