#10 Efficient fork handling

Slēgta
JustAnotherArchivist atvēra pirms 4 gadiem · 1 komentāri

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 pievienoja atskaites punktu v0.1 pirms 4 gadiem
JustAnotherArchivist pievienoja etiķeti
enhancement
pirms 4 gadiem
JustAnotherArchivist komentēja pirms 1 gada
Īpašnieks
8e83c9b7
JustAnotherArchivist slēdza šo problēmu pirms 1 gada
Pierakstieties, lai pievienotos šai sarunai.
Nav atskaites punktu
Nav atbildīgo
1 dalībnieki
Paziņojumi
Izpildes termiņš

Izpildes termiņš nav uzstādīts.

Atkarības

Šai problēmai pagaidām nav nevienas atkarības.

Notiek ielāde…
Vēl nav satura.