Welcome to the Eternal September of open source. Here's what we plan to do for maintainers.

As contribution friction drops, maintainers are adapting with new trust signals, triage approaches, and community-led solutions.

The GitHub Blog
@bagder Conspicuously missing is Microsoft's complicity in creating the problem they're now saying they'll solve.
@bagder they don't seem to have many ideas but at least they're acknowledging the problem they helped create
@bagder the biggest thing github is doing to address the slop problem is to crater their uptime so that people start seriously considering moving to other forges
@bagder I would’ve loved to see a stronger opinion on community built systems like vouch, which is a far better first step to managing contributions than a delete button for pull requests.

@bagder

we and our 121764873 agents take the health of our maintainers very seriously.

LLMs generate too much noise so the best solution our local LLM has invented is (tadam) :

pinned comments in issues.

@bagder "It’s the sheer volume of contributions."

No, it's not. It is the AI Slop you help create. But oh well.

@bagder scale down drastically their push on AI? Allow maintainers to disable Copilot entirely on their repos? 😈

@bagder

"We all know it's the Eternal September's fault"

@bagder pinned comments and enforced quiet time sound good but I can't help but think "these should've been here ages ago!"

Also, not sure how this addresses the issue at hand lol.

@bagder it's so laughable, so cringe that they brag about "pull request diff performances". These days github is barely usable anymore for patch reviews. The pr review tool is broken and slow. The two distinct versions they offer are in competition which one is more broken. Half the patch context links they have never get you to the right place, and they collapse anything by default that's larger than a couple of dozens of lines. So many clicks for everything. And the slow UI reaction times...

@pid_eins @bagder yes. the best thing they could do for maintainers is fix the review tool and stop messing with it.

also, if they could stop pushing copilot everywhere, that would also be nice.

@pid_eins @bagder Yeah, sometimes in the last 5 years I just gave up on reviewing *anything* on Github and just shallow clone.

It still generally outperforms waiting their UI to stop screwing around.

@pid_eins @bagder i remember having to review a massive pr. it was lagging everywhere. it got to a point where i wrote a basic neovim script to review PRs. Take it. It is buried in my dotfiles: https://github.com/MatusGuy/dotfiles/blob/master/dot_config%2Fnvim%2Fgithub_review.lua

the only caveats are: you must have gh and jq installed; i think it only works for linux; you cant do multiline reviews (because i didnt implement it); oh! and you need to know how to use vim :(

@bagder I really hate this blog post, it's about 50% fluff talking about how AI ruins open source projects, and then a list of random minor performance improvements that github wants to pretend will "help solve" the AI slop problem

the only thing even approaching a useful tool from them here is temporary interaction limits for certain users, the rest feels like corporate PR trying to sell me on github caring somehow
@bagder i still think AI code review tools can help tho.
@bagder

Alternate title: "Here's what we plan to do to maintainers"