Programming

23307 readers

267 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Why do some people fork repos but make no changes to them? (lemmy.world)

submitted 3 days ago by aloofPenguin@lemmy.world to c/programming@programming.dev

46 comments fedilink hide all child comments

I've seen some projects on GitHub (howdy being one of them that came to mind) where there are forks, but when I check the forks out they are either unchanged, or are behind by a few commits. I was wondering why this would happen. It couldn't be for archival purposes, could it?

you are viewing a single comment's thread
view the rest of the comments

[–] who@feddit.org 19 points 3 days ago* (last edited 3 days ago)

When looking for activity, are you only checking for the number of commits ahead/behind, or are you also checking for new branches?

A common workflow is to fork a project, clone it locally, add some work on a new branch, push it to your fork, and then create a pull request from the new branch. None of that will add commits to the default branch.