#10 Efficient fork handling

Затворено
отворено пре 3 година од JustAnotherArchivist · 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 added this to the v0.1 milestone пре 3 година
JustAnotherArchivist added the
enhancement
label пре 3 година
JustAnotherArchivist коментирира пре 1 година
Власник
8e83c9b7
Пријавите се да се прикључе у овом разговору.
Нема фазе
No Assignees
1 учесника
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Још нема садржаја.