actions-marketplace-validations/XML Model Validator

Validate xml-model XML with Relax NG and Schematron for TEI, DocBook, JATS, and other complex XML workflows

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Apr 8, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: actions-marketplace-validations/adunning_xml-model-validator@bcaf6c6e290181710b4efef3e6642ef1b1a5796a # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
filesNewline-delimited list of files to validate explicitlyno
files_fromPath to a newline-delimited file listno
directoryDirectory containing matching files to validate recursivelyno
file_extensionsComma- or whitespace-separated file extensions to discover when scanning directories or changed files; a leading period is optionalno
changed_files_onlyValidate only changed files with matching extensions from the current push or pull requestnofalse
changed_sourceSource for changed_files_only file discovery (auto, api, git)noauto
jobsNumber of parallel workers to use (0 = auto)no0
configOptional path to a TOML validator config file containing schema aliases and xml-model rulesno
xml_model_rule_modeOptional inline xml-model rule mode for this run (fallback or replace)no
xml_model_rule_directoryOptional directory scope for the inline xml-model rule; when no selection input is set, this also becomes the default directory to validateno
xml_model_rule_extensionOptional file extension scope for the inline xml-model rule; a leading period is optionalno
xml_model_declarationsOptional newline-delimited xml-model declarations for one inline rule; repeat lines to validate against multiple schemasno
fail_fastStop after the first file that fails validationnofalse
check_schematron_schemaRun SchXslt assembled-schema checks before validating documents that use Schematronnofalse
schematron_severity_thresholdSkip Schematron assertions with a severity lower than this threshold; one of INFO, WARNING, ERROR, FATALnoINFO
json_report_pathOptional path, relative to the repository root or absolute, where the Action should save a JSON validation reportno
namedescription
skippedWhether validation was skipped because no changed files matched the configured extensions
files_checkedNumber of files checked during validation
failed_filesNumber of files that failed validation
warning_countNumber of warning-level issues produced during validation
json_report_pathAbsolute path to the saved JSON report when json_report_path input is set