#10 Efficient fork handling

Chiuso
aperto 4 anni fa da JustAnotherArchivist · 1 commenti

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 aggiunta alle pietre miliari v0.1 4 anni fa
JustAnotherArchivist added the
enhancement
label 4 anni fa
JustAnotherArchivist 1 anno fa ha commentato
Proprietario
8e83c9b7
JustAnotherArchivist closed this issue 1 anno fa
Effettua l'accesso per partecipare alla conversazione.
Nessuna milestone
Nessuna assegnatario
1 Partecipanti
Notifiche
Data di scadenza

Nessuna data di scadenza impostata.

Dipendenze

Questo problema attualmente non ha alcuna dipendenza.

Caricamento…
Non ci sono ancora contenuti.