Skip to content

Backport: Skip pull_request triggered runs in private repos - 4.7 Branch - #13002

Draft
desrosj wants to merge 1 commit into
WordPress:4.7from
desrosj:backport/4.7-branch-63183
Draft

Backport: Skip pull_request triggered runs in private repos - 4.7 Branch#13002
desrosj wants to merge 1 commit into
WordPress:4.7from
desrosj:backport/4.7-branch-63183

Conversation

@desrosj

@desrosj desrosj commented Aug 12, 2026

Copy link
Copy Markdown
Member

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

Merge Conflict Resolution

The 4.7 branch's .github/workflows/ directory only contains four of the twelve workflow files touched by the original commit: coding-standards.yml, javascript-tests.yml, phpunit-tests.yml, and test-build-processes.yml. git cherry-pick produced conflicts on every file (content conflicts on the four present files, plus modify/delete conflicts on the eight files that don't exist on this branch), so the cherry-pick was aborted and the change was applied by hand to only the jobs that exist here, using the original commit message.

  • coding-standards.yml: updated the if: condition on the jshint job (the phpcs job present on trunk does not exist on this branch).
  • javascript-tests.yml: updated the if: condition on the test-js job.
  • phpunit-tests.yml: updated the if: condition on the test-php job. This branch's phpunit-tests.yml has a single PHP-version job (no startsWith( github.repository, 'WordPress/' ) wrapper and no fork-only job), so only the simple form of the condition applies.
  • test-build-processes.yml: updated the if: condition on the test-core-build-process job. The test-core-build-process-macos job in this file uses a different, unrelated condition (github.repository == 'WordPress/wordpress-develop' only, no pull_request fallback) and was left untouched, per the scope rules.

The following files from the original commit do not exist on the 4.7 branch at all and were skipped entirely: end-to-end-tests.yml, javascript-type-checking.yml, performance.yml, php-compatibility.yml, phpstan-static-analysis.yml, test-and-zip-default-themes.yml, upgrade-develop-testing.yml, workflow-lint.yml. None of these (or an equivalent under a different name) exist on this branch, so there was nothing to map the change to. The uses: .../@trunk to uses: ./... conversion (originally done in upgrade-develop-testing.yml and workflow-lint.yml) does not apply here since neither file exists on this branch.

No Slack-notification jobs, and no workflows outside the scope of the original commit, were modified.

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.

This modifies the conditions for GitHub Actions workflow runs so that they do not run within private forks and mirrors for `pull_request` events when the PR is in `draft` status.

For situations where this may be desirable, a `Draft Workflow Runs` label can be added to a `draft` pull request to force workflows to run.

Props desrosj, jorbin.
See #65848.

git-svn-id: https://develop.svn.wordpress.org/trunk@63183 602fd350-edb4-49c9-b593-d223f7449a82
@desrosj desrosj self-assigned this Aug 12, 2026
@github-actions

Copy link
Copy Markdown

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant