Allow manually dispatching the PHPCS workflow [ignore_release] - #197
Merged
Conversation
The README/dashboard badge reads the latest default-branch run, which has been a failed Dec 2025 run from a fork PR branch named 5.x-dev. Push runs keep the badge reflecting the actual state of the dev branches.
snake14
force-pushed
the
phpcs-run-on-dev-branch-push
branch
from
August 14, 2026 02:49
d66025a to
24d2879
Compare
PHPCS is already enforced on every PR before merge, so per-push runs add nothing. A single manual dispatch on 5.x-dev is enough to refresh the stale badge.
AltamashShaikh
approved these changes
Aug 14, 2026
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.
Description
The PHPCS badge for this plugin (shown on the plugins build dashboard) has displayed "failing" since December 2025 even though PHPCS passes on all recent pull requests. The badge shows the latest workflow run whose head branch matches the default branch, and that run is a failed December 2025 run from a fork PR whose branch was named
5.x-dev. Because the workflow only triggers onpull_request, no future run can replace that badge state on its own.This adds a
workflow_dispatchtrigger so the workflow can be run manually; a single dispatch on5.x-devafter merging refreshes the badge. PHPCS otherwise stays PR-only, since it is already enforced on every PR before merge. CI-only change with no runtime effect.Issue No
NA
Steps to Replicate the Issue
Checklist