Documented case · 2026
trevtheballer (Trever Hatch)
Suspended Oct 14, 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
Suspended without warning on October 14, 2026. The account's work was a private game project, and the activity he believes tripped the flag was his own AI tooling working on it: Google Jules and Cursor agents opening many pull requests and running heavy CI in a short window. He states the activity was legitimate and his, and his post is largely an offer to change how he works, fewer and larger pull requests, much lower CI volume, no bulk automation, if GitHub will tell him which activity caused it.
The record
- Suspended or flagged
- October 14, 2026, about 16:25 UTC
- Posted
- GitHub Community discussion #210477, October 2026
- Ticket / discussion
- Discussion #210477; no ticket number published
- Suspected trigger
- Heavy automated activity on a private game project: Google Jules and Cursor agents opened many pull requests and ran a lot of CI in a short time (his inference; all of the activity was his own, on his own project)
- Human reply from GitHub
- Not stated
- How it ended
- Unresolved at posting. He offered to throttle the automation: fewer, larger PRs, much lower CI, no bulk automation, and asked which activity caused the suspension
- Duration
- Not stated
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 GitHub Community discussion #210477 by trevtheballer; opened and checked November 17, 2026.
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.