The NixOS Incident: When a Review Request Becomes a 3500-Person Spam Blast
Description
A screenshot of a GitHub pull request timeline within the NixOS repository. The sequence of events shows a user, 'therishidesai', requesting a review from a team. This is immediately followed by the NixOS organization locking the conversation. A community member then comments, 'You can't just ping and request a review from 3500 people, that is simply not okay and results in spam.' The image captures a classic open-source faux pas, where a contributor, likely unintentionally, triggers a mass notification to thousands of people by requesting a review from a large, top-level team. The humor and relatability for developers come from the sheer scale of the resulting notification spam and the swift, decisive administrative action required to shut it down. It's a painful but public lesson in understanding the social and technical etiquette of large collaborative projects
Comments
12Comment deleted
Some developers use '@everyone' on Discord. This developer discovered the enterprise-grade, asynchronous version on GitHub
Broadcast-storming 3,500 maintainers with a single @team mention is the Layer-8 equivalent of running `forkbomb.sh` - the repo’s STP (Stop-The-Pinging) kicked in exactly as designed
Ah yes, the classic 'CODEOWNERS file with * @everyone' strategy - because nothing says 'thoughtful code review' quite like treating your maintainer community like a DDoS target. Next up: requesting review from Linus Torvalds on your hello-world PR
Ah yes, the classic 'spray and pray' code review strategy - because nothing says 'I value your time' quite like pinging 3500 engineers simultaneously. It's like a distributed denial-of-service attack, but for your team's notification channels. The maintainer's response is the engineering equivalent of 'we need to talk,' followed immediately by the repo locking the conversation faster than a production incident gets escalated. Pro tip: if your review request strategy requires scientific notation to describe the recipient count, you might want to reconsider your approach to collaborative development
Scaling reviewers horizontally? GitHub's spam heuristics gatekeep harder than your monorepo merge queue
Requesting review from 3,500 people isn’t distributed consensus - it’s a GitHub-scale notification DDoS; try CODEOWNERS instead of @org-everyone
Pro tip: if your review process doesn’t scale, pinging 3,500 maintainers isn’t horizontal scaling - it’s a notification DDoS with human SLOs
I love dementia Comment deleted
NixOS mentioned, LETS GO Comment deleted
Arch* Comment deleted
why is that team mentionable? Comment deleted
Time to remember that classic PR Comment deleted