I see this so often, but I don’t understand it. Some people just fork a huge amount of repos and never commit anything to them. What’s the point? Are they trying to pad their profile for potential employers or what?
It just clutters your active repos. Personally, I just remove forks once my PR gets merged upstream. And I only fork when I’m ready to push a commit.
Is there something I’m missing?
sim642 ( @sim642@lemm.ee ) 25•9 months agoThey might not have always been empty. Could be that there was a branch for a PR that got merged, so the branch was deleted.
Gamma ( @GammaGames@beehaw.org ) English13•9 months agoIf it’s licensed well then it means the user has a backup of the project if it ever gets removed or they change the license. I don’t know if that’s the actual reason though, just a guess
onlinepersona ( @onlinepersona@programming.dev ) English9•9 months agoIn my case, it’s a TODO list. But often, life gets in between and I forget.
Luci ( @Luci@lemmy.ca ) 7•9 months agoI fork the version I deploy in prod across multiple machines. I find it makes my life easier and I never need to learn any cli other than git clone and git pull.
Sigmatics ( @Sigmatics@lemmy.ca ) 1•7 months agoTbf forks should be separated in the repo view on GitHub from repos you’ve created