Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔍 Local copy of a shared reusable workflow drifts from wave-foundation source
The header comment of
.github/workflows/_checks.yml:3-6states this workflow is the shared cross-project gate whose "one source of truth" lives in wave-av/wave-foundation (checks.yml@master), and the skill-validate job comment (.github/workflows/_checks.yml:48-50) says it mirrorswave-foundation/scripts/validate-skills.pyand "keep the two in sync". Bumping the Python version only in this repo's local copy introduces exactly the drift the comment warns about; the same bump should be made upstream (or this copy replaced by auses:reference).Was this helpful? React with 👍 or 👎 to provide feedback.