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?

  • darklamer@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    arrow-down
    5
    ·
    2 days ago

    What do you think that people should be doing instead? What is your own workflow when contributing to projects on GitHub?

    • plm00@lemmy.ml
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      2 days ago

      OP is referring specifically to those who don’t contribute but fork anyway.

      • darklamer@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        arrow-down
        5
        ·
        2 days ago

        How could anyone possibly know that those people don’t contribute? Why would anyone even try finding that information?

        • Eager Eagle@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          edit-2
          2 days ago

          you compare the number of forks with the number of contributors

          forks are almost always higher, not just higher, but often by a factor of 10

          • tyler@programming.dev
            link
            fedilink
            arrow-up
            3
            ·
            1 day ago

            that is just people that got their commits in, it doesn’t mean that others didn’t try to contribute, but failed.

    • aloofPenguin@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      2 days ago

      I’d do a PR. Although I would understand forking if the project maintainers wouldn’t merge a PR. (or create an issue (for the fix/ addition) if the README says that it’s an option)

      • cecilkorik@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 day ago

        So while you’re working on your PR, where do you push your commits? If you don’t fork, you can’t push them to Github. You don’t have access to the repo you’re making a PR for. That’s exactly why people fork.

        Of course you could just NOT push any commits, but then your commits only exist locally on your development machine, and if you have a hardware failure you’ve lost them, defeating the point of a distributed version control system. Or you could push them to another computer you have access to, but Github lets you push to your own free account for free, so most people would rather just do that. Which they do. By creating a fork.

        Maybe it’s okay if you’re only creating a small PR with a single commit or two. But for more extensive development, anyone reasonable is going to create a fork so they have somewhere to store their work until it’s ready. Once/If the PR is merged, the fork is abandoned as it’s no longer needed. But that’s why they exist.

      • tyler@programming.dev
        link
        fedilink
        arrow-up
        4
        ·
        1 day ago

        A PR requires push access… That’s why you create a fork… So you can create a PR from your fork.