Repository navigation
Conversation
|
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. |
…ys use the workflow file from trunk, so this branch's copy never runs.
aca1fec to
c4bd296
Compare
desrosj
changed the title
wp/6.3 branch Actions: Remove RN mobile and trunk-only workflowswp/6.3 branch Actions: Remove obsolete and trunk-only workflows
lucatume
left a comment
lucatume
left a comment
There was a problem hiding this comment.
Wrappers stay for the same reason as the 6.2 PR.
Part of #82930.
What?
Removes GitHub Actions workflows from
wp/6.3that can no longer run successfully, that only ever make sense running fromtrunk, that enforce a contributor convention with no meaning on a frozen branch, or that are only maintained for the current WordPress release.rnmobile-ios-runner.ymlmacos-12, retired by GitHub in December 2024; React Native mobile support is no longer maintained or shipped by Gutenbergrnmobile-android-runner.ymlmacos-12, retired by GitHub in December 2024; React Native mobile support is no longer maintained or shipped by Gutenberggradle-wrapper-validation.ymlrnmobile-android-runner.ymlis removedstorybook-pages.ymltrunk; this branch never pushes thereupload-release-to-plugin-repo.ymlreleaseevent published from the main plugin release process, which this branch doesn't participate instale-issue-gardening.ymlcheck-components-changelog.ymlpackages/componentsunless it also adds a## Unreleasedentry topackages/components/CHANGELOG.mdlinking back to the PR## Unreleasedsection stages changes for the next@wordpress/componentsnpm release, but packages are never published from this branch (publish-npm-packages.ymlisworkflow_dispatch-only and hard-codesref: trunk), so an entry added here would never reach a published changelog. The check is explicitly optional/advisory guidance for ongoingtrunkdevelopment, not for a frozen branch that only takes targeted backportsperformance.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.ymllatestpublish)trunkor arelease/*branch, so they never run fromwp/X.Ypublish-npm-packages.ymlis kept: it is manually dispatched only, and both of its checkout steps hard-coderef: trunk, so it can never publish from this branch.Why?
These workflows are either structurally incapable of running on a frozen release branch (trunk-only push/release/schedule triggers, or hard-coded
ref: trunkcheckouts), depend on a GitHub-hosted runner image (macos-12) that no longer exists, test React Native mobile code that Gutenberg no longer maintains or ships, enforce a changelog convention whose only destination is an npm release that never happens from this branch, or are only maintained for the current WordPress release (performance testing). Keeping them around adds maintenance noise and workflow content that references tooling for a platform this project no longer supports.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.