ci(ilxnsm-vibe-coding-dev-setup): add HOL skill-publish validate workflow#1
Open
internet-dot wants to merge 2 commits intoILXNSM:mainfrom
Open
ci(ilxnsm-vibe-coding-dev-setup): add HOL skill-publish validate workflow#1internet-dot wants to merge 2 commits intoILXNSM:mainfrom
internet-dot wants to merge 2 commits intoILXNSM:mainfrom
Conversation
ILXNSM
force-pushed
the
main
branch
6 times, most recently
from
4ee381a to
8592c75
Compare
internet-dot
changed the title
ILXNSM
force-pushed
the
main
branch
3 times, most recently
from
443646c to
d121ded
Compare
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
2 participants
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.
This repo already has enough skill metadata to validate in CI.
A couple of repo-specific details I checked first:
This adds one workflow for
.and leaves the runtime code alone.It only runs the schema and trust checks for the skill metadata in validate mode.
If you would rather place the workflow under a different filename or point it at a different skill directory, I can adjust the branch.