-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the WordPress Plugin Check Action #806
Conversation
…; add caching to this so it runs faster; use this action in our plugin check action so we're testing on the final build version
working-directory: ${{ github.event.repository.name }} | ||
|
||
- name: Run plugin check | ||
uses: wordpress/plugin-check-action@v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any options to know specifically what checks we're running or is it all-or-nothing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default it will run all tests but you can exclude certain checks or certain categories of checks. If you see a few lines below, we're using the exclude-checks
setting to remove a couple checks but we run everything else.
You can see all the checks and categories here: https://github.com/wordpress/plugin-check-action/?tab=readme-ov-file#supported-checks
Looks good to me, though we might suggest an upstream enhancement to have some sort of simple report post-run to see what's passed/failed as it wasn't immediately clear where that info was in action run. |
Description of the Change
WordPress has an official Plugin Check plugin that runs a handful of different checks. They've brought the same functionality into a GitHub Action and this PR adds that as a workflow.
Also made some minor updates to our Build Release Zip Action (which we use here to run tests on the final build) and fix the few issues the Plugin Check found.
Note there are quite a few checks the Plugin Check does, some of which we already do separately (like PHPCS). For now I've left all checks in place other than the Plugin Readme and Plugin Updater checks (both fail here) but we may want to trim the list down if we think some of these are overkill, though they run fast enough I think it's fine.
How to test the Change
Verify the Plugin Check Action is passing on this PR
Changelog Entry
Credits
Props @dkotter
Checklist: