Skip to content

Repair wp/6.7 branch Actions: Remove obsolete and trunk-only workflows - #82896

Merged
desrosj merged 9 commits into
wp/6.7from
fix-actions-6.7/remove-rn-workflows
Oct 27, 2026
Merged

desrosj merged 9 commits into
wp/6.7from
fix-actions-6.7/remove-rn-workflows

Conversation

@desrosj

@desrosj desrosj commented Sep 14, 2026 •

Copy link
Copy Markdown
Member

Part of #82783.

What?

This removes several GitHub Actions workflows from the wp/6.7 branch.

Workflow Purpose Reason removed Trunk removal PR
rnmobile-ios-runner.yml React Native iOS E2E test runner Job hardcodes if: false; hasn't executed since before this branch existed #76503
rnmobile-android-runner.yml React Native Android E2E test runner Job hardcodes if: false; hasn't executed since before this branch existed #76503
gradle-wrapper-validation.yml Validates the Gradle wrapper checksum used by the React Native Android build Orphaned once the Android E2E workflow it supported was permanently disabled #79030
storybook-pages.yml Deploys the canonical Storybook GitHub Pages site push: branches: [trunk] only — a single deploy target, not per-branch N/A — still active on trunk
check-components-changelog.yml Verifies a CHANGELOG update on PRs touching packages/components pull_request: branches: [trunk] only N/A — still active on trunk
check-backport-changelog.yml Verifies Core backport changelog notes on PRs touching lib//phpunit/ pull_request: branches: [trunk] only N/A — still active on trunk
upload-release-to-plugin-repo.yml Uploads the built plugin zip to the WordPress.org SVN repo on release publish Plugin releases are cut from trunk/release branches, never from wp/X.Y branches N/A — still active on trunk
cherry-pick-wp-release.yml Auto-cherry-picks labeled trunk commits into wp/X.Y branches Only triggers on trunk push/labeled PR; wp/X.Y branches are its destination, never its trigger N/A — still active on trunk
sync-backport-changelog.yml Syncs the "Core Backport" tracking issue on trunk pushes and issue-label events push: branches: [trunk], plus an issues: labeled trigger that isn't tied to any git ref, so GitHub always runs it from the default branch's copy N/A — still active on trunk
stale-issue-gardening.yml Daily scheduled bot that marks/closes stale issues and PRs schedule-triggered workflows only ever run using the default branch's copy N/A — still active on trunk
performance.yml Performance tests Performance testing is only maintained on the branch for the current WordPress release N/A — still active on trunk
pull-request-automation.yml Assigns fixed issues and labels first-time contributors on new pull requests pull_request_target runs always use trunk's copy of the file, and its push-triggered tasks return immediately outside trunk, so this branch's copy never does anything N/A — still active on trunk
enforce-pr-labels.yml Requires exactly one [Type] label on each pull request pull_request_target only, and those runs always use trunk's copy of the file, so this branch's copy never runs N/A — still active on trunk
build-plugin-zip.yml Builds the plugin zip, and holds the plugin release jobs (version bump, GitHub release, npm latest publish) Nothing uses the zip it builds: WordPress 6.7 takes Gutenberg as npm packages. The release jobs only run when started from trunk or a release/* branch, so they never run from wp/X.Y N/A — still active on trunk

check-dataviews-changelog.yml and sync-assets-to-plugin-repo.yml do not exist on wp/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.

@desrosj desrosj added the [Type] Build Tooling Issues or PRs related to build tooling label Sep 14, 2026
@desrosj desrosj self-assigned this Sep 14, 2026
@coderabbitai

coderabbitai Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 48c7737b-eda2-46bb-939b-07e422e1dcec

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

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.

Co-authored-by: desrosj <desrosj@git.wordpress.org>
Co-authored-by: lucatume <lucatume@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

…ll_request_target` runs always use the workflow file from trunk, so this branch's copies never run.
@desrosj
desrosj removed this pull request from stack #84188 October 8, 2026 21:24
@desrosj
desrosj removed this pull request from stack #84474 October 21, 2026 18:31
@desrosj
desrosj added this pull request to stack #85321 October 21, 2026 18:32
@desrosj desrosj added the props-bot Manually triggers Props Bot to ensure the list of props is up to date. label Oct 26, 2026
@github-actions github-actions Bot removed the props-bot Manually triggers Props Bot to ensure the list of props is up to date. label Oct 26, 2026
@desrosj
desrosj merged commit 5f595d4 into wp/6.7 Oct 27, 2026
18 of 46 checks passed
@desrosj
desrosj deleted the fix-actions-6.7/remove-rn-workflows branch October 27, 2026 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Build Tooling Issues or PRs related to build tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants