HN

Need help?
<- Back
PR spam today looks like email spam in the early 2000s

PR spam today looks like email spam in the early 2000s

dakshgupta

Comments (63)

  • Retr0id
    Maybe we should cut out the middle-man and make it easy for people to donate token credits to open-source projects, and let the maintainers decide how to use them.
  • j2kun
    In my main project we added a new requirement that all new contributors meet a maintainer in a non-textual format before their first PR is merged. Seems to work well for a small project.
  • andix
    I see one big difference: with email it was always about sender reputation based on email servers (IPs), maybe about domains. But never about individual users. It's the organizations running the email server, who make sure users behave. So they don't get blacklisted and lose sending privileges for hundreds or thousands of users.For PRs/issues this is not applicable.
  • anon
    undefined
  • guidoiaquinti
    GitHub just recently added configurable PR limits for maintainers to help partially address this problem: https://github.blog/open-source/maintainers/how-pull-request...
  • othmanosx
    100% agree, as a web dev, my team and I are shipping code like crazy, I just merged a 20k PR today and we're just starting.Even if it's all AI code, we still need to read it and understand it before we ship it to prod with millions of users.Thanks to AI Agents, we now have either:- too many small PRs (good luck managing them), or- huge PRs (try not to keep them sitting for long)I've been through this and learned a few things shipping AI code as a software engineer. I've gathered all my pain points in a project I built.Pyor ReviewYou can check it out here: https://news.ycombinator.com/item?id=48621549we all know that Github sucks, so Pyor for me is now the place where I manage my open PRs easily, and review my teammates' code faster and easier.I was able to get PRs merged 3X faster, without the frustration that comes with interacting with GitHub's UI or the AI summary tools that add even more bloat and more text to read.I'm still developing it so I'm open to feedback.
  • janalsncm
    I understand this is a general problem in OSS, but I also hope the irony isn’t lost that this article is specifically complaining about AI slop PRs to the Open Claw repo.If the maintainers are that tired of it, they should update OpenClaw to prevent it from submitting PRs to their repo.
  • benj111
    Wait. So to combat AI spam there's AI agents to prevent it?Why can the anti spam agents not just do the work directly???
  • fecal_henge
    Can I ask what the motive is to create agents to do this? Where is the profit?
  • aniokono
    What are the best solutions to this issue?
  • giancarlostoro
    Does github not have rulesets for who can even try to do a PR? I would lockdown my repositories if I didn't want any PR slop.
  • runarberg
    AI agents who review the slop created by other AI agents is not the answer here.I much prefer a blanket ban on PRs and issues created by AI agents (which is what I personally do for my repos; so far I have closed one[1]). In fact I would love a github alternative which considers AI contributions to be a breach of their terms of use and ban any people who let AI agents loose on their platform.1: https://github.com/runarberg/markdown-it-math/pull/48#issuec...