Skip to content

Repair wp/5.9 branch Actions: Remove the mobile-unit-js job - #84399

Open
desrosj wants to merge 1 commit into
fix-actions-5.9/fix-workflow-branch-filtersfrom
fix-actions-5.9/remove-mobile-unit-js-job
Open

desrosj wants to merge 1 commit into
fix-actions-5.9/fix-workflow-branch-filtersfrom
fix-actions-5.9/remove-mobile-unit-js-job

Conversation

@desrosj

@desrosj desrosj commented Oct 9, 2026

Copy link
Copy Markdown
Member

Part of #82934.

What?

Removes the mobile-unit-js job (job name Mobile) from .github/workflows/unit-test.yml.

Why?

This job is not broken, and it is not disabled. Unlike the equivalent job on wp/7.0 and wp/6.9 — where it carries a hardcoded if: false — this branch's copy has the ordinary if: ${{ github.repository == 'WordPress/gutenberg' || github.event_name == 'pull_request' }} condition, runs on every push and pull request, and currently passes. It is being removed for scope and consistency, not because of a failure.

The job runs the React Native mobile unit tests. On this branch it does so via npm run native test, which resolves to npm run --prefix packages/react-native-editor test, i.e. the react-native-editor package's own Jest suite configured by test/native/jest.config.js. (Note this is the older script form — the test:native root script that later branches invoke does not exist here.)

React Native mobile support is no longer maintained or shipped as part of Gutenberg, and the bottom PR in this stack already removed the React Native workflows on that basis: rnmobile-android-runner.yml and rnmobile-ios-runner.yml were dropped as providing no signal worth spending CI resources on for a frozen, security-maintenance-only branch. mobile-unit-js is the last remaining piece of that same testing surface still running here. Leaving it behind means this branch keeps paying runner time on every PR to test a platform it will never ship a fix for, while the E2E half of that story is already gone — an inconsistent end state.

Any dangling references?

None. Nothing under .github/ references mobile-unit-js in a needs: list or anywhere else, and the job declares no outputs. The file's remaining two jobs, unit-js (JavaScript) and unit-php (PHP), are independent and untouched; the workflow still parses with exactly those two jobs.

Testing Instructions

The Mobile check should no longer appear in the Unit Tests workflow run for this PR. JavaScript and the PHP * matrix jobs should behave exactly as they do on the base branch.

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.

🤖 Generated with Claude Code

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

coderabbitai Bot commented Oct 9, 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: 945a59af-668b-42e4-99ab-cc8b844dd60d

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.

@desrosj
desrosj removed this pull request from stack #84427 October 10, 2026 00:16
@desrosj
desrosj changed the base branch from fix-actions-5.9/fix-workflow-branch-filters to wp/5.9 October 10, 2026 00:17
@desrosj
desrosj force-pushed the fix-actions-5.9/remove-mobile-unit-js-job branch from f1858c8 to 38e50f1 Compare October 10, 2026 00:19
@desrosj
desrosj changed the base branch from wp/5.9 to fix-actions-5.9/fix-workflow-branch-filters October 10, 2026 00:20
@desrosj
desrosj added this pull request to stack #84490 October 10, 2026 00:21
@desrosj
desrosj marked this pull request as ready for review October 13, 2026 00:57
@github-actions

github-actions Bot commented Oct 13, 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. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @tellthemachines.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: tellthemachines.

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

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

@desrosj desrosj changed the title Repair wp/5.9 branch Actions: remove the mobile-unit-js job Repair wp/5.9 branch Actions: Remove the mobile-unit-js job Oct 16, 2026

@tellthemachines tellthemachines left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Are the descriptions for these PRs AI-generated? I've been noticing how they differ slightly on all the branches from 6.8 downwards while having the same info.

@desrosj
desrosj removed this pull request from stack #84490 October 21, 2026 15:57
@desrosj
desrosj added this pull request to stack #85300 October 21, 2026 15:58
@desrosj

desrosj commented Oct 21, 2026

Copy link
Copy Markdown
Member Author

Are the descriptions for these PRs AI-generated? I've been noticing how they differ slightly on all the branches from 6.8 downwards while having the same info.

They are. I instructed it to use the same descriptions for each fix across every stack's corresponding PR, except when there is context specific to a given branch. It generally did an OK job, but I think that strayed a bit when I made revisions only to specific branch ranges (ie. 6.8-6.4, or something similar).

@desrosj
desrosj removed this pull request from stack #85300 October 21, 2026 19:47
@desrosj
desrosj added this pull request to stack #85350 October 21, 2026 19:47

This branch has not been deployed

No deployments
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