Repository navigation
Conversation
desrosj
added this pull request to stack #187
September 11, 2026 03:41
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 11, 2026 14:48
db407ae to
e0ae937
Compare
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 11, 2026 16:11
e0ae937 to
08444da
Compare
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 11, 2026 17:02
08444da to
c1ad7e7
Compare
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 14, 2026 01:52
c1ad7e7 to
d424424
Compare
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 14, 2026 17:56
5bedcac to
cdab45b
Compare
desrosj
marked this pull request as ready for review
September 14, 2026 17:58
Ports upstream trunk PR WordPress#82744 (head commit 3fe3bd4 as of this writing; the PR is still open/unmerged), "Workflows: Refine and complete the push and pull_request branch filters": - Narrows/widens `push:` branch filters on unit-test/end2end-test/static-checks/ build-plugin-zip/create-block/workflow-lint (where present) to the precise upstream set (trunk, release/X.Y, wp/X.Y, wp/latest, wp/next), fixing workflows that previously never ran on a direct push to this branch. Per the current version of that upstream PR, `pull_request:` triggers are deliberately left unfiltered everywhere (a PR should get the same checks regardless of which branch it targets) — the one exception upstream carves out is `workflow-lint.yml`, where a previous trunk-only `pull_request` filter is removed entirely rather than widened. This supersedes this project's earlier port of an older revision of WordPress#82744, which had added an explicit `pull_request` branch allowlist (plus a project-local temporary `fix-actions-[0-9]+.[0-9]/**` pattern) to several files. That's been reverted here to match the upstream author's updated approach — since `pull_request` now stays unfiltered, the temporary project-local pattern is no longer needed at all.
…h-triggered tasks (`add-milestone`, `first-time-contributor-account-link`) both bail out immediately outside of `trunk`, so running them here on every push does nothing.
desrosj
force-pushed
the
fix-actions-6.8/fix-workflow-branch-filters
branch
from
September 14, 2026 18:50
cdab45b to
ec767bb
Compare
Owner
Author
|
Migrated to real upstream: WordPress#82892. Closing this fork PR. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
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.
What?
Widens
push:branch filters across this branch's GitHub Actions workflows so they trigger correctly on a direct push to this branch.Why?
Ports upstream trunk's open PR #82744 (head commit
3fe3bd4aceb8331161e99d9bfc6a7463c048fcacas of this writing — the PR is still open/unmerged), "Workflows: Refine and complete the push and pull_request branch filters". Per the current version of that PR,pull_request:triggers are deliberately left unfiltered everywhere (so a PR gets the same checks regardless of target branch) exceptworkflow-lint.yml, where a previous trunk-only filter is removed entirely.build-plugin-zip.ymlpush:branch filtertrunk,release/X.Y,wp/X.Y,wp/latest, andwp/next, replacing the oldrelease/**/wp/**globs with the precise pattern from upstream WordPress#82744.create-block.ymlpush:branch filtertrunk/wp/latest; now also triggers onrelease/X.Y,wp/X.Y, andwp/next, matching upstream WordPress#82744.end2end-test.ymlpush:branch filtertrunk,release/X.Y,wp/X.Y,wp/latest, andwp/next, replacing the oldrelease/**/wp/**globs with the precise pattern from upstream WordPress#82744.static-checks.ymlpush:branch filtertrunk,release/X.Y,wp/X.Y,wp/latest, andwp/next, replacing the oldrelease/**/wp/**globs with the precise pattern from upstream WordPress#82744.unit-test.ymlpush:branch filtertrunk,release/X.Y,wp/X.Y,wp/latest, andwp/next, replacing the oldrelease/**/wp/**globs with the precise pattern from upstream WordPress#82744.pull-request-automation.ymlpushtriggerpayload.ref !== 'refs/heads/trunk'and return immediately on this branch, so nothing happens on push here.pull_request_targetis untouched and still does real work (fixed-issue assignment, first-time-contributor labeling) on PRs targeting this branch.Use of AI Tools
This PR was authored with the help of Claude Code.