#10 Efficient fork handling

Suljettu
4 vuotta sitten avasi JustAnotherArchivist · 1 kommenttia

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 lisäsi tämän merkkipaaluun v0.1 4 vuotta sitten
JustAnotherArchivist added the
enhancement
label 4 vuotta sitten
8e83c9b7
JustAnotherArchivist sulki tämän ongelman 1 vuosi sitten
Sign in to join this conversation.
Ei merkkipaalua
Ei käsittelijää
1 osallistujaa
Ilmoitukset
Määräpäivä

Määräpäivää ei asetettu.

Riippuvuudet

This issue currently doesn't have any dependencies.

Ladataan…
Sisältöä ei vielä ole.