Hacker News new | ask | show | jobs
by altairprime 3 hours ago
Anywhere you accept unvouched pull requests will end up being spammed. You might find some respite at other sites, but whether you stay or go: you’re better off disabling pull requests on your projects for everyone but you, and then using discussions (like ghostty) where people petition to work on a feature; if they can convince you it’s a feature that’s valuable to you, then you can pull from their branch (like Linus) and merge them yourself when ready. That will halt the PRs and give you a much reduced pool of noise, as most fly-by-night sloppers won’t be interested in spending the extra tokens on both code and discussion. (You’ll still get entitled human beings who demand you add and maintain their solution to their needs, but that’s much easier to sift out and discard once people have to discuss their needs in written words rather than code.)
1 comments

Really surprised that this is not the first thing everyone does on their repositories.

I am not a celebrity on github and not even agents bother with my repositories, however, even before the bot pull requests/issues, I always made sure to enable only the things I felt I would want to use and provide a way for someone to reach out in case I was expecting collaboration/feedback.

I realized that anyone can create a PR to upstream, when I accidentally did so using the github web UI on mobile. Felt embarrassed and immediately closed it. But, then it made sense that why people were frustrated with this sort of thing happening to big repositories.