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
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. 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. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
4487269 to
1b140c1
Compare
1b140c1 to
b002c3c
Compare
b002c3c to
7f25bd9
Compare
🤖 PR meta 🤖📦 Bundle sizeSize Change: 0 B Total Size: 7.75 MB From |
7f25bd9 to
767f8ca
Compare
767f8ca to
acabdd8
Compare
acabdd8 to
7ae776d
Compare
Part of #82781.
What?
Removes the
Install NVMstep from.github/workflows/performance.yml.Why?
nvm is already installed on GitHub-hosted Ubuntu runners, in
$HOME/.nvm. The step's own output says so (=> nvm is already installed in /home/runner/.nvm, trying to update using git), so on every run it only downloads and re-runs the nvm v0.39.1 install script over the existing copy.Nothing else in the workflow uses the step: the performance CLI loads nvm itself with
source $HOME/.nvm/nvm.sh, which the preinstalled copy provides.Upstream
trunkno longer has this step. It was removed in #82160 ("Performance tests: Build once and shard the suites across parallel CI jobs") as part of a larger rework of the workflow, which isn't ported here.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