Urgent: GitHub Account Suspended – Development Work Blocked

[fangliquan33]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

@github-staff
Hi GitHub Community,

My GitHub account @fangliquanflq was suspended on 25/09/2026. I have already opened Support ticket #4792736, but I have not received a response yet.

I sincerely apologize for posting this here, as I know this may not be the primary place for support requests. However, my daily work is completely blocked right now, which is why I am reaching out here in hopes of finding some guidance or help.

I have invested a great deal of energy into the open-source community, particularly participating in the development of hermes-agent. I suspect my account might have been flagged and suspended because I used an AI tool integrated with the GitHub CLI (gh cli) to automate tasks, such as searching for duplicate Pull Requests and automatically initiating PRs.

Could someone please help look into my case to see if this was indeed the reason? I have already disabled all automated tasks and I promise to strictly limit and use AI tools with extreme caution moving forward.

If anyone could spare some time to help unban or review my account, I would be incredibly grateful. Thank you so much for your time and help!

Any guidance would be greatly appreciated.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ezeanyimhenry1]

Hello @github-staff

Please, I am in this same situation. My account @ezeanyimhenry was suspended over a month ago. I reached out to support (ticket ID: #4726519) on 3rd September, but I haven't received any response till date.

Please I also have a lot of contributions and it has really affected my work for the past month.

I humbly request help with this, I'd do my best to be more careful and go through your terms and guidelines to avoid any violations.

[BradPerbs]

Only GitHub Support can review a suspension, and nobody here can see or change it. Your ticket #4792736 is the right channel, and a reply there keeps it in the queue. Don't open duplicate tickets, since that can reset its place. If automated bulk PR creation was the cause, the Acceptable Use Policies section on automated activity is worth quoting in your reply along with what you've disabled. Also consider editing your email address out of this post, since it's public.

[fangliquan33]

@BradPerbs
Thank you for the guidance! I have removed my email address from the post.

The reason I reached out here is that I am currently unable to view the status or progress of ticket #4792736. Since my daily work is completely blocked, I would be extremely grateful if my ticket could be expedited or looked into. Thank you again!

[flwb-li]

I'm in the same situation as you. Keep following up on that work order and remain patient. So far, I haven't received a reply for three weeks. Maybe I'll have to wait even longer.

[ezeanyimhenry1]

I haven't received any reply for over a month.

[AnselmD]

Pinging @teknium1 (maintainer of hermes-agent, the project named in this thread) - not to derail this request, but because this thread documents a pattern that now has concrete numbers from that project's ecosystem.
A maintainer-side data point from the hermes-agent ecosystem:

• The contributor behind the account named above (@fangliquanflq - suspended on 25/09/2026, as the thread author describes it, after automating duplicate-PR search and PR filing via gh cli) was one of the most active contributors in NousResearch/hermes-agent: 1,088 pull requests over roughly five months, 21 merged, 605 still open today.
• The last public action on that account was opening fix(web): allow free Portal accounts to use managed Fast Search NousResearch/hermes-agent#122404 on 25/09 at 06:54 UTC, the day the account went silent. Six days later, a maintainer closed that PR and landed the work on main via fix(web): free managed fast search reaches registered Nous accounts (guests keep the keyless ring) NousResearch/hermes-agent#130660, closing it with explicit credit ("Supersedes #122404 (earliest submitter) and #122967, both closed with credit"). That handling is exactly right - and it is manual goodwill. There is no process behind it: a frozen author cannot rebase the 605 open PRs, cannot respond to reviews, cannot fix CI, and the platform offers no adoption or handover mechanism for suspended accounts.
• The same suspension also hit third parties directly, myself included. The fix pull request attached to a cost-accuracy issue I filed myself ([Bug]: Hermes cost estimate undercounts real OpenRouter billing by up to 4.9× on long-context calls NousResearch/hermes-agent#109976) was authored by that same account - and on 28/09 that PR, its issue view, and the author's profile all returned 404 at the same time (we measured this while re-checking our own ticket). It reappeared on 01/10 with no explanation or restoration notice that we could observe, and the author's public activity has been silent ever since. Third parties lose access to work attached to their own tickets with no warning, no notification, and no way to plan around it.
• This is not an isolated case, and the causes are not uniform. Five further suspended-account discussions appeared in this community in October alone: Another machine account suspended after automation activity... #209306 (01/10 - a dedicated automation account for the hermes-agent ecosystem, suspended within a day of activity, self-reported by its operator), GitHub account suspended since September 3 — Support ticket #4726519 still unanswered #209416 (suspended since 03/09, support ticket #4726519 unanswered for over a month), Account Suspended for 15 Days - Need Help Escalating Ticket #4791216 #209814 (15 days suspended after an accidentally leaked access token, ticket #4791216), Open source maintainer suspended 8 days with no reason, only automated replies to every ticket #209418 (an open-source maintainer, 8 days, no stated reason), Request for Guidance on Suspended GitHub Account – Reinstatement Request Awaiting Response #209886 (09/10). The causes differ - what repeats is the shape: instant locks and appeals that sit unanswered for weeks to months - and in a repository moving at hermes-agent's pace (over 2,000 pull requests merged in the two weeks before its latest release), unreachable authors' work goes stale in days.
  The pattern from an agent-platform perspective: the behavior this thread's author self-describes (AI-assisted duplicate detection and PR filing via gh cli) is the normal operating mode of agent-platform ecosystems. GitHub currently offers no declared lane for contributor-side automation, no graduated warning before enforcement, and no rest state for frozen accounts (write-locked on the flagged actions, but still able to answer reviews or rebase). Instant enforcement plus months-long appeal latency plus unhandoff-able in-flight work quietly destroys contributor output.
  Ask, deliberately small:

1. @teknium1 - would hermes-agent consider a short contributor automation-hygiene note (what not to automate, volume limits, keeping PRs small and rebaseable), so the project's user base - the class most exposed to this dragnet - has documented guidance?
2. For anyone with a channel to GitHub staff: the ticket latencies above plus this thread may be worth forwarding. The public surface here is documented as a dead end ("Only GitHub Support can review a suspension, and nobody here can see or change it").