Documented case · 2018
movermeyer (Michael)
Mar 2018
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
He built a bot that mended broken badges by opening pull requests on strangers' repos, and GitHub suspended and flagged the account: profile hidden, every PR, issue, and repo gone, his Pages site offline. Then the part that dates the case: GitHub replied quickly, named the behaviour it objected to, and unflagged him when he promised to stop. Eight years before the AI-agent cluster of 2026, the same trigger, automated activity at machine speed, produced a conversation instead of a corridor. Included as the baseline for how much the process changed.
The record
- Suspended or flagged
- March 2018 (before this explorer's 2020 starting point; the earliest bot precedent found)
- Posted
- His blog, March 8, 2018
- Ticket / discussion
- None published
- Suspected trigger
- GitHub-stated: unsolicited automated pull requests were spam. His bot auto-submitted PRs to fix broken badges in other projects' readmes
- Human reply from GitHub
- Yes: GitHub replied quickly and said what the problem was
- How it ended
- Unflagged after he promised to stop the automated PRs; all of his PRs returned
- Duration
- Under 1 month
Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.
Sources
First-hand post by movermeyer, movermeyer.com, March 8, 2018; checked November 17, 2026.
Predates the explorer's main range; included as the earliest documented bot-flag precedent.
This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.