Repository navigation
Conversation
|
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. |
|
Flaky tests detected in e2df481. 🔍 Workflow run URL: https://github.com/desrosj/gutenberg/actions/runs/34549523255 ensures List View global shortcut works properly in
|
wp/6.9 branch Actions: Remove obsolete and trunk-only workflows
`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.
bed527f to
fe9156e
Compare
fe9156e to
ca77fa7
Compare
ca77fa7 to
d7e05bb
Compare
`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` is kept. It builds Storybook and runs each story's interaction tests on a bare `pull_request` trigger with no branch restriction at all, so it genuinely still runs against PRs targeting this branch.
`check-components-changelog.yml`, `check-backport-changelog.yml`, and `check-dataviews-changelog.yml` all trigger on `pull_request: branches: [trunk]`, so none of them can run against a pull request targeting this 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. `sync-assets-to-plugin-repo.yml` triggers only on pushes to `trunk` that touch `assets/**`.
`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 per updated project policy; it is intentionally not removed here.
`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.
e2df481 to
d848519
Compare
…ch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
d848519 to
257a277
Compare
|
Migrated to real upstream: WordPress#82864. Closing this fork PR. |
What?
This removes several GitHub Actions workflows from the
wp/6.9branch.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]onlycheck-dataviews-changelog.ymlpackages/dataviewspull_request: branches: [trunk]onlyupload-release-to-plugin-repo.ymlwp/X.Ybranchessync-assets-to-plugin-repo.ymlpush: branches: [trunk], paths: [assets/**]onlycherry-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 copyWhy?
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.