Microsoft/vscode

SCM - go to next/previous change (Alt-F5) should cycle between files

Open

#111,596 创建于 2020年12月1日

在 GitHub 查看
 (4 评论) (35 反应) (1 负责人)TypeScript (74,848 star) (10,221 fork)batch import
feature-requesthelp wantedscm

描述

In #18059, @Tyriar requested that this work like "go to next problem" (F8), but the way it's been implemented there's a crucial difference - upon reaching the end of the file, it goes back to the top, rather than the next changed file! This means, for example, that when reviewing changes prior to staging, I end up running git diff in a terminal to avoid a lot of fiddly mouse clicking. Any other power user surely does the same. This is a shame, since VScode has replaced every other one of my everyday uses of git.

I see no reason anyone would be opposed to this change.

贡献者指南

技术栈
typescript
领域
desktopdeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
TypeScriptVS Code extension APIGit
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
The issue requests that Alt F5 (go to next change) should cycle across files, similar to how F8 cycles through problems. The prior discussion in issue #18059 and the current implementation should be studied. The SCM extension in VS Code handles change tracking; the relevant code likely resides in extensions/git or src/vs/workbench/contrib/scm. To implement, one could examine how 'go to next problem' works (likely in problems extension) and adapt it to SCM changes. The assigned developer may have left comments; check the issue for any linked PRs or further clarification.