3 ms·

https://www.digitalocean.com/community/tutorials/hacktoberfest-contributor-s-guide-how-to-find-and-contribute-to-open-source-projects https://www.digitalocean.c

• deleted 6y ago
  [deleted]
• stickupkid 6y ago
  This isn't highlighted high enough, and the lack of what makes a good PR that shows new contributors the best way forward isn't shown enough. Yet I standby my statement, you're not blameless here.
  • neom 6y ago
    Would you be willing to share what you'd recommend? I don't work at DigitalOcean but I know a few of the folks working on hacktoberfesst and I'm happy to forward our suggestions. je at h4x dot club.
    • cmeacham98 6y ago
      Only count pull requests that are merged. Make this fact obvious on the hacktoberfest website so contributors know spamming PRs will not help them. I know the standard answer to this is that it would exclude some repos (ex: node) that merge PRs manually via git. However: 1. You already are excluding every open source project not on GitHub, so this is a really weak point. 2. I am extremely confident trading off not including a very small subset of repos for removing the incentive to spam bad PRs is a worthwhile trade.