On October 17, WordPress Core is seeking reviewers for roughly 500 pull requests to repair Gutenberg GitHub Actions across more than 20 wp/X.Y branches. The first stacks, covering wp/7.1 through wp/5.7, are ready; work on older branches is still coming.
For contributors deciding where to help, the immediate task is to claim a fix in tracking issue GB-84853, review the corresponding pull requests across branches, and record which branches they covered. Every branch still needs at least one approving review from a member of the WordPress GitHub organization with write access.
What the Gutenberg GitHub Actions review covers
The WordPress Core call for review, posted by Jonathan Desrosiers on October 16, describes broken automated checks and test suites in the Gutenberg repository’s release branches. Some checks fail consistently; others do not run at all. The post attributes this to poorly scoped branch filters, event targeting and other workflow problems.
The repairs go beyond getting a red or missing check to run. The proposed stacks also address degraded local test tooling, including wp-env, Composer and PHPUnit, along with flaky tests. The work includes updating and pinning GitHub Actions and runner images, removing jobs that do not serve a release branch, and adding job timeouts and workflow linting.
Each branch’s test environment is also intended to use software versions that match the WordPress release for that branch. The stated goal is predictable testing with PHP and Node.js versions supported by that release. These changes matter because the repository’s release branches are snapshots of the Gutenberg code used to build WordPress releases.
Why CI repair matters for security backports
WordPress Core’s post says versions 4.7 and later are in security-only support, with selected security patches backported as a courtesy. Gutenberg code is part of WordPress from version 5.0 onward, so fixes to that code can affect older WordPress releases as well as current development.
When checks fail for reasons unrelated to a code change, reviewers and maintainers have a less dependable way to validate changes on those branches. When checks do not run, they provide no result at all. Restoring the branch-specific tests gives people working on backports a functioning validation path before patches ship to users.
That is the practical case for reviewing infrastructure changes even when they do not alter the editor’s visible behavior. The work is about making the checks useful again on release branches, where security fixes may still need to be tested.
How the pull request stacks are organized
Desrosiers prepared a separate pull request stack for each wp/X.Y branch. Each pull request is based on the one below it, so the stack is reviewed from the bottom up. The top pull request runs CI against the full stack, while its Files changed tab shows only that individual pull request’s changes.
Related fixes use matching branch names and titles across branches and sit in roughly the same position in each stack. That lets reviewers follow one repair across several WordPress releases rather than treating every branch as an unrelated project. A fix appears only on branches where the problem exists, and it may be adapted when branch code differs.
The pull request descriptions document the changes and the CI failures or error output they address. The author also says draft pull requests should be treated as AI-produced and not yet human-verified. The stacks were staged and checked before being pushed to the Gutenberg repository, and pull requests were marked ready after a final confirmation.
How to review and claim work
Reviewers should use tracking issue GB-84853 to claim the fix they plan to review. The issue tracks one row per fix across branches, making it possible to see which parts of a stack have already received attention. If a reviewer cannot complete their assigned work within 24 hours, the call asks them to comment on the issue and note the branches they reviewed in the table’s Reviewer column.
Anyone can help with review, but not every review can satisfy the repository’s merge requirement. Gutenberg’s repository rules require at least one approving review from a WordPress GitHub organization member who has write access. Contributors without that access can still review and report findings, while an eligible member must provide the required approval for each branch.
As of October 17, the stacks for wp/7.1 through wp/5.7 are ready in the repository. The remaining branches are expected to be added in the coming days, with updates posted to the tracking issue for people who have already helped.
FAQ
Which Gutenberg branches are ready for review?
The wp/7.1 through wp/5.7 branches are ready as of October 17, 2026. Work on older branches is still being prepared.
How many pull requests are part of the CI repair effort?
The effort covers roughly 500 pull requests across more than 20 Gutenberg release branches. The fixes are grouped into branch-specific stacks, with related changes aligned across branches where possible.
Who can approve a pull request for merging?
Anyone can help review, but each branch needs at least one approving review from a member of the WordPress GitHub organization who has write access to the Gutenberg repository. Reviewers should claim their work and record completed branches in GB-84853.
Next step: Open GB-84853, claim an unreviewed fix, and record the branches you complete so other reviewers can avoid duplicating the work.