Repository navigation
Conversation
`rnmobile-ios-runner.yml` and `rnmobile-android-runner.yml` both run their only job on `macos-12`, a runner image GitHub fully retired in December 2024. Neither workflow was updated to point at a supported image before this branch was frozen, so both now fail to even schedule a runner on any push or pull request that triggers them. `gradle-wrapper-validation.yml` exists solely to validate the Gradle wrapper used by that same broken Android tooling, and is equally unused as a result. Trunk already removed all three files, in WordPress#76503 and WordPress#79030.
`storybook-pages.yml` deploys the single canonical Storybook GitHub Pages site and only triggers on pushes to `trunk`; there is one deployed site, not one per branch.
`upload-release-to-plugin-repo.yml` triggers on GitHub release publication; Gutenberg plugin releases are cut from `trunk` and release branches, never from `wp/X.Y` branches.
`stale-issue-gardening.yml` is schedule-triggered, and GitHub only ever runs a scheduled workflow using the copy on the repository's default branch, regardless of any copy present elsewhere.
desrosj
force-pushed
the
fix-actions-6.5/remove-rn-workflows
branch
from
September 10, 2026 23:59
acfd502 to
157b993
Compare
…ch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
desrosj
force-pushed
the
fix-actions-6.5/remove-rn-workflows
branch
from
September 14, 2026 01:35
b69b5ec to
dc0e30d
Compare
desrosj
marked this pull request as ready for review
September 15, 2026 21:23
Owner
Author
|
Migrated to the real |
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?
This removes several GitHub Actions workflows from the
wp/6.5branch.rnmobile-ios-runner.ymlmacos-12, a runner image GitHub fully retired in December 2024; it now fails to even schedule a runnerrnmobile-android-runner.ymlmacos-12, a runner image GitHub fully retired in December 2024; it now fails to even schedule a runnergradle-wrapper-validation.ymlstorybook-pages.ymlpush: branches: [trunk]only — a single deploy target, not per-branchupload-release-to-plugin-repo.ymlwp/X.Ybranchesstale-issue-gardening.ymlschedule-triggered workflows only ever run using the default branch's copypublish-npm-packages.ymlis intentionally kept on this branch per updated project policy — it is not removed here.check-components-changelog.yml, which trunk's copy restricts topull_request: branches: [trunk], was intentionally not removed: this branch's copy predates that restriction (added on trunk months afterwp/6.5branched) and still has no branch filter at all, so it genuinely runs — and is potentially useful — on pull requests targeting this branch.Why?
These workflows are not relevant to the branch, mostly due to the fact that they only run from
trunk, are permanently disabled or non-functional, or are not meant for running with non-latest code. Removing them also cuts down on the long-term maintenance burden, and avoids causing confusion.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.