4 ms·
> If someone malicious can make commits to your repo, you have a much worse problem than a possible hash collision. This is exactly how GitHub works though: al
by haileys 4y ago
> If someone malicious can make commits to your repo, you have a much worse problem than a possible hash collision.
This is exactly how GitHub works though: all repositories in a fork network share a single underlying repository, only the ref namespaces are separated.
- wildfire 4y agoI am skeptical that is actually the case though, there are so many use-cases where you have to think through the consequences too carefully: - what happens when the source repository rewrites all the commits (to remove one); should the forks also be re-written? - what happens when the source repository disappears? _All_ of the problems go away when you actually do a "git clone" of the source repository and have your own objects. More storage, yes, but way fewer corner cases to think through.