Repository navigation
Root-layout plugin repos: audits scan shipped plugin code only (DEC-083) - #66
Merged
Merged
Conversation
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.
What & why
Plugins can now live at the repo root (
plugin_dir: .) — the layout the plugin hub needs, because A0clones the whole repo as the plugin. But the audits then scanned the repo's own
tests/and devfiles and flagged them as plugin problems (false alarms on code that never ships).
Fix: the audits now skip repo scaffolding (
tests/,.github/, build output, …) — the same set theCI zip already excludes — so they check only what actually ships. No-op for repos using the old
nested layout.
SPEC alignment
Checklist
pytestgreen locallyCHANGELOG.mdentry —v2.2.0 — unreleased(MINOR)sample-plugin-e2eCI gate green