Documented case · 2022
seanpm2001 (Sean Poole)
Flagged Jul 19, 2022; restored Aug 26, 2022
Secondary source
The details here rest on another site's summary of the case, not on the account holder's own post.
Flagged on July 19, 2022 and hidden: profile and repos gone from public view. He appealed the same day, again on July 22, and heard nothing until August 4. What arrived was not an explanation but a toll: delete roughly a thousand organisations, by hand, because GitHub would not do it, and then the account could be reviewed. He paid it, twelve days of manual deletion. The account was restored overnight on August 26, thirty-eight days after the flag, without any reply to his final appeal and without any reason for the flag ever being communicated. The demand is the detail that has no parallel elsewhere in this explorer: the price of a review was the destruction of part of the work under review.
The record
- Suspended or flagged
- Flagged July 19, 2022
- Posted
- His own day-by-day case log (a GitHub repo), July to August 2022
- Ticket / discussion
- Ticket #1731581 (the organisation-deletion exchange); three appeals: July 19, July 22, August 19
- Suspected trigger
- The automated system marked the account as spam, per the summary of his log. No reason for the original flag was ever communicated to him
- Human reply from GitHub
- The first reply came on day 17, August 4, and it was a precondition, not a review (see resolution). support@github.com was blocked
- How it ended
- Restored overnight on August 26, 2022, with no direct response to his third appeal. The precondition: GitHub's August 4 reply required him to delete all of the roughly 1,000 organisations his account owned before it would review the flag. GitHub refused to delete them itself, so he deleted them manually from August 5 to 16, twelve days of deletions, to qualify for a review of a flag whose reason was never stated
- Duration
- 1 to 3 months
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
His own case log, kept as a GitHub repo; read in research through a secondary summary (DeepWiki) of the repo's timeline pages, November 17, 2026.
Details read through a secondary summary of his own primary log, which is linked here.
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.