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.7 branch Actions: remove obsolete/trunk-only workflowswp/5.7 branch Actions: Remove obsolete and trunk-only workflows
Part of #82936.
What?
Removes obsolete and trunk-only GitHub Actions workflows from
wp/5.7.rnmobile-ios-runner.ymlrnmobile-android-runner.ymlstorybook-pages.ymlpush: branches: [master]only — this frozen branch never pushes tomaster, so the workflow can never run herestale-issue-needs-info.ymlschedule-triggered only — GitHub always executes a scheduled workflow using the default branch's copy, never a frozen branch's own copyupload-release-to-plugin-repo.ymlrelease: types: [released]-triggered only; plugin releases are never published fromwp/5.7, so this branch's copy never runscancel.ymlstyfle/cancel-workflow-actionconcurrency:key withcancel-in-progress: true, which #84766 adds to every relevant workflow on this branchperformance.ymlpull-request-automation.ymlpull_request_targetruns always use trunk's copy of the file, and every run checks outref: masterrather than this branch, so this branch's copy never does anythingbuild-plugin-zip.ymlv*tag is pushedv*tag is pushed, and nov*tags are pushed fromwp/5.7, so it never runs hereWhy?
These workflows either automate functionality this project no longer maintains (React Native), can structurally never execute from a frozen, non-default branch like
wp/5.7(anything gated onschedule,release, orpush: branches: [master]), have been superseded by functionality GitHub Actions now provides natively (cancel.yml), or are only maintained for the current WordPress release (performance testing). Leaving them in place is dead weight at best, and a source of confusion or accidental interference with trunk's own deployments/automation at worst.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.