Add publiccode.yml validation to CI

Open Beginner friendly
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, yaml
Domain
ci-cd

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.

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.

Dominant language
HTML
Stars
5
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenRailAssociation/landscape

All issues in OpenRailAssociation/landscape

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.