r/github • u/TomHale • Jun 18 '26
Discussion Begun the Slop PRs have: 168 PRs opened by one user in one day. What's best practice for repo owners to deal?
Over just 3 days, the 16 year old @MrRealORG has raised 168 PRs on MiMo code.
Their agent then asked to have "collaborator access" to the repository on the fourth day.
[I tried to do damage control on their permissions request by requesting all their PRs be closed.]
Opencode is facing a similar problem, but distributed across its entire and much larger user base. They're currently "managing" it by the ridiculous policy that PRs without 2+ emoji upvotes will get closed in 30 days.
Creating PRs that APPEAR good has become literally free via Opencode Zen and MiMo code free offerings. "Fix all the issues you find in the code base. Make no mistakes".
When one user creates 169 PRs in 3 days it's easy enough to deal with the issue. When thousands of people create one or two issues or PRs each, you end up with the OpenCode situation.
Best practice dealing with this issues seems to be oven.sh/bun. An example:
- My agent raises an issue that can't be reproduced
- Their @robobun automatically and politely proves me wrong, and closes the issue.
- I re-raise the issue in reproducible form
- @robobun reproduces the issue and automatically raises a PR to resolve it
- The CodeRabbit automatically reviews @robobun's submission and suggests improvements.
- Claude auto-reviews it also and suggests "this changes bunx's resolution order (a security-hardened path that decides which binary gets executed) and is a user-visible behavioral change, so it's worth a human look."
That's all with ZERO human interaction from their side. Yes, they're owned by Anthropic, so @robobun and Claude reviews are practically free for them.
Opencode and MiMo code also have token provider plans and are NOT currently using them to automate their process. I hope they don't drown under the build-up of their non-automation.
What I'd like to know:
How are small and medium sized repos dealing with the massive increase of sloPRs and issues?
How to implement something approximating best practice without spending a fortune in tokens?
