Unresolved
As of 2026-11-17

All 66 cases

Documented case · 2025

HalfSweet

May 20, 2025

UnresolvedNot stated; a week with no response at postingCode access lost / 404

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

The banned account was not his daily account; it was the bot account that handled most API-token access in his workflow. The appeal itself is the story: the appeal form requires an SMS captcha, and the country list does not include +86, so the appeal could not be filed from the suspended account at all. He filed from an alternate account instead, and a week passed with no response. This is the earliest dated instance in this explorer of the +86 SMS barrier blocking an appeal outright, a year and a half before the same wall appears in the October 2026 cases.

The record

Suspended or flagged
May 20, 2025 (post date)
Posted
GitHub Community discussion #159759, May 20, 2025
Ticket / discussion
Discussion #159759; appeal filed from an alt account
Suspected trigger
Not stated; the account was a bot handling most of the API-token access in his workflow, "banned for no reason" in his words
Human reply from GitHub
No response after a week, at posting. Staff closed the discussion as not a support forum
How it ended
Unknown
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 #159759 by HalfSweet; read via search text on 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.