microsoft / microsoft/vscode-pull-request-github
Files in pull request opened by absolute path; not considered the same file as the file within the workspace
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 2.6k
- 派生
- 795
- 平均合并
- 1 天 4 小时
- 30 天内合并 PR
- 46
描述
Type: Bug
I have a PR checked out in the root directory of my VS code workspace. Sometimes (I'm not sure exactly the conditions for this happening, but it happens frequently for me), PR comments do not appear when I open the corresponding file.
When this happens, if I open the file from the "GitHub Pull Requests" sidebar, a second editor view appears. In this second editor view, the path to the file is displayed as an absolute path (home > me > workspace > path > file) whereas the path in the first editor view is displayed relative to the workspace (path > file). VS code appears to treat them as two completely separate files, and the PR comments appear only in the absolute-path view of the file.
There are no symlinks or other obvious complicating factors in the path. Running code path/file or code $PWD/path/file from the integrated terminal open the relative-path view.
Extension version: 0.106.0
VS Code version: Code 1.98.0 (Universal) (6609ac3d66f4eade5cf376d1cb76f13985724bcb, 2025-03-04T21:06:18.612Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux x64 6.10.11-1rodete2-amd64
System Info
| Item | Value |
|---|---|
| CPUs | Apple M1 Pro (10 x 2400) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 3, 2, 3 |
| Memory (System) | 32.00GB (3.19GB free) |
| Process Argv | --crash-reporter-id a2b1566c-976d-4a22-b919-31335ae2a712 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: ct |
| OS | Linux x64 6.10.11-1rodete2-amd64 |
| CPUs | AMD EPYC 7B13 (128 x 0) |
| Memory (System) | 236.11GB (219.44GB free) |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
5a9hg449:31230677
hdaa2157:31222309
copilot_t_ci:31222730
f5992895:31254866
jda6j935:31233686
pythoneinst12cf:31257680
4d2d8976:31256800
563cc122:31253270
31787653:31256342
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未指定文件或测试。在包含已检出 pull request 的 VS Code 工作区中重现该问题,比较从 GitHub Pull Requests 侧边栏打开的文件与从终端打开的文件,并跟踪它们的路径如何与 PR 评论关联。完成标准是两种打开路径都解析到同一个工作区文件,并且评论出现在正常的编辑器视图中。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, typescript, vscode
- 领域
- developer-experience, devtools
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100