GitHub Enterprise Organization Flagged for Over 4 Weeks – No Resolution Despite Multiple Support Tickets #212134
Unanswered
malithwee
asked this question in
Enterprise
Replies: 1 comment
|
Hi @malithwee, Thank you for your patience. The community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place as I just checked its spot in the queue. It will be answered in the order it was received based on our team's resources and the amount of tickets ahead of yours. We appreciate your understanding! In the future, please only open 1 ticket per incident. Thank you! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
GitHub Enterprise Organization Flagged for Over 4 Weeks – No Resolution Despite Multiple Support Tickets
Hello GitHub Community,
I'm reaching out here because we've been struggling to get a critical issue resolved through GitHub Support, and we're running out of channels to get the necessary attention.
We are an existing GitHub Enterprise customer, and our organization has been flagged for more than four weeks.
The notification we received states:
We immediately contacted GitHub Support and have since raised multiple tickets:
Unfortunately, despite repeated follow-ups, we still haven't received a clear explanation of why our organization was flagged, what actions are required from our side, or when this issue can be resolved.
What's even more concerning is that some of the support tickets have been archived without any meaningful explanation or resolution.
This is not just a visibility issue for us. The restriction is affecting our engineering operations and blocking critical production workflows. Our team has been dealing with this situation for over a month now.
As an Enterprise customer on a paid subscription, we expected a much more responsive support experience, particularly when a restriction has a direct impact on our production operations.
We're hoping to get some guidance from GitHub employees or anyone who has experienced a similar situation:
We're not looking to bypass any security or compliance checks. We simply need transparency, a clear explanation, and someone from GitHub who can take ownership of this case.
Any guidance or assistance from the GitHub team or community would be greatly appreciated.
Thank you.
All reactions