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
 |
| Layer / File(s) | Summary |
|---|---|
Pull request validation automation .github/workflows/check-backport-changelog.yml, .github/workflows/check-package-changelogs.yml, .github/workflows/pull-request-automation.yml |
Removed changelog validation, project-management automation, contributor welcome comments, and profile-link prompts. |
Backport and issue maintenance automation .github/workflows/cherry-pick-wp-release.yml, .github/workflows/sync-backport-changelog.yml, .github/workflows/stale-issue-gardening.yml |
Removed release-branch cherry-picking, backport changelog synchronization, and scheduled stale-issue processing. |
Repository publishing automation .github/workflows/storybook-pages.yml, .github/workflows/sync-assets-to-plugin-repo.yml |
Removed Storybook GitHub Pages deployment and WordPress.org plugin asset synchronization. |
Plugin release publishing .github/workflows/upload-release-to-plugin-repo.yml |
Removed release validation, changelog updates, SVN tag handling, and plugin publishing jobs. |
Priority:
Estimated code review effort: 3 (Moderate) | ~25 minutes
Change: Other
Merge Risk: 
3717c
-
The removed workflows are obsolete for this branch, with no remaining concrete merge-blocking risk identified.
🚥 Pre-merge checks | ✅ 5
-
✅ Passed checks (5 passed)
-
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 describes the main change: removing obsolete and trunk-only GitHub Actions workflows from the wp/7.1 branch.
-
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create PR with unit tests
- Commit unit tests in branch
fix-actions-7.1/remove-rn-workflows
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
🔵 Needs a closer look
Preserve or split pull-request automation because it also serves PRs targeting wp/7.1.
Pull request overview
Removes obsolete or trunk-specific GitHub Actions workflows from wp/7.1.
Changes:
- Removes changelog, backport, asset-sync, Storybook, stale-issue, and release workflows.
- Removes cherry-pick and pull-request automation.
File summaries
| File | Reviewed change |
|---|---|
.github/workflows/upload-release-to-plugin-repo.yml |
Removes release publishing automation. |
.github/workflows/sync-backport-changelog.yml |
Removes backport changelog synchronization. |
.github/workflows/sync-assets-to-plugin-repo.yml |
Removes asset synchronization. |
.github/workflows/storybook-pages.yml |
Removes Storybook deployment. |
.github/workflows/stale-issue-gardening.yml |
Removes scheduled issue maintenance. |
.github/workflows/pull-request-automation.yml |
Removes pull-request labeling and welcome automation. |
.github/workflows/cherry-pick-wp-release.yml |
Removes release cherry-picking automation. |
.github/workflows/check-package-changelogs.yml |
Removes package changelog validation. |
.github/workflows/check-backport-changelog.yml |
Removes backport changelog validation. |
Review details
Suppressed comments (1)
.github/workflows/pull-request-automation.yml:1
- Unlike the other deleted workflows, this one is not trunk-only:
pull_request_targethas nobranchesfilter, so it runs for PRs targetingwp/7.1. The PR-opened handlers do not check the base branch (packages/project-management-automation/lib/index.js:36-46), so deleting this file removes fixed-issue assignment and first-time-contributor labeling/welcome output for backport-branch PRs; retain or split those jobs and gate only the push-only trunk automation.
- Files reviewed: 9/9 changed files
- Comments generated: 0
- Review effort level: Lite (auto)
Note
Copilot is running an experiment and ran this review at Lite.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
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. |
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved issues were identified in the reviewed workflow removals.
Review details
- Files reviewed: 8/8 changed files
- Comments generated: 0 new
- Review effort level: Lite (auto)
Note
Copilot is running an experiment and ran this review at Lite.
7708c31 to
4ac36e2
Compare
4ac36e2 to
50fbd81
Compare
…l_request_target` runs always use the workflow file from trunk, so this branch's copies never run.
50fbd81 to
525ca70
Compare
Part of #82781.
What?
Removes every workflow whose triggers make it trunk-only, from
wp/7.1.check-backport-changelog.ymlpull_request: branches: [trunk]onlycheck-package-changelogs.ymlCHANGELOG.mdupdatespull_request: branches: [trunk]onlystale-issue-gardening.ymlsync-backport-changelog.ymlpush: branches: [trunk], plus anissues: labeledtrigger that — like the schedule case above — isn't tied to any git ref, so GitHub always runs it from the default branch's copy toosync-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 sourcestorybook-pages.ymlpush: branches: [trunk]onlyupload-release-to-plugin-repo.ymlrelease: types: [published]; in practice, releases are only ever published fromrelease/X.Ybranches, not from numberedwp/X.Ybranches, so this branch is never the context a release actually happens inpull-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 runsNo React Native mobile workflows or
gradle-wrapper-validation.ymlexist on this branch at all — it was cut after those were already removed from trunk.Why?
Keeping dead or inapplicable workflow files around adds maintenance surface (stale action pins, lint noise) with no corresponding benefit.
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