Automated Testing: Include Windows build for GitHub Actions static checks#73923
Conversation
Now including Windows
aduth
added
the
[Type] Automated Testing
|
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. |
|
Seen in GitHub checks: 
We may want to follow-up to make this "Required" at some point. |
|
Flaky tests detected in ca2d397. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/20142282135
|
2 participants
What?
Updates GitHub Actions configuration to include Windows on Node.js 20 for "Static Analysis" checks in pull requests.
Why?
There have been numerous recent issues relating to code changes that are incompatible with Windows environments:
The situation was improved slightly in #72946, where we started running builds for Windows environments on the
trunkbranch. However, this is too late in the process, and is easily overlooked for some time.How?
Since previous issues largely manifest as a result of
npm run build, the changes here are isolated to adding a single build check for pull requests to run the "Static checks" build pipeline for Windows + Node.js 20.This is a minimal compromise that aims to preserve CI optimizations introduced in #72506.
Testing Instructions
Observe that the build checks for this pull request include one passing build for Windows + Node.js 20 with "Static checks".