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. |
…ll_request_target` runs always use the workflow file from trunk, so this branch's copies never run.
b059616 to
907f35f
Compare
Part of #82929.
What?
Removes GitHub Actions workflow files from
wp/6.4that are fully obsolete, only meaningful when running fromtrunk, or only maintained for the current WordPress release.rnmobile-ios-runner.ymlmacos-12, retired by GitHub in December 2024rnmobile-android-runner.ymlmacos-12, retired by GitHub in December 2024gradle-wrapper-validation.ymlstorybook-pages.ymlpush: branches: [trunk]only; there is one canonical deployed site, not one per branchupload-release-to-plugin-repo.ymlrelease: types: [published]; Gutenberg plugin releases are cut fromtrunkand release branches, never fromwp/X.Ybranchesstale-issue-gardening.ymlschedule-triggered; GitHub only ever runs a scheduled workflow using the copy on the repository's default branchcheck-components-changelog.ymlpackages/components/to add a## Unreleasedentry topackages/components/CHANGELOG.mdlinking to the PR@wordpress/componentsrelease is cut fromwp/X.Y, and the required link pattern is hardcoded toWordPress/gutenbergPR URLsphp-changes-detection.ymlwp/6.4mirrors the Gutenberg code already shipped in WordPress 6.4; changes here are maintenance for a released version, handled by the established backport process, so the bot's advice is wrong on every PR it posts toperformance.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 anythingenforce-pr-labels.yml[Type]label on each pull requestpull_request_targetonly, and those runs always use trunk's copy of the file, so this branch's copy never runsbuild-plugin-zip.ymllatestpublish)trunkor arelease/*branch, so they never run fromwp/X.YWhy?
Apart from the performance tests, which are only maintained for the current WordPress release, none of these workflows can do useful work from a frozen maintenance branch. The React Native mobile workflows can't even schedule a runner anymore since GitHub retired the
macos-12image they're pinned to. The remaining workflows are all gated totrunk(by push branch, release-cut convention, scheduled-workflow semantics, or a hardcodedref: trunkcheckout), so their copies onwp/6.4never execute anything meaningful and only add noise and maintenance burden.Both
check-components-changelog.ymlandphp-changes-detection.ymlareOPTIONAL(non-blocking) checks with nobranches:filter, so unlike thetrunk-gated workflows above they really do run againstwp/6.4pull requests. They are removed for the opposite reason: they run, and what they produce is wrong. The CHANGELOG check can only ever fail here, and the PHP detection bot can only ever post backport instructions that do not apply to a released branch. Removing them also drops this branch's last references totj-actions/changed-files,peter-evans/find-comment, andpeter-evans/create-or-update-comment.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.