Repository navigation
Conversation
…ys use the workflow file from trunk, so this branch's copy never runs.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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. |
desrosj
changed the title
wp/5.8 branch Actions: remove obsolete/trunk-only workflowswp/5.8 branch Actions: Remove obsolete and trunk-only workflows
Part of #82935.
What?
Removes obsolete React Native mobile E2E workflows, workflows that only ever execute from
trunk, and the performance testing workflow from thewp/5.8branch.rnmobile-android-runner.ymlif: ${{ false }}— already fully dead. React Native support is also no longer maintained/shipped from Gutenberg.rnmobile-ios-runner.ymlxcode: 12.2onmacos-latest; current macOS runner images no longer include Xcode 12. React Native support is also no longer maintained/shipped from Gutenberg.storybook-pages.ymlpushtotrunkand explicitly checks outref: trunk— never reaches its deploy target from this branch.upload-release-to-plugin-repo.ymlrelease: types: [published]; plugin releases are never published fromwp/5.8, so this branch's copy never runs.stale-issue-add-needs-testing.ymlschedule-only trigger — always runs from trunk's copy.stale-issue-mark-stale.ymlschedule-only trigger — always runs from trunk's copy.stale-issue-needs-info.ymlschedule-only trigger — always runs from trunk's copy.performance.ymlpull-request-automation.ymlpull_request_targetruns always use trunk's copy of the file, and itspush-triggered tasks return immediately outsidetrunk, so this branch's copy never does anythingbuild-plugin-zip.ymltrunk, so they never run fromwp/5.8This branch does not have
gradle-wrapper-validation.yml, anycheck-*-changelog.yml,cherry-pick-wp-release.yml,publish-npm-packages.yml,sync-assets-to-plugin-repo.yml, orsync-backport-changelog.yml— so there is nothing else in these categories to remove here.Why?
wp/5.8is a frozen, security-maintenance-only branch. Workflows that only ever execute using another branch's copy of the file (trunk-push or schedule triggers, or release events that never come from this branch), or are only maintained for the current WordPress release (performance testing), add maintenance surface — stale action pins to track, confusing signal in workflow-run history — without ever actually protecting this branch. React Native mobile support is not maintained or shipped from Gutenberg at all anymore, so its CI workflows have no ongoing value regardless of their current enabled/disabled state.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.