Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
This was referenced Sep 18, 2026
desrosj
marked this pull request as ready for review
September 21, 2026 15:19
|
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. |
desrosj
added this pull request to stack #82812
September 21, 2026 17:38
desrosj
removed this pull request from stack #82812
September 22, 2026 16:29
desrosj
changed the base branch from
fix-actions-7.0/guard-setaccessible-php85
to
wp/7.0
September 22, 2026 16:29
desrosj
force-pushed
the
fix-actions-7.0/pin-performance-tests-wp-version
branch
from
September 22, 2026 16:32
47dd4b5 to
f8c71f5
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/remove-disabled-mobile-unit-js
September 22, 2026 16:33
desrosj
added this pull request to stack #83387
September 22, 2026 16:33
|
Size Change: 0 B Total Size: 7.61 MB ℹ️ View Unchanged
|
…ranch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
desrosj
removed this pull request from stack #83387
September 22, 2026 21:48
desrosj
changed the base branch from
fix-actions-7.0/remove-disabled-mobile-unit-js
to
wp/7.0
September 22, 2026 21:48
desrosj
force-pushed
the
fix-actions-7.0/pin-performance-tests-wp-version
branch
from
September 22, 2026 21:50
f8c71f5 to
8d6f311
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/remove-disabled-mobile-unit-js
September 22, 2026 21:51
desrosj
added this pull request to stack #83409
September 22, 2026 21:52
desrosj
removed this pull request from stack #83409
September 28, 2026 15:38
desrosj
changed the base branch from
fix-actions-7.0/remove-disabled-mobile-unit-js
to
wp/7.0
September 28, 2026 15:39
…h-triggered tasks (`add-milestone`, `first-time-contributor-account-link`) both bail out immediately outside of `trunk`, so running them here on every push does nothing.
desrosj
force-pushed
the
fix-actions-7.0/pin-performance-tests-wp-version
branch
from
October 7, 2026 15:58
b91cbbd to
fbad641
Compare
desrosj
force-pushed
the
fix-actions-7.0/remove-disabled-mobile-unit-js
branch
from
October 7, 2026 15:58
001f5c9 to
7261a8b
Compare
desrosj
removed this pull request from stack #83630
October 7, 2026 18:13
desrosj
changed the base branch from
fix-actions-7.0/remove-disabled-mobile-unit-js
to
wp/7.0
October 7, 2026 18:14
Member
Author
|
Closing: the performance tests workflow is removed from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #82782.
What?
This pins WordPress 7.0 as the version to use when running the performance tests on
pull_requestevents.Why?
While this branch's
.wp-env.jsonpins Core asWordPress/WordPress#7.0-branch, the performance testing workflow never reads that file.bin/plugin/cli.js perfbuilds its own, separate.wp-env.jsonfor each branch it measures, and that file'scorefield is only pinned when an explicit--wp-versionargument is passed.With no
--wp-version,wpZipUrlstaysnulland the environment falls back toWordPress/WordPress— WordPress Core's own development trunk. The CLI even says so out loud, loggingUsing: WordPress trunkinstead ofUsing: WordPress v7.0.That means the
pull_requestjob was measuring this branch's frozen Gutenberg snapshot against a continuously moving Core install, ignoring the branch's own Core pin entirely. That makes the numbers meaningless at best, and breaks the suite outright once Core's architecture drifts far enough from what this branch's editor expects.--wp-version "7.0"resolves tohttps://wordpress.org/wordpress-7.0.zip(confirmed available), giving the performance tests the same Core pin every other test suite on this branch already uses.This workflow's
release,push, andworkflow_dispatchsteps already pass--wp-version; thepull_requeststep was the only one missing it. Nothing else about the step changes — its name and its"$GITHUB_BASE_REF"argument are already correct on this 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