Work account @auto-use suspended since 2 July — Support ticket #4529119 unanswered for 10+ weeks #208053
🏷️ Discussion TypeQuestion 💬 Feature/Topic AreaOther BodyHi all, I know the Community can't reinstate accounts or escalate tickets, so I'm asking about the process. I'm stuck in a support loop and would welcome advice from anyone who has been through this. What happened
Why I'm stuck
My questions
If anything in the repos broke the rules, I'm happy to fix or remove it. I just need to know what it was. A reason with next steps, or a clear "no", would both be fine. It's the silence I can't work with. Thanks for reading. |
Replies: 3 comments 2 replies
|
Hi @FunctionFreak (posting about @auto-use) Ten plus weeks with zero reply on ticket 4529119 is beyond normal Support SLA. Open source project repos offline makes this urgent. Escalation steps that sometimes break login loops:
Evidence to attach:
If email replies fail:
Community cannot reinstate accounts. Only documented escalation paths work. Do not create new org or bot accounts to republish. That extends bans. Update this thread when Support responds so others know current queue times for long silent suspensions. |
|
I hear you. Eleven weeks with email only contact and closed redirect tickets is a dead end loop, not user error. One path left that sometimes works when login is blocked:
For GDPR non-response:
Community cannot reinstate. Documenting your timeline here helps the next person in the same situation. Update when anything moves. |
|
Hi @FunctionFreak, That sounds like a particularly difficult situation, especially since you’ve already tried the normal support routes and have an existing ticket going back to July. One important point from GitHub’s current documentation is that account suspensions can be appealed or submitted for reinstatement, and GitHub says those requests are reviewed by staff rather than decided entirely by automation. GitHub also says legitimate appeals will receive a final decision. Since you’ve already provided the relevant information on #4529119 and have been following up by email, I’d avoid creating more tickets or repeatedly opening new cases. Instead, I’d keep the existing case as the primary reference and make each follow-up concise: account I also wouldn’t rely too much on claims about a specific “normal” turnaround time or a particular escalation route unless GitHub has confirmed it. Their public documentation doesn't give a standard 10-week suspension-review SLA. The fact that the project is open source or that it is a computer-use tool doesn't by itself establish why the suspension happened. GitHub's policies cover a range of prohibited activity, including certain unauthorized-access and harmful automated activity, so ultimately the support/appeal process is the place where the specific reason needs to be established. Hopefully the existing case eventually gets a clear human response—whether that means reinstatement, an explanation of what needs to change, or a final decision that you can formally appeal if appropriate. |
Hi @FunctionFreak,
That sounds like a particularly difficult situation, especially since you’ve already tried the normal support routes and have an existing ticket going back to July.
One important point from GitHub’s current documentation is that account suspensions can be appealed or submitted for reinstatement, and GitHub says those requests are reviewed by staff rather than decided entirely by automation. GitHub also says legitimate appeals will receive a final decision.
Since you’ve already provided the relevant information on #4529119 and have been following up by email, I’d avoid creating more tickets or repeatedly opening new cases. Instead, I’d keep the existing case as the prima…