#10 Efficient fork handling

已關閉
JustAnotherArchivist4 年之前建立 · 1 條評論

This should include handling situations where the fork is not directly linkable to the original repository via e.g. GitHub’s “forked from” information, e.g. when someone forked a GitHub project onto GitLab or some other platform.

On Git, a repository can be uniquely identified with the root commit’s hash. However, repositories can have multiple root commits via orphan branches and even on a single branch when merging independent histories.

Related: #1

This should include handling situations where the fork is not directly linkable to the original repository via e.g. GitHub's "forked from" information, e.g. when someone forked a GitHub project onto GitLab or some other platform. On Git, a repository can be uniquely identified with the root commit's hash. However, repositories can have multiple root commits via orphan branches and even on a single branch when merging independent histories. Related: #1
JustAnotherArchivist 新增至v0.1 里程碑 4 年之前
JustAnotherArchivist added the
enhancement
label 4 年之前
8e83c9b7
登入 才能加入這對話。
未選擇里程碑
No Assignees
1 參與者
訊息
截止日期

未設定截止日期。

Dependencies

This issue currently doesn't have any dependencies.

Loading…
尚未有任何內容