this post was submitted on 01 Oct 2023
29 points (93.9% liked)

Git

2899 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
jnovinger@programming.dev
canpolat@programming.dev
29
What is the point of empty forks? (programming.dev)
submitted 1 year ago by sirdorius@programming.dev to c/git@programming.dev
11 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] Luci@lemmy.ca 10 points 1 year 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.