Repair wp/6.6 branch Actions: widen push/pull_request branch filters

[desrosj]

Part of #82784.

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 3fe3bd4aceb8331161e99d9bfc6a7463c048fcac as 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) except workflow-lint.yml, where a previous trunk-only filter is removed entirely.

This supersedes an earlier revision of this same PR, which (following an older version of #82744) had added an explicit pull_request branch allowlist plus a project-local temporary pattern — no longer needed now that pull_request stays unfiltered.

Workflow	Change	Why
build-plugin-zip.yml	Widened the push: branch filter	Previously only triggered on trunk; now also triggers on release/X.Y, wp/X.Y, wp/latest, and wp/next, matching upstream #82744.
create-block.yml	Widened the push: branch filter	Previously only triggered on trunk/wp/latest; now also triggers on release/X.Y, wp/X.Y, and wp/next, matching upstream #82744.
end2end-test.yml	Widened the push: branch filter	Now matches trunk, release/X.Y, wp/X.Y, wp/latest, and wp/next, replacing the old release/**/wp/** globs with the precise pattern from upstream #82744.
static-checks.yml	Widened the push: branch filter	Now matches trunk, release/X.Y, wp/X.Y, wp/latest, and wp/next, replacing the old release/**/wp/** globs with the precise pattern from upstream #82744.
unit-test.yml	Widened the push: branch filter	Now matches trunk, release/X.Y, wp/X.Y, wp/latest, and wp/next, replacing the old release/**/wp/** globs with the precise pattern from upstream #82744.
pull-request-automation.yml	Removed the push trigger	Its push-triggered tasks check payload.ref !== 'refs/heads/trunk' and return immediately on this branch, so nothing happens on push here. pull_request_target is 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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: cf4a757a-8866-49c7-bd5a-746c1053e85a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.