Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[rush] Better support for Git Worktrees

未关闭
#5,633 1 条评论 2 个 reaction 已指派 2 人 在 GitHub 查看

维护者通常 1 天内回复

@dmichon-msft 已经在做这个了。

开始于 2026年2月19日。

评估

这个 Issue 还没有评估数据。

描述

Summary

Currently in a Rush repository, the build cache will be written to common/temp/build-cache unless overridden via the $HOME/.rush-user/settings.json file's buildCacheFolder property, and the pnpm store will be written to common/temp/pnpm-store unless overridden via the RUSH_PNPM_STORE_PATH environment variable.

In a multi-worktree environment, this results in duplication of the build cache and pnpm store, causing considerable excess disk usage.

Repro steps

Create a Git repository and multiple worktrees.

Expected result:
Only one build cache folder and one pnpm store.

Actual result:
One build cache folder and one pnpm store per worktree.

Details

We can address this by having the default computed location for the pnpm-store and the build cache folder be based on the git repository root, rather than the rush json folder, when the former is defined and the user is in a worktree.

We should also improve and standardize the configuration options.

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question Answer
@microsoft/rush globally installed version? 5.168.0
rushVersion from rush.json? 5.168.0
pnpmVersion, npmVersion, or yarnVersion from rush.json? 8.14.0
(if pnpm) useWorkspaces from pnpm-config.json? true
Operating system? *
Would you consider contributing a PR? Yes
Node.js version (node -v)? 22.16.0
主要语言
TypeScript
星标
6.5k
派生
708
平均合并
4 天 13 小时
30 天内合并 PR
62

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/rushstack 的其他 Issue

查看 microsoft/rushstack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。