[desrosj]

Backports r63183 to the 7.0 branch.

In private forks and mirrors, pull_request workflows no longer run for draft PRs unless the Draft Workflow Runs label is added. The condition is applied to each job on this branch that runs for pull_request events outside of WordPress/wordpress-develop. Workflows from the trunk commit that don't exist on this branch are skipped.

Differences from trunk:

• uses: references in upgrade-develop-testing.yml and workflow-lint.yml still point to @trunk. This branch has no local reusable workflows.

Trac ticket: https://core.trac.wordpress.org/ticket/65845

Use of AI Tools

This pull request was created by an AI agent (Claude Code). Until this PR is marked "Ready for Review", treat it as untrusted, AI-created code that requires a manual review by a human team member.

🤖 Generated with Claude Code

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

⚠️ PHPStan Static Analysis

PHPStan reported 2 errors when analyzing 96ae830 (workflow run). This comment is updated as new commits are pushed.

Errors

These are also shown as annotations on the changed files. They do not fail the check, but they should still be fixed before the pull request is committed. An error that is a false positive may instead warrant being added to a baseline.

Location	Error	Identifier	First reported
src/wp-admin/load-scripts.php:68	Function get_file not found.	function.notFound	96ae830
src/wp-admin/load-styles.php:83	Function get_file not found.	function.notFound	96ae830

Running PHPStan locally

To run the analysis on your own machine, use npm run typecheck:php, or composer phpstan outside the Docker environment.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[lancewillett]

Compared with r63183 and the 7.0 branch workflows: every pull_request job on this branch now has the same private-repo, draft, and Draft Workflow Runs label condition as trunk (18 jobs across 11 files), and nothing else changes. Workflows trunk touched that this branch lacks are correctly left out. Job uses: lines keep @trunk, which matches how this branch calls its reusable workflows. It merges cleanly into the current 7.0 tip (90618cc). CI: 126 passed, 34 skipped, 0 failed.

_{AI review · claude-opus-5-5}