Closed neilenns closed 1 month ago
This PR adds two YAML validation steps to the existing CI process. This should guard against issues like the one introduced in #17.
Here's an example of a failed run against the file checked in with #17: https://github.com/neilenns/navdata/actions/runs/10392918979/job/28779239721
Here's an example of a successful run against the current checked in yaml: https://github.com/neilenns/navdata/actions/runs/10392937229
The job is named "Validate and generate" and can be added as a required status check in GitHub's branch protection rules to guard against merges that fail validation.
This PR adds two YAML validation steps to the existing CI process. This should guard against issues like the one introduced in #17.
Here's an example of a failed run against the file checked in with #17: https://github.com/neilenns/navdata/actions/runs/10392918979/job/28779239721
Here's an example of a successful run against the current checked in yaml: https://github.com/neilenns/navdata/actions/runs/10392937229
The job is named "Validate and generate" and can be added as a required status check in GitHub's branch protection rules to guard against merges that fail validation.