Repository navigation
Repair wp/6.7 branch Actions: Remove obsolete and trunk-only workflows - #82896
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. 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. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
0b90866 to
68184c2
Compare
68184c2 to
5c27587
Compare
…ll_request_target` runs always use the workflow file from trunk, so this branch's copies never run.
e91c789 to
c780ae9
Compare
Part of #82783.
What?
This removes several GitHub Actions workflows from the
wp/6.7branch.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]onlyupload-release-to-plugin-repo.ymlwp/X.Ybranchescherry-pick-wp-release.ymlwp/X.Ybrancheswp/X.Ybranches are its destination, never its triggersync-backport-changelog.ymlpush: branches: [trunk], plus anissues: labeledtrigger that isn't tied to any git ref, so GitHub always runs it from the default branch's copystale-issue-gardening.ymlschedule-triggered workflows only ever run using the default branch's copyperformance.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.Ycheck-dataviews-changelog.ymlandsync-assets-to-plugin-repo.ymldo not exist onwp/6.7, so there is nothing to remove for them here.Why?
These workflows are not relevant to the branch, mostly due to the fact that they only run from
trunk, are not meant for running with non-latest code, or are only maintained for the current WordPress release (performance testing). 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.