Skip to content

Repair wp/7.0 branch Actions: Run macOS and Windows jobs only on WordPress/gutenberg - #85128

Open
desrosj wants to merge 1 commit into
fix-actions-7.0/remove-flaky-test-report-leftoversfrom
fix-actions-7.0/limit-fork-runner-os
Open

desrosj wants to merge 1 commit into
fix-actions-7.0/remove-flaky-test-report-leftoversfrom
fix-actions-7.0/limit-fork-runner-os

Conversation

@desrosj

@desrosj desrosj commented Oct 19, 2026

Copy link
Copy Markdown
Member

Part of #82782.

What?

Replaces the fixed os list in create-block.yml's checks job and static-checks.yml's check job with one chosen by repository. Runs on WordPress/gutenberg, including pull requests opened from forks, keep the macos-15, ubuntu-24.04 and windows-2025 legs, while runs inside a fork only use ubuntu-24.04. The event matrix dimension and the event-based pull request exclude entries in both jobs are removed.

Why?

macOS and Windows runner minutes cost more than Ubuntu ones. Contributors running these workflows inside their own forks only need the Ubuntu leg, but every change proposed to WordPress/gutenberg should still be checked on every operating system before it lands.

This branch inherited event-based excludes from trunk that skip the macOS leg of both jobs and the Windows leg of create-block.yml on every pull request, including pull requests to WordPress/gutenberg, so changes proposed to this branch were not checked on those operating systems before merging. Keying on the repository instead keeps them for runs on WordPress/gutenberg and drops them only inside forks, so the excludes, and the event dimension that existed only to feed them, are no longer needed.

How?

For pull_request events, github.repository is the base repository, so a pull request from a fork to WordPress/gutenberg still gets the full list. fromJSON turns each JSON string into the array the matrix expects. The existing job-level if: conditions are unchanged.

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 19, 2026
@desrosj desrosj self-assigned this Oct 19, 2026
@desrosj
desrosj added this pull request to stack #84468 October 19, 2026 17:04
@coderabbitai

coderabbitai Bot commented Oct 19, 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
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9f7eb188-fca7-4582-9168-33a66496afb1

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 force-pushed the fix-actions-7.0/limit-fork-runner-os branch from 69dbe12 to 143347f Compare October 19, 2026 17:19
@desrosj
desrosj marked this pull request as ready for review October 19, 2026 17:23
@github-actions

github-actions Bot commented Oct 19, 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.

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: ramonjd <ramonopoly@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 removed this pull request from stack #84468 October 21, 2026 18:35
@desrosj
desrosj added this pull request to stack #85325 October 21, 2026 18:35
@desrosj
desrosj force-pushed the fix-actions-7.0/limit-fork-runner-os branch from 143347f to e2e623f Compare October 23, 2026 17:27

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