#10 Efficient fork handling

Fermé
créé il y a 4 ans par JustAnotherArchivist · 1 commentaires

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 a ajouté cela au jalon v0.1 il y a 4 ans
JustAnotherArchivist a ajouté l’étiquette
enhancement
il y a 4 ans
JustAnotherArchivist a commenté il y a 1 an
Propriétaire
8e83c9b7
Connectez-vous pour rejoindre cette conversation.
Aucun jalon
Pas d'assignataires
1 participants
Notifications
Échéance

Aucune échéance n'a été définie.

Dépendances

Ce ticket n'a actuellement pas de dépendance.

Chargement…
Il n'existe pas encore de contenu.