Repository navigation
Conversation
desrosj
force-pushed
the
fix-actions-5.9/remove-rn-workflows
branch
from
September 14, 2026 01:13
fc71f1c to
6f02a6b
Compare
desrosj
removed this pull request from stack #173
September 21, 2026 16:56
desrosj
added this pull request to stack #395
September 21, 2026 16:56
desrosj
removed this pull request from stack #395
September 21, 2026 16:57
desrosj
added this pull request to stack #396
September 21, 2026 16:57
desrosj
removed this pull request from stack #396
September 22, 2026 16:02
desrosj
force-pushed
the
fix-actions-5.9/remove-rn-workflows
branch
from
September 22, 2026 16:02
6f02a6b to
7e4445c
Compare
desrosj
added this pull request to stack #463
September 22, 2026 16:04
React Native mobile support is no longer maintained or shipped as part of Gutenberg. `rnmobile-android-runner.yml` still ran live (no disabling condition) on `macos-latest`; `rnmobile-ios-runner.yml` was already hardcoded `if: false` and targeted `macos-11`, a runner image GitHub has since retired. Neither provides any signal worth keeping CI resources on for a frozen, security-maintenance-only branch.
`storybook-pages.yml` triggers only on `push` to `trunk` and its single job explicitly checks out `ref: trunk` before building and deploying Storybook to GitHub Pages. It never builds or deploys anything from `wp/5.9`, and the GitHub Pages target it publishes to is trunk's own deployment, not something this branch could safely publish over. There is nothing for this branch's copy of the file to do.
`upload-release-to-plugin-repo.yml` triggers only on the `release` event. GitHub Actions only ever executes a `release`-triggered workflow using the copy of the file that exists on the repository's default branch, regardless of which branch a release is tagged from. `wp/5.9`'s own copy of this file can never run — trunk's copy is what always executes, publishing whatever release trunk itself cuts. Keeping a dead copy on this branch serves no purpose.
stale-issue-add-needs-testing.yml, stale-issue-mark-stale.yml, and stale-issue-needs-info.yml all trigger only on schedule. GitHub Actions only ever runs a schedule-triggered workflow using the copy of the file on the repository's default branch. wp/5.9's own copies never execute, so removing them has no effect on the actual issue-gardening automation, which continues to run from trunk.
flaky-tests.yml's only trigger is workflow_run, listening for the End-to-End Tests workflow to complete. GitHub Actions only ever runs a workflow_run-triggered workflow using the copy of the file that exists on the repository's default branch, regardless of which branch the completed workflow ran on. wp/5.9's own copy of this file can never execute, so removing it has no effect on flaky-test reporting, which continues to run from trunk's copy. The custom .github/report-flaky-tests action this workflow called is left in place, now orphaned, as optional cleanup out of scope for this fix.
desrosj
removed this pull request from stack #463
September 22, 2026 21:19
desrosj
force-pushed
the
fix-actions-5.9/remove-rn-workflows
branch
from
September 22, 2026 21:35
7e4445c to
1e8dc29
Compare
desrosj
added this pull request to stack #483
September 22, 2026 21:37
desrosj
removed this pull request from stack #483
September 23, 2026 01:33
desrosj
added this pull request to stack #490
September 23, 2026 01:52
desrosj
removed this pull request from stack #490
September 23, 2026 21:23
desrosj
added this pull request to stack #498
September 23, 2026 21:27
desrosj
removed this pull request from stack #498
September 24, 2026 18:22
desrosj
added this pull request to stack #530
September 24, 2026 18:23
desrosj
removed this pull request from stack #530
September 28, 2026 19:13
desrosj
added this pull request to stack #570
September 28, 2026 19:14
desrosj
removed this pull request from stack #570
October 5, 2026 20:49
desrosj
added this pull request to stack #616
October 5, 2026 20:49
desrosj
removed this pull request from stack #616
October 6, 2026 18:27
desrosj
added this pull request to stack #636
October 6, 2026 18:28
desrosj
removed this pull request from stack #636
October 7, 2026 00:58
desrosj
added this pull request to stack #643
October 7, 2026 00:59
desrosj
removed this pull request from stack #643
October 7, 2026 18:02
desrosj
added this pull request to stack #668
October 7, 2026 18:06
This was referenced Oct 7, 2026
…ys use the workflow file from trunk, so this branch's copy never runs.
desrosj
removed this pull request from stack #668
October 8, 2026 19:35
desrosj
force-pushed
the
fix-actions-5.9/remove-rn-workflows
branch
from
October 8, 2026 19:35
8bf0a68 to
8d83147
Compare
desrosj
added this pull request to stack #695
October 8, 2026 19:35
desrosj
marked this pull request as ready for review
October 9, 2026 16:29
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Owner
Author
|
Moved to WordPress#84395. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Removes CI workflows on
wp/5.9that are either obsolete (React Native mobile testing), only maintained for the current WordPress release (performance testing), or that can never actually execute using this branch's own copy of the file.rnmobile-android-runner.ymlrnmobile-ios-runner.ymlif: falseand targeted the retiredmacos-11runnerperformance.ymlpull-request-automation.ymlpull_request_targetruns always use trunk's copy of the file, and itspush-triggered tasks return immediately outsidetrunk, so this branch's copy never does anythingstorybook-pages.ymlpush: branches: [trunk]only, and explicitly checks outref: trunk— this branch's copy never runs against its own contentupload-release-to-plugin-repo.ymlreleaseevent only; GitHub Actions always executesrelease-triggered workflows using the default branch's copy of the file, regardless of which branch the release is tagged fromstale-issue-add-needs-testing.yml,stale-issue-mark-stale.yml,stale-issue-needs-info.ymlscheduleonly; GitHub Actions always executesschedule-triggered workflows using the default branch's copy of the fileflaky-tests.ymlworkflow_runonly; GitHub Actions always executesworkflow_run-triggered workflows using the default branch's copy of the fileThe last three of the original rows share a mechanism, not just a similar shape:
schedule,release, andworkflow_runare all documented as always resolving to the workflow file on the repository's default branch (trunk), never the branch whose event actually fired.wp/5.9's own copies of these files are therefore inert — trunk's copies are what always runs.flaky-tests.yml's custom.github/report-flaky-testscomposite action is left in place, now orphaned. Removing it is optional cleanup out of scope for this fix.Why?
Removing dead or unmaintained workflow files reduces confusion about what actually runs on this branch and removes CI resource usage/noise (in the RN case) that provides no real signal.
Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.