Codeberg.org on Nostr: nprofile1q…l464c In the background, a fork is actually a copy of the entire ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq8pfm34dcxymy9jy5q0e4aa03y8cw68nwg7gy9udg5msksvva4wgqql464c (nprofile…464c) In the background, a fork is actually a copy of the entire repository itself. On GitHub, forks are actually "embedded" to the repository they were forked from (you might have seen people "forging" commits on GitHub's DMCA repositories, but "they are not connected to any branch".
I'm not sure about how big the repositories you're forking are, but I hope this background might help you make a more educated decision. ~n
I'm not sure about how big the repositories you're forking are, but I hope this background might help you make a more educated decision. ~n