Request for help checking my Aethersailor reinstatement ticket #4510782 #201098
Replies: 3 comments
-
|
Hi there, Thank you for providing such a detailed timeline, your remediation steps, and all the relevant ticket numbers (especially the active reinstatement ticket #4510782). While the public community forum cannot directly access or expedite individual account tickets, GitHub Staff and Community Moderators frequently monitor these discussions. Because you have explicitly shown that Enterprise Support directed you back to your personal ticket, and you have already self-remediated the Actions workflow, your case is well-prepared for review. I am giving this thread a bump to help increase its visibility. Hopefully, a GitHub Staff member or Moderator can see this, verify that ticket #4510782 is routed to the correct internal team, and provide you with an update. Hang in there—reinstatement queues for high-volume automation triggers often require a deeper review by the operations team. |
Beta Was this translation helpful? Give feedback.
This comment was marked as low quality.
This comment was marked as low quality.
-
|
Hi @Rule-Bot , This community is managed by GitHub employees, but it is not a support forum. You have done everything necessary on your end by opening a ticket on our Support page. This is a public forum, and the community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. There are an extremely high volume of Support tickets right now, yours will be answered in the order it was received based on the amount of tickets ahead of yours. Please open only one ticket per request. As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Profile
Body
Hello GitHub Community,
I am posting from Rule-Bot, a maintenance account I use. My affected personal account is Aethersailor.
On June 12, 2026, my Aethersailor profile and repositories became unavailable to signed-out users. The restriction appears to have been triggered by a GitHub Actions workflow that performed high-volume DNS classification while generating repository rule files.
I did not knowingly or intentionally misuse GitHub Actions, use it as a general computing service, or engage in any malicious or commercial activity. However, I understand that the workflow’s resource and network usage may have fallen outside GitHub’s permitted use.
After learning of the concern, I immediately archived the relevant repository, disabled Actions across the affected repositories, confirmed that no jobs remained queued or running, and committed to moving resource-intensive automation away from GitHub-hosted runners. I am willing to complete any additional remediation GitHub requires, including keeping Actions restricted.
I have tried to follow the appropriate support process:
As of July 6, 2026, my account and unrelated community projects, including Custom_OpenClash_Rules and SubConverter-Extended, remain publicly unavailable.
I understand that reinstatement reviews take time and that the Community cannot decide the outcome. Could a GitHub staff member please help confirm that ticket #4510782 has reached the appropriate team and advise whether anything further is required from me?
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions