4 ms·
Hi HN community, I wanted to share our approach to reduce amount of AI slop PR's and issues in our repo. We enabled "require prior contribution" flag on GH and
by ildari 5mo ago
Hi HN community, I wanted to share our approach to reduce amount of AI slop PR's and issues in our repo. We enabled "require prior contribution" flag on GH and created a CI script that creates a tiny commit co-authored with you, if you pass captcha on our website. Worked really well and we were able to block at least 500 bots in the first week. Sharing a screenshot from cloudflare: https://archestra.ai/hn-comment-cloudflare-challenge-outcomes-do-not-delete.webp https://archestra.ai/hn-comment-cloudflare-challenge-outcome...
- satvikpendem 5mo agoYep, this is similar to some other version control tools like Tangled which has vouching. https://blog.tangled.org/vouching/ https://blog.tangled.org/vouching/
- tln 5mo agoThats a really elegant solution. How does the website trigger the CI script? Through GH rest API?
- ildari 5mo agothank you, yep through the rest API, here is the example: https://github.com/archestra-ai/website/blob/29ebdacbd8a22b91e2b14a9ab136a2c3cfe215af/app/app/api/contributor-onboard/callback/route.ts#L52 https://github.com/archestra-ai/website/blob/29ebdacbd8a22b9...
- halapro 5mo agoWho do you add as a contributor though? Wannabe-contributors? Then they appear in the list of contributors before you even see if they're capable of producing an acceptable PR. Your solution would be great if GitHub would also allow me to whitelist specific users, but unfortunately this still won't block "implementation plans" in comments.