Backport: Skip pull_request triggered runs in private repos - 5.9 Branch

[desrosj]

This backports 15c4b04 (r63183) to the 5.9 branch.

Merge Conflict Resolution

The 5.9 branch has a much smaller and older set of workflow files than trunk, so the cherry-pick conflicted. Notes on exactly what was applied, dropped, and hand-edited:

Files from the original commit that do not exist on 5.9 (dropped entirely)

These came through as modify/delete conflicts (the commit modified them, 5.9 does not have them). They were git rm'd so that the backport does not introduce brand new workflow files onto this branch:

• .github/workflows/javascript-type-checking.yml
• .github/workflows/performance.yml
• .github/workflows/phpstan-static-analysis.yml
• .github/workflows/test-and-zip-default-themes.yml
• .github/workflows/upgrade-develop-testing.yml
• .github/workflows/workflow-lint.yml

Because upgrade-develop-testing.yml and workflow-lint.yml do not exist on 5.9, the part of the original commit that switched those two workflows from uses: WordPress/wordpress-develop/.github/workflows/<x>.yml@trunk to uses: ./.github/workflows/<x>.yml was not carried over. No reusable-build-package.yml, reusable-upgrade-testing.yml, or reusable-workflow-lint.yml exists on this branch either, so no local uses: reference would resolve.

Files that applied cleanly

• .github/workflows/end-to-end-tests.yml – e2e-tests job.
• .github/workflows/test-build-processes.yml – test-core-build-process job.

Files that conflicted and were resolved by hand

In each of these, the 5.9 version of the job differs from trunk (extra with: blocks, secrets: inherit instead of named secrets, different job names/structure), so the surrounding lines did not match. The 5.9 content was kept as-is and only the if: expression was replaced with the new condition:

• .github/workflows/coding-standards.yml – phpcs job (conflicted because 5.9 has a with: php-version: '7.4' block immediately after the if:) and jshint job.
• .github/workflows/javascript-tests.yml – test-js job (conflicted because 5.9 has a with: disable-apparmor: true block after the if:).
• .github/workflows/php-compatibility.yml – php-compatibility job (conflicted because 5.9 has a with: php-version: '7.4' block after the if:).
• .github/workflows/phpunit-tests.yml – test-php job. This file conflicted heavily: 5.9 has a single test-php job with secrets: inherit, while trunk has prepare-gutenberg, test-with-mysql, test-with-mariadb, test-innovation-releases, html-api-test-groups, and limited-matrix-for-forks. Only the existing test-php job was updated. None of the trunk-only jobs were added, so the startsWith( github.repository, 'WordPress/' ) && (...) variant and the fork-only limited-matrix-for-forks variant of the condition do not appear on this branch — 5.9's test-php uses the plain github.repository == 'WordPress/wordpress-develop' || github.event_name == 'pull_request' form and therefore received the plain replacement condition.

Intentionally left untouched

• All slack-notifications and failed-workflow jobs — they are gated on github.event_name != 'pull_request' and are unaffected.
• .github/workflows/test-build-processes.yml – the test-core-build-process-macos job is gated only on github.repository == 'WordPress/wordpress-develop', which is not part of the condition family this commit changes.
• .github/workflows/welcome-new-contributors.yml — not touched by the original commit.

Net result

6 files changed, all under .github/workflows/. Seven job if: gates updated in total. All changed files were verified to parse as valid YAML and contain no conflict markers.

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.

[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.