Repository navigation
ci: add a separate per-plugin test workflow and plugin test rules - #84
Open
MyPrototypeWhat wants to merge 1 commit into
Open
MyPrototypeWhat wants to merge 1 commit into
MyPrototypeWhat wants to merge 1 commit into
Conversation
Add .github/workflows/plugin-tests.yml, which runs on pull_request for plugins/** changes, detects changed plugins/<author>/<plugin> dirs that define scripts.test, and runs npm test in each via a matrix (Node 22, read-only permissions). Document plugin test conventions in CONTRIBUTING.md and CONTRIBUTING.zh-CN.md.
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.
This PR adds a dedicated workflow for plugin tests and documents how contributors should write them.
What changes
.github/workflows/plugin-tests.yml(new)pull_requestonly, limited to changes underplugins/**.permissions: contents: read. Checkout runs withpersist-credentials: false.plugins/<author>/<plugin-id>directories the PR changes and keeps only those whosepackage.jsonhas atestscript. It then runsnpm testinside each of those directories, on Node.js 22.CONTRIBUTING.md/CONTRIBUTING.zh-CN.mdAdds a "Plugin tests" section:
npm test.package.json.test/directory is reserved for repo-wide Mini App rule checks. It must not import or run plugin tests.Why
Plugin tests stay out of repo-wide CI. The rules check (
npm run check) and roottest/stay exactly as they are, so a plugin's own test suite can't slow down or break the rules CI for unrelated PRs.Notes
package.json.Need help on this PR? Tag
@codesmith-botwith what you need.