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:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Description Check | ✅ Passed | Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | ✅ Passed | The title clearly summarizes the main change: it removes obsolete and trunk-only GitHub Actions workflows from the wp/7.0 branch. |
✨ Finishing Touches 💡 1
-
🛠️ Fix failing CI checks 💡
-
- Create stacked PR
- Commit on current branch
🧪 Generate unit tests (beta)
-
- Create PR with unit tests
- Commit unit tests in branch
fix-actions-7.0/remove-rn-workflows
-
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 @coderabbitai help to get the list of available commands.
There was a problem hiding this comment.
🟢 Approval recommended
The removals align with each workflow’s trigger semantics and do not eliminate meaningful wp/7.0 automation.
Pull request overview
Removes workflows from wp/7.0 that are disabled, trunk-specific, or executed from the default branch.
Changes:
- Removes disabled React Native workflows and related Gradle validation.
- Removes trunk-only release, deployment, and changelog automation.
- Removes redundant repository-management workflows.
File summaries
| File | Description |
|---|---|
check-backport-changelog.yml |
Removes trunk-only backport validation. |
check-components-changelog.yml |
Removes trunk-only Components validation. |
check-dataviews-changelog.yml |
Removes trunk-only DataViews validation. |
cherry-pick-wp-release.yml |
Removes trunk-originated cherry-picking. |
gradle-wrapper-validation.yml |
Removes validation for unused mobile tooling. |
pull-request-automation.yml |
Removes the redundant branch copy. |
rnmobile-android-runner.yml |
Removes disabled Android E2E tests. |
rnmobile-ios-runner.yml |
Removes disabled iOS E2E tests. |
stale-issue-gardening.yml |
Removes default-branch scheduled automation. |
storybook-pages.yml |
Removes trunk-only Storybook deployment. |
sync-assets-to-plugin-repo.yml |
Removes trunk-only asset synchronization. |
sync-backport-changelog.yml |
Removes trunk/default-branch synchronization. |
upload-release-to-plugin-repo.yml |
Removes plugin-release publishing automation. |
Review details
- Files reviewed: 13/13 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🔵 Needs a closer look
Removing the active Gradle wrapper validation leaves backports without wrapper-integrity checks.
Review details
Suppressed comments (1)
.github/workflows/gradle-wrapper-validation.yml:1
- This workflow is not inactive like the mobile E2E jobs: it runs on every push and PR and validates the three committed, executable Gradle wrapper JARs.
wp/X.Ybranches still receive bug/security backports (docs/contributors/code/release/package-release-and-core-updates.md:42-52), so deleting this check removes the only wrapper-integrity validation from changes targeting this branch. Please retain it, optionally narrowing it with path filters for the wrapper files.
- Files reviewed: 12/12 changed files
- Comments generated: 0 new
- Review effort level: Balanced
|
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. |
2496ed1 to
bb1c733
Compare
bb1c733 to
80020a7
Compare
…l_request_target` runs always use the workflow file from trunk, so this branch's copies never run.
e11e87a to
b823ba2
Compare
Part of #82782.
What?
Removes obsolete React Native mobile workflows, every workflow whose triggers make it trunk-only, and the performance tests, which are only maintained for the current WordPress release, from
wp/7.0.rnmobile-ios-runner.ymlif: false; has not run since before this branch existedrnmobile-android-runner.ymlif: false; has not run since before this branch existedgradle-wrapper-validation.ymlstorybook-pages.ymlpush: branches: [trunk]onlycheck-backport-changelog.ymlpull_request: branches: [trunk]onlycheck-components-changelog.yml@wordpress/componentschangelog entrypull_request: branches: [trunk]onlycheck-dataviews-changelog.yml@wordpress/dataviewschangelog entrypull_request: branches: [trunk]onlyupload-release-to-plugin-repo.ymltrunk/release branches, neverwp/X.Ysync-assets-to-plugin-repo.ymlassets/**to the WordPress.org plugin repopush: branches: [trunk]onlycherry-pick-wp-release.ymlwp/X.Ybranchestrunk; this branch is its destination, never its trigger sourcesync-backport-changelog.ymlpush: branches: [trunk], plus anissues: labeledtrigger that isn't tied to any git ref — like the schedule case below, GitHub always runs it from the default branch's copy regardless of what's on this branchstale-issue-gardening.ymlperformance.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 runspr-labeling-automation.ymlpull_request_targetonly, and those runs always use trunk's copy of the file, so this branch's copy never runsWhy?
Keeping dead or inapplicable workflow files around adds maintenance surface (stale action pins, lint noise) with no corresponding benefit.
Apart from the performance tests, which are only maintained for the current WordPress release, the workflows removed cannot be meaningfully executed against a branch other than
trunk.scheduleevents, the event only ever fires for the default branch.trunk(except minor releases, which come from the respectiverelease/X.Ybranch).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.
Summary by CodeRabbit