OpenRailAssociation / OpenRailAssociation/landscape
Add publiccode.yml validation to CI
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The repository has no automated validation of the publiccode.yml files in data/. Adding a check would catch structural errors in PRs before merge.
The publiccode-parser-action GitHub Action or the publiccode-parser-go CLI (also available as Docker image) can validate files against the spec.
Suggested approach: add a CI workflow that runs the parser against all .yml files in data/ on every PR.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the existing CI workflow configuration and the YAML files under data/. Compare the publiccode-parser-action and publiccode-parser-go options, then run the chosen parser against every .yml file on pull requests. Done means malformed publiccode.yml files cause CI to fail before merge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100