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

[desrosj]

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

Merge Conflict Resolution

git cherry-pick produced conflicts on every touched file (4 content conflicts plus 8 modify/delete conflicts), so the cherry-pick was aborted and the change was applied by hand with the original commit message instead.

The 4.9 branch only has 4 workflow files under .github/workflows/ (coding-standards.yml, javascript-tests.yml, phpunit-tests.yml, test-build-processes.yml). Each contains exactly one job whose if: gate matches the github.repository == 'WordPress/wordpress-develop' || github.event_name == 'pull_request' pattern from the original commit, and each was updated to the canonical replacement condition:

    if: |
      github.repository == 'WordPress/wordpress-develop' || (
        github.event_name == 'pull_request' && (
          ! github.event.repository.private ||
          ! github.event.pull_request.draft ||
          contains( github.event.pull_request.labels.*.name, 'Draft Workflow Runs' )
        )
      )

• .github/workflows/coding-standards.yml — jshint job.
• .github/workflows/javascript-tests.yml — test-js job.
• .github/workflows/phpunit-tests.yml — test-php job. (This branch has only a single PHP-matrix job here, unlike trunk's multiple PHP/MySQL jobs gated with the startsWith( github.repository, 'WordPress/' ) variant, so only the simple form was needed.)
• .github/workflows/test-build-processes.yml — test-core-build-process job. (The test-core-build-process-macos job on this branch is gated only on github.repository == 'WordPress/wordpress-develop', with no pull_request clause, so it was left untouched — it is not an equivalent of any job the original commit touched.)

The following files from the original commit do not exist on the 4.9 branch, so their hunks were dropped entirely (nothing to do, nothing created):

• .github/workflows/end-to-end-tests.yml
• .github/workflows/javascript-type-checking.yml
• .github/workflows/performance.yml
• .github/workflows/php-compatibility.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

No uses: WordPress/wordpress-develop/.github/workflows/<x>.yml@trunk → uses: ./.github/workflows/<x>.yml conversions were carried over: upgrade-develop-testing.yml and workflow-lint.yml do not exist on this branch.

Slack-notification and failed-workflow jobs were left untouched, as they are gated on github.event_name != 'pull_request' and are unaffected by this change.

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.