ci: add per-PR XML structure check against doc-en#412
Conversation
9e0b2fa to
ed04e21
Compare
|
Thanks. It does find real problems: 11 of the 22 distinct annotations it produced in doc-ru are genuine The description says a lagging file is compared against the English it actually translated, so it cannot false-positive. That holds for ordinary commits, not for Measured on doc-ja master: 346 files flagged, but only 81 still diverge when compared against doc-en HEAD instead. So 265 — 77% — are false positives, and all 265 also appear in #413's failure set. As noted there, doc-base documents this On scope: doc-en's With php/doc-en#5672 (removing Two smaller things: two annotations print the same signature on both sides, because the depth prefix is compared but trimmed from the message; and the translator-credits guard expects Closing. php/docbook-cs looks like the right home for this — you already have #16, #17 and #22 there, it is wired into doc-en, and |
Adds a GitHub Actions workflow that runs on every pull request and checks that the block structure of modified XML files stays aligned with the corresponding
doc-enfile.How it works
pull_requestevents targetingmaster.xmlfiles changed in the PREN-Revisionhash it declares and fetchesdoc-enat that exact revision::errorannotations in the PR if a divergence is foundPrior art
This check is already in use in
doc-fr,doc-ru,doc-es, anddoc-it. There is also an ongoing initiative indoc-baseto provide reusable workflows that alldoc-*repos can share.