The current CI workflow for the purl-spec repo/project is based on an early implementation from the initial creation of the current repo structure in July 2025 (converted from narrative documentation into schemas, test file and new documentation artifacts).
The subject of this issue is to:
The objectives are to:
- Ensure consistent validation of changes to
purl-spec artifacts - these are primarily documentation files, schema files and test case files
- Improve the purl-spec contributor experience
The primary use cases for the CI workflows are to check/validate:
- Add a new PURL type
- Add or update a JSON Schema file(s)
- Add or update a JSON data file(s) - including the type definition or test files
- Add or update markdown documentation file(s) - see also
It probably makes sense to run the full validation check for any PR rather than try to detect which checks to run because the validation should be very fast.
The current CI workflow for the
purl-specrepo/project is based on an early implementation from the initial creation of the current repo structure in July 2025 (converted from narrative documentation into schemas, test file and new documentation artifacts).The subject of this issue is to:
/etc/or/etc/scriptsfolder as internal documentationThe objectives are to:
purl-specartifacts - these are primarily documentation files, schema files and test case filesThe primary use cases for the CI workflows are to check/validate:
It probably makes sense to run the full validation check for any PR rather than try to detect which checks to run because the validation should be very fast.