Add CI/CD workflow to validate YAML files #40
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dave Thaler <[email protected]>
dthaler
requested review from
clarkegj,
tychonievich and
albertemmerich
as code owners
Signed-off-by: Dave Thaler <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The intent is that this should run on a pull request and be required to pass before the pull request can be merged.
Unlike the workflow in the GEDCOM and GEDCOM.io repositories, this workflow is configured to ignore trailing spaces since the generated YAML files have lots of trailing spaces (e.g., blank lines between paragraphs in the spec are converted to lines indented with four spaces) so the workflow would fail if not disabled.
Addressed part of #37