githubIssues.queries is applied to auto-detected linked worktrees
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, typescript, vscode
调研方向
Start in the issue state manager where githubIssues.queries is read, and check the extension manifest for its resource scope. Trace how the query list is reused across detected repositories and how an empty list falls back to the default. Done means each worktree gets its own configured queries, including an explicit empty list.
由索引模型根据 Issue 内容生成。
描述
- Extension version: 0.172.0
- VSCode Version: Not recorded
- OS: macOS (version not recorded)
- Repository Clone Configuration (single repository/fork of an upstream repository): One main worktree with linked worktrees for the same repository
- GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): Not recorded
Steps to Reproduce:
- Open the main worktree in VS Code.
- Keep
"git.detectWorktrees": trueso linked worktrees are detected and shown in Source Control. - Configure a custom
githubIssues.queriesvalue for the main worktree. - Open the GitHub Issues view and refresh it.
Actual:
The configured query categories are also applied to the auto-detected linked worktrees. I cannot configure the queries for the main worktree without also applying them to those linked worktrees.
Setting githubIssues.queries to an empty array does not disable the queries; the extension replaces the empty array with its default query.
Expected:
githubIssues.queries should be resolved per repository/worktree, so the main worktree can use its configured queries while linked worktrees can use their own configuration or no query categories. An explicit empty array should remain empty.
This should work while "git.detectWorktrees": true remains enabled, since I want the linked worktrees to continue appearing in Source Control.
Additional context:
The extension manifest declares githubIssues.queries as a resource-scoped setting, but the issue state manager appears to read it without a resource and reuse the resulting query list for all detected repositories. It also replaces an empty query list with the default query.
- 主要语言
- TypeScript
- 星标
- 2.6k
- 派生
- 807
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 70
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/vscode-pull-request-github 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
microsoft/vscode-pull-request-github#9143 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
microsoft/vscode-pull-request-github#9072 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 53/100
microsoft/vscode-pull-request-github#9142 · 1 条评论 ·
维护者通常 1 天内回复
-
githubIssues.queries is applied to auto-detected linked worktrees可能已有人在做 @alexr00 于 1 天前认领。 未关闭
microsoft/vscode-pull-request-github#9140 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 56/100
microsoft/vscode-pull-request-github#9125 ·
维护者通常 1 天内回复
查看 microsoft/vscode-pull-request-github 的全部 Issue
相似的 Issue
-
area: triage theme: undefined
难度 2/5 1-3 小时 新手友好度 85/100
jhipster/generator-jhipster#35895 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
paperclipai/paperclip#18396 ·
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 82/100
lingdojo/kana-dojo#33380 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
chore other
难度 2/5 1-3 小时 新手友好度 82/100
alastair-smith/card-games#342 ·
维护者通常 1 天内回复