Repository navigation
Conversation
YAML Integration
✅ All 1 passed. |
GitHub Actions Integration
✅ All 1 passed. |
posquit0
marked this pull request as ready for review
October 19, 2026 08:07
This file contains hidden or 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
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.
👋 Background
YAML validation only has a yamllint-specific reusable workflow. It lacks standalone check actions, formatting validation, and the combined report used by the Terraform and GitHub Actions integrations.
⚙️ Description
yaml.yamllintandyaml.yamlfmtcomposite actions. Both require caller-installed CLIs, exposeskipped/stdout/stderr/exitcode, useshell.run, and publish failure details throughgithub.step-summary. Annotations can be disabled. Formatting checks do not modify files.yaml.integration.yamlreusable with mise setup, independent versions/configs/targets/enabled flags, both checks enabled by default, andgithub.matrix-reportcollection plus a single summary/sticky PR comment. Disabled checks are omitted, and failures fail the lint job after both checks finish.yaml.yamland grant the report's PR-comment permission.yaml.yamllint.yamlinterface as a lint-only entry point backed by the new composite action..yamlfmt.yamlto preserve the repository's existing formatting without reformatting existing files.Validation:
git diff --check.🚨 To Reviewers
The complete integration passed on GitHub-hosted Ubuntu runners using temporary PR-branch references: YAML lint, format, result collection, and report. GitHub Actions lint and schema validation also passed.
Final references follow the repository's
@mainconvention. The new callable workflow and actions are not available onmainbefore this PR is merged, so the final-head YAML CI cannot resolve them yet; the successful run above validates the same implementation with only those references changed. After merge, the normalmainpush runs both checks through the published components.The existing
yaml.yamllint.yamlinputs and optionaltokensecret remain accepted. New integration callers using the default PR comment setting should grantcontents: readandpull-requests: write, as the repository CI caller does.