How can such a wrong answer get so many points? Clones and forge forks are unrelated. First, GitHub or GitLab cannot and could not link clones together without analyzing the remotes of each clone.
FFS it’s a tech community…
Comment on Data from deleted GitHub repos may not really be deleted
Mubelotix@jlai.lu 3 months agoYes they exist. It’s called a clone
best_username_ever@sh.itjust.works 3 months ago
Mubelotix@jlai.lu 3 months ago
Because you are the one being wrong. Github and others only provide a nice interface around clones. That’s all there is, and it doesn’t matter much
arcuru@lemmy.world 3 months ago
The article is specifically about how GitHub forks are not the same as a git clone. A clone isn’t accessible from the upstream without the upstream pulling the changes, but this vulnerability points out that a fork on GitHub is accessible from the upstream without a pull, even if the fork is private.
It’s because GitHub under the hood doesn’t actually do a real clone so that they can save on disk usage.
Mubelotix@jlai.lu 3 months ago
You actually can’t turn a fork private on github