My organisation got flagged can I speed up process for reviewing my tickets? #189733
Replies: 2 comments
-
|
Hi @pewpewgogo, here is the reality regarding your questions:
What you can do:
Hang in there, but avoid moving repos or creating new orgs until you hear back from the official support. |
Beta Was this translation helpful? Give feedback.
-
|
From what I understand, GitHub Trust & Safety reviews flagged organizations manually and the process can take some time. If the repositories are legitimate open-source projects, the best approach is to keep communication with GitHub support through the existing ticket and avoid creating new organizations or transferring repositories until the review is completed. Hopefully the issue gets resolved soon. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
My organization Open4dev was recently flagged and restricted. I believe it was triggered by automation, as the repositories only contain open-source blockchain-related code — nothing that violates GitHub's policies.
I've already submitted two support tickets — one from my personal account and one from an enterprise account — and it's been 4 days with no resolution. Some people in the community are saying it can take weeks or even months to get reviewed, which is a real problem as my team's workflow is blocked.
My question Does GitHub offer any premium or paid support tier that allows for faster review of flagged organization cases? I'm happy to pay if there's an official way to escalate and speed up the process similar to how DigitalOcean and Cloudflare offer priority support with faster response. Is there an equivalent option on GitHub?
Any advice from people who've been through this would be appreciated. Did anything help get your case resolved faster?
My second question If I decide to create a new organization while waiting for this to be resolved, is there a risk it gets auto-flagged again for the same reason?
My concern is that the new org would:
Transfer repos from the flagged org possibly trigger the same automation that flagged Open4dev
Has anyone been in a similar situation what's the safest way to move forward without making things worse?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions