I am (idly) wondering if Github stores a full copy of a
.git folder when a user forks a repository. A friend of mine postulated that surely there is some smarter implementation at work here that avoids replicating the full history of commits in a fork, but I believe (Occam’s razor) that Github would just take the disk usage hit and copy the
.git folder verbatim, altering the
remote aspects of the (user) repository to point to the original repo.
If anyone has some inside understanding of the implementation I would love to know how Github implements it.