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?

all 12 comments

sorted by: hot top controversial new old
[–] 34 points 2 years ago (1 child)

I’ve forked a couple projects that I just wanted a copy of in case the upstream is deleted.

  • source
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    Can't you clone a previous build? Actual noob here, serious question

  • source
  • parent
  • hideshow 2 child comments
  • [–] 28 points 2 years ago

    They might not have always been empty. Could be that there was a branch for a PR that got merged, so the branch was deleted.

  • source
  • [–] 10 points 2 years ago

    I 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.

  • source
  • [–] 10 points 2 years ago

    If 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

  • source
  • [–] 9 points 2 years ago

    In my case, it's a TODO list. But often, life gets in between and I forget.

  • source
  • [+] 5 points 2 years ago (1 child)
  • [–] 1 point 2 years ago

    Tbf forks should be separated in the repo view on GitHub from repos you've created

  • source