Feature/add Phpcs Workflow#22
Merged
Merged
Conversation
phpcs.yml already covers WordPress coding standards with proper text domain configuration, making wpcs.yml duplicate work.
Rename phpcs.yml back to wpcs.yml for clarity — the workflow enforces WordPress Coding Standards, not generic PHPCS. Update CHANGELOG.md and readme.txt to say "Changed/Replaced" instead of "Added", naming the replaced 10up/wpcs-action and the specific sniffs now enforced. Co-Authored-By: Jasper Frumau <jasper@imagewize.com>
Replace plugin-check-action@v1 with manual wp-env setup to fix silent wp-env start failures and incorrect artifact upload path.
Add tee to capture wp plugin check output and upload it via actions/upload-artifact@v4 so results are available from the workflow summary after each run.
Show all available Plugin Check checks in the log before running so it is clear what was evaluated on each run.
wp plugin check does not support a --list-checks flag; remove the step that was causing the workflow to fail with exit code 1.
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
1 participant
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 release (v1.4.1) introduces automated PHP code quality enforcement via GitHub Actions, adding a PHPCS workflow and refining the existing plugin-check CI pipeline. Two new workflow files —
wpcs.ymlfor WordPress Coding Standards linting and an updatedplugin-check.yml— establish a baseline for static analysis on every push. The plugin-check workflow was rewritten with explicitwp-envsetup steps to improve reliability and reproducibility in the CI environment. Changelog and readme documentation were updated to reflect these additions accurately.CI/CD Infrastructure:
wpcs.ymlGitHub Actions workflow to run PHP_CodeSniffer against WordPress Coding Standards, providing automated style and quality gates on the codebase.plugin-check.ymlwith explicitwp-envinitialization steps, replacing implicit environment assumptions with deterministic setup to reduce flaky runs.wpcs.ymlworkflow that was introduced during the initial scaffolding, consolidating linting into a single, canonical workflow file.Release and Documentation:
warder-cookie-consent.phpto reflect the CI infrastructure additions as a minor maintenance release.CHANGELOG.mdandreadme.txtwith corrected entries for this release, fixing inaccuracies introduced in earlier draft commits.Files Changed:
.github/workflows/plugin-check.yml(Modified).github/workflows/wpcs.yml(Modified)CHANGELOG.md(Modified)readme.txt(Modified)warder-cookie-consent.php(Modified)