Organization/repo flagged for no apparent reason and support not answering tickets for 3+ months?!

[alexlicuriceanu]

🏷️ Discussion Type

Bug

Body

Hi, I'm writing here as somewhat of a last resort, maybe somebody else has had this issue and can shed some light on it.

I have an organization with a few repositories that contain VERY simple Lua scripts for FiveM servers. The scripts have at most 20 lines, literally nothing suspicious about them, clear clean code, not obfuscated or anything like this, and I suddenly woke up with the organization being automatically flagged and locked, without any kind of message, email or explanation and how it can be resolved.
I don't even know what could have possibly flagged this org, as it barely has anything in it to begin with?!

Now I have this global banner everywhere on github:

I can't modify anything, can't delete the org, nothing. I did what the banner said and contacted support (ticket #4583924) with no kind of response for 3 months already (ticket was submitted on 19 Jul, I wrote follow-ups on 1 Aug and 6 October), no response.

I'm willing to collaborate with anything the support team deems necessary to do in order to resolve this issue, but nobody is replying.
Has anyone else encountered this issue? Is waiting this long for a reply normal?

[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. ⭐

[queenofcorgis]

Hi @alexlicuriceanu,

I looked into this. There should be a reply on your support ticket, you should be good to go now, but the ticket is the best source of truth here!

[alexlicuriceanu]

Thanks for the quick reply, the issue is now resolved :)

[queenofcorgis]

Hooray! Happy to hear and help 😃 See you around the community!