Repository navigation
Conversation
desrosj
force-pushed
the
fix-actions-6.1/remove-rn-workflows
branch
from
September 11, 2026 00:00
3948eac to
18c7471
Compare
desrosj
removed this pull request from stack #107
September 13, 2026 01:31
desrosj
added this pull request to stack #323
September 13, 2026 01:31
desrosj
force-pushed
the
fix-actions-6.1/remove-rn-workflows
branch
2 times, most recently
from
September 14, 2026 01:40
fffa163 to
6a74aae
Compare
desrosj
removed this pull request from stack #323
September 21, 2026 21:42
desrosj
added this pull request to stack #425
September 21, 2026 21:48
desrosj
removed this pull request from stack #425
September 21, 2026 23:47
desrosj
added this pull request to stack #443
September 21, 2026 23:57
desrosj
removed this pull request from stack #443
September 22, 2026 00:49
desrosj
added this pull request to stack #451
September 22, 2026 01:02
desrosj
removed this pull request from stack #451
September 22, 2026 15:53
desrosj
force-pushed
the
fix-actions-6.1/remove-rn-workflows
branch
from
September 22, 2026 15:55
6a74aae to
37d8b2a
Compare
desrosj
added this pull request to stack #461
September 22, 2026 15:57
Removes `rnmobile-ios-runner.yml` and `rnmobile-android-runner.yml`. The iOS workflow runs its test job on `macos-11`, a runner image GitHub retired in June 2023, so the job can no longer execute successfully regardless of any other change made to it. The Android workflow still runs on the currently supported `macos-latest` runner, but React Native mobile support is no longer maintained or shipped as part of Gutenberg, so there is no ongoing need to keep testing it on this branch.
This workflow deploys Storybook to GitHub Pages and only triggers on pushes to `trunk`. Frozen release branches like this one never push to `trunk`, so the workflow can never run from this branch's copy and only adds noise to the Actions tab.
This workflow uploads a published Gutenberg plugin release to the WordPress.org plugin repository and only triggers on the `release` event. Releases are cut from `trunk`, not from frozen `wp/X.Y` maintenance branches, so this workflow's copy on this branch never has a reason to run.
Removes `stale-issue-add-needs-testing.yml`, `stale-issue-flaky-test.yml`, `stale-issue-mark-stale.yml`, and `stale-issue-needs-info.yml`. These workflows only trigger on a `schedule`, and GitHub Actions always uses the copy of a scheduled workflow that exists on the repository's default branch, never the copy on this branch, no matter what changes are made here. Keeping stale copies around only adds confusion for anyone browsing this branch's Actions configuration.
This workflow reports flaky end-to-end test failures to GitHub issues and only triggers on the `workflow_run` event, firing when the `End-to-End Tests` or `End-to-End Tests Playwright` workflows complete. Like `schedule`-triggered workflows, `workflow_run` events always execute using the copy of the file that exists on the repository's default branch, never the copy on the branch being tested, so this file's copy on this branch can never actually run.
…ch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
desrosj
removed this pull request from stack #461
September 22, 2026 20:36
desrosj
force-pushed
the
fix-actions-6.1/remove-rn-workflows
branch
from
September 22, 2026 20:38
37d8b2a to
edd3581
Compare
desrosj
added this pull request to stack #479
September 22, 2026 20:43
desrosj
removed this pull request from stack #479
September 23, 2026 01:32
desrosj
added this pull request to stack #488
September 23, 2026 01:47
desrosj
removed this pull request from stack #488
September 23, 2026 21:32
desrosj
added this pull request to stack #506
September 23, 2026 21:36
desrosj
removed this pull request from stack #506
September 24, 2026 18:16
desrosj
added this pull request to stack #520
September 24, 2026 18:17
desrosj
removed this pull request from stack #520
September 28, 2026 14:34
desrosj
added this pull request to stack #541
September 28, 2026 14:36
desrosj
removed this pull request from stack #541
September 28, 2026 19:09
desrosj
added this pull request to stack #568
September 28, 2026 19:10
desrosj
removed this pull request from stack #568
September 29, 2026 00:26
desrosj
added this pull request to stack #574
September 29, 2026 00:28
desrosj
removed this pull request from stack #574
October 5, 2026 20:48
desrosj
added this pull request to stack #611
October 5, 2026 20:48
desrosj
removed this pull request from stack #611
October 6, 2026 14:20
desrosj
added this pull request to stack #621
October 6, 2026 14:21
desrosj
removed this pull request from stack #621
October 7, 2026 18:02
desrosj
added this pull request to stack #667
October 7, 2026 18:05
desrosj
marked this pull request as ready for review
October 8, 2026 03:24
|
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#84240. |
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 GitHub Actions workflow files from
wp/6.1that can never run correctly from this branch, that can never run at all as this branch's copy because of GitHub's own event-triggering rules, or that are only maintained for the current WordPress release.rnmobile-ios-runner.ymlmacos-11, a runner image GitHub retired in June 2023; the job can no longer executernmobile-android-runner.ymlstorybook-pages.ymltrunk; this branch never pushes totrunkupload-release-to-plugin-repo.ymlreleaseevent; releases are cut fromtrunk, not from frozenwp/X.Ybranchesstale-issue-add-needs-testing.yml,stale-issue-flaky-test.yml,stale-issue-mark-stale.yml,stale-issue-needs-info.ymlschedule; GitHub Actions always uses the default branch's copy of a scheduled workflow, never this branch'sflaky-tests.ymlworkflow_run; likeschedule, GitHub Actions always uses the default branch's copy, never this branch'sperformance.ymlpublish-npm-packages.ymlis kept: it is manually dispatched only, and both of its checkout steps hard-coderef: trunk, so it can never publish from this branch.Why?
Keeping dead workflow files around on a frozen maintenance branch adds noise to the Actions tab and confusion for anyone trying to understand what actually runs against
wp/6.1. Apart from the performance tests, which are only maintained for the current WordPress release, none of the removed files can produce a passing (or in most cases, any) run from this branch's copy, so removing them has no effect on real CI coverage.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.