Skip to content

Repair wp/6.7 branch Actions: Remove obsolete and trunk-only workflows - #52

Closed
desrosj wants to merge 7 commits into
wp/6.7from
fix-actions-6.7/remove-rn-workflows
Closed

desrosj wants to merge 7 commits into
wp/6.7from
fix-actions-6.7/remove-rn-workflows

Conversation

@desrosj

@desrosj desrosj commented Aug 26, 2026 •

Copy link
Copy Markdown
Owner

What?

This removes several GitHub Actions workflows from the wp/6.7 branch.

Workflow Purpose Reason removed Trunk removal PR
rnmobile-ios-runner.yml React Native iOS E2E test runner Job hardcodes if: false; hasn't executed since before this branch existed WordPress#76503
rnmobile-android-runner.yml React Native Android E2E test runner Job hardcodes if: false; hasn't executed since before this branch existed WordPress#76503
gradle-wrapper-validation.yml Validates the Gradle wrapper checksum used by the React Native Android build Orphaned once the Android E2E workflow it supported was permanently disabled WordPress#79030
storybook-pages.yml Deploys the canonical Storybook GitHub Pages site push: branches: [trunk] only — a single deploy target, not per-branch N/A — still active on trunk
check-components-changelog.yml Verifies a CHANGELOG update on PRs touching packages/components pull_request: branches: [trunk] only N/A — still active on trunk
check-backport-changelog.yml Verifies Core backport changelog notes on PRs touching lib//phpunit/ pull_request: branches: [trunk] only N/A — still active on trunk
upload-release-to-plugin-repo.yml Uploads the built plugin zip to the WordPress.org SVN repo on release publish Plugin releases are cut from trunk/release branches, never from wp/X.Y branches N/A — still active on trunk
cherry-pick-wp-release.yml Auto-cherry-picks labeled trunk commits into wp/X.Y branches Only triggers on trunk push/labeled PR; wp/X.Y branches are its destination, never its trigger N/A — still active on trunk
sync-backport-changelog.yml Syncs the "Core Backport" tracking issue on trunk pushes and issue-label events push: branches: [trunk] only N/A — still active on trunk
stale-issue-gardening.yml Daily scheduled bot that marks/closes stale issues and PRs schedule-triggered workflows only ever run using the default branch's copy N/A — still active on trunk

storybook-check.yml, check-dataviews-changelog.yml, and sync-assets-to-plugin-repo.yml — present in the equivalent cleanup on wp/6.9 — do not exist on wp/6.7, so there is nothing to remove for them here.

publish-npm-packages.yml is 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.

`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.
@desrosj
desrosj removed this pull request from stack #90 September 10, 2026 19:33
@desrosj
desrosj added this pull request to stack #185 September 10, 2026 19:36
`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
desrosj force-pushed the fix-actions-6.7/remove-rn-workflows branch from 7b9f7cf to fcb256a Compare September 10, 2026 23:53
@desrosj
desrosj marked this pull request as ready for review September 11, 2026 02:43
@desrosj
desrosj marked this pull request as draft September 11, 2026 03:22
@github-actions

Copy link
Copy Markdown

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

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
desrosj force-pushed the fix-actions-6.7/remove-rn-workflows branch from 1e8cac7 to dd8b468 Compare September 14, 2026 01:38
@desrosj
desrosj marked this pull request as ready for review September 14, 2026 19:29
@desrosj
desrosj marked this pull request as draft September 14, 2026 19:31
@desrosj
desrosj marked this pull request as ready for review September 14, 2026 19:38
@desrosj

desrosj commented Sep 15, 2026

Copy link
Copy Markdown
Owner Author

Migrated to real upstream: WordPress#82896. Closing this fork PR.

@desrosj desrosj closed this Sep 15, 2026
@desrosj
desrosj deleted the fix-actions-6.7/remove-rn-workflows branch October 29, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant