Repository navigation
chore: add a Plugin Check workflow - #100
Merged
Merged
Conversation
Run the official Plugin Check Action on the release files for every pull request and on trunk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ WordPress Plugin Check Report
📊 ReportAll checks passed! No errors or warnings found. 🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check |
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.
Change
The new
.github/workflows/plugin-check.ymlruns the official Plugin Check Action on every pull request and on trunk. This is the same tool the wordpress.org review team uses.bin/build-zip.shand checks the unzippedlifecycle-profiler/folder. Plugin Check sees exactly what wordpress.org receives, andvendor/,tests/and the other development folders are not checked.wordpress/plugin-check-actionis pinned to the commit hash of v1.1.9, released on 2026-08-11.contents: read, and forpull-requests: writeso the Action can post its results as a PR comment. On PRs from forks, GitHub keeps the token read-only anyway.actions/checkout@v7, the same as the workflows Dependabot updated.Result
On this PR, Plugin Check reported "Checks complete. No errors found." The Action posted its comment: "All checks passed! No errors or warnings found."
pull-requests: write, and then the comment posted.Not in this PR
spell-check.ymlstill usesactions/checkout@v5. It was added after Dependabot's update. Dependabot will move it to v7 in its next weekly run.🤖 Generated with Claude Code