What would you want from a forge?

你对代码托管平台（Forge）有什么期待？

17 What would you want from a forge? ☶ ask design vcs authored by runxiyu 8 hours ago | 27 comments 17 你对代码托管平台（Forge）有什么期待？ ☶ 提问设计版本控制系统作者：runxiyu 8小时前 | 27条评论

(This is more or less open ended, but sorta directed to users of Jujutsu and other version control systems. However, if you have a workflow with pure Git that isn’t covered by many major forges, I’d appreciate hearing them too!) （这个问题比较开放，但主要是针对 Jujutsu 和其他版本控制系统的用户。不过，如果你在使用纯 Git 时有某种工作流是目前主流托管平台无法覆盖的，我也很乐意听听！）

I’m referring to features related to version control and the presentation/behavior of repositories itself, rather than things like SPA/JS vs server-rendered HTML, etc. 我所指的主要是与版本控制相关的功能，以及仓库本身的呈现方式或行为，而不是像 SPA/JS 与服务端渲染 HTML 这种技术选型问题。

There have been many ideas in this space, such as Tangled, GitHub’s stacked PRs, forgefed, etc., but I haven’t found a place where people really voice their opinions and discuss on the design itself. 在这个领域已经出现了很多构想，比如 Tangled、GitHub 的堆叠式 PR（stacked PRs）、forgefed 等，但我还没找到一个地方，能让人们真正表达观点并深入探讨其设计本身。

While stacked PRs/MRs, alternative collaboration models, etc., are definitely on-topic, I’ve found almost no discussion on, e.g., the presentation of tags/commits/tree/blobs themselves, which seem to be largely uniform across forges other than minor formatting differences. 虽然堆叠式 PR/MR、替代性协作模型等话题绝对在讨论范围内，但我几乎没看到关于标签（tags）、提交（commits）、树（tree）或数据块（blobs）本身呈现方式的讨论。除了细微的格式差异外，这些元素在各大托管平台上的表现似乎高度统一。