ci: add codex-plugin-scanner workflow#8
Closed
internet-dot wants to merge 1 commit intosane-apps:mainfrom
Closed
Conversation
MrSaneApps
force-pushed
the
ci/codex-plugin-scanner
branch
from
2b6dd17 to
e816b88
Compare
MrSaneApps
force-pushed
the
ci/codex-plugin-scanner
branch
from
e816b88 to
f28eb10
Compare
Collaborator
|
Thanks for the careful PR. I am closing this because SaneApps keeps app-repo GitHub workflows manual-only unless there is a documented SaneProcess exception, and this adds an automatic third-party workflow. If we add plugin scanning, I will route it through the shared SaneProcess verification path or a workflow_dispatch-only shared workflow instead. |
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 adds one validate-only workflow for the plugin metadata already in this repo.
The change is limited to one workflow file. Permissions stay read-only, and runtime code is untouched.
It only checks the metadata files already in the repo.
No secrets or publish step are involved.
No runtime code or release flow changes are included here, and the workflow can be removed cleanly if it does not fit your setup.
If you would rather fold it into existing CI or place it under a different filename, I can adjust the branch.