CI: check .xml structure drift against doc-en#152
Open
lacatoire wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a structure check: on every PR it verifies that the block skeleton of the changed .xml files stays a mirror of doc-en (same
<note>, same lists). Inline prose (<para>,<title>...) is not compared, as it legitimately differs between languages.Each file is compared to doc-en at the revision it declares (
EN-Revision), so lagging files do not raise false positives. It only needs a checkout of doc-en, no doc-base.The same check already runs on
php/doc-fr,php/doc-esandphp/doc-ru:https://github.com/php/doc-fr/blob/master/.github/workflows/check-xml.yml
The script skips translator credits (
authorgroup xml:id="translators..."). To make it warn only, change the finalexittoexit 0.A shared translation toolchain is being built in
php/doc-baseso every language can get these checks from a single place. Until that lands, this workflow is a useful stopgap: it is fully self-contained (doc-en checkout only) and provides the check today.