Repository navigation
Conversation
`rnmobile-ios-runner.yml` and `rnmobile-android-runner.yml` both hardcode `if: false` on their only job and have not run on any push or pull request since before this branch existed. `gradle-wrapper-validation.yml` exists solely to validate the Gradle wrapper used by that same disabled 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. `storybook-check.yml` does not exist on this branch, so only this one file needs to be removed here.
`check-components-changelog.yml` and `check-backport-changelog.yml` both trigger on `pull_request: branches: [trunk]`, so neither can run against a pull request targeting this branch. `check-dataviews-changelog.yml` does not exist on this branch, so only these two files need to be removed here.
`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. `sync-assets-to-plugin-repo.yml` does not exist on this branch, so only this one file needs to be removed here.
`cherry-pick-wp-release.yml` only triggers on pushes to `trunk` or labeled pull requests targeting `trunk`. `wp/X.Y` branches, including this one, are the destination its `git push` step writes to, never its trigger source. `publish-npm-packages.yml` is being kept on this branch per updated project policy.
`sync-backport-changelog.yml` triggers only on pushes to `trunk` (plus an issue-label event unrelated to any branch). `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.7/remove-rn-workflows
branch
from
September 10, 2026 23:53
7b9f7cf to
fcb256a
Compare
desrosj
marked this pull request as ready for review
September 11, 2026 02:43
desrosj
marked this pull request as draft
September 11, 2026 03:22
|
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. |
…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.7/remove-rn-workflows
branch
from
September 14, 2026 01:38
1e8cac7 to
dd8b468
Compare
desrosj
marked this pull request as ready for review
September 14, 2026 19:29
desrosj
marked this pull request as draft
September 14, 2026 19:31
desrosj
marked this pull request as ready for review
September 14, 2026 19:38
Owner
Author
|
Migrated to real upstream: WordPress#82896. Closing this fork PR. |
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.7branch.rnmobile-ios-runner.ymlif: false; hasn't executed since before this branch existedrnmobile-android-runner.ymlif: false; hasn't executed since before this branch existedgradle-wrapper-validation.ymlstorybook-pages.ymlpush: branches: [trunk]only — a single deploy target, not per-branchcheck-components-changelog.ymlpackages/componentspull_request: branches: [trunk]onlycheck-backport-changelog.ymllib//phpunit/pull_request: branches: [trunk]onlyupload-release-to-plugin-repo.ymlwp/X.Ybranchescherry-pick-wp-release.ymlwp/X.Ybrancheswp/X.Ybranches are its destination, never its triggersync-backport-changelog.ymlpush: branches: [trunk]onlystale-issue-gardening.ymlschedule-triggered workflows only ever run using the default branch's copystorybook-check.yml,check-dataviews-changelog.yml, andsync-assets-to-plugin-repo.yml— present in the equivalent cleanup onwp/6.9— do not exist onwp/6.7, so there is nothing to remove for them here.publish-npm-packages.ymlis being kept on this branch per updated project policy, and is no longer part of this removal.Why?
These workflows are not relevant to the branch, mostly due to the fact that they only run from
trunk, 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.