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

Update — 23 August, ten days on. Still unresolved, and I can now be more precise about the defect. This includes one correction to my original post.

Correction first: there is an entry point I had not found. GitHub renders a banner on the flagged organization owner's own profile page, and the words "contact support" in it are a link. So the route is not entirely absent, and I want that on the record. It does not help, though, because it lands in the same place as everything else.

I then tested every documented and undocumented support entry point I could find. All seven resolve to the same destination, and that destination contains no form:

Every one returns HTTP 200 at /request/landing with zero form or textarea elements in the document. Signed in, that page presents a guided assistant that cycles between help articles and does not terminate in a ticket.

So the defect is narrower and more fixable than what I originally described. It is not that one policy link is stale. It is that every support entry point — documented and undocumented alike — collapses to a single landing page that has no submission form on it. A flagged owner who follows the documented process arrives nowhere, and so does one who guesses.

Current state, unchanged since I posted on 21 August: all repositories still return 404 to logged-out visitors, while the organization metadata continues to report every one of them as private: false, visibility: public. Actions execution has now stopped on a second repository as well. No email notice was ever received, so there is still no stated finding to remediate.

What would close this thread, independently of my own case: a support entry point that terminates in a submission form for a moderation appeal, and the Acceptable Use policy's "Appeal and Reinstatement form" link updated to point at it. As it stands, the published appeal process cannot be completed by anyone.

I remain happy to share the organization name and full details privately with anyone able to route this.

Appeal/Reinstatement route redirects to generic Support without an appeal option

On 21 September 2026, I reproduced this while signed in as the owner of the flagged organization Tisankan-dev:

1. Open https://support.github.com/contact/reinstatement from the organization's flag banner.
2. The browser redirects to https://help.github.com/support/contact.
3. Select the affected organization, displayed as Tisankan.dev, and GitHub.com.
4. The available categories are Copilot, Codespaces, Repositories, Education, Sign-in issues, and Billing and payments.
5. Selecting Repositories opens a repository support form. No dedicated Appeal/Reinstatement option is exposed.

Expected: A working appeal submission route, or clear confirmation that the available form routes organization restrictions to the appropriate reviewers.

Actual: I can submit ordinary repository requests, but cannot verify how to submit an organization moderation appeal through the documented route.

Existing Support case #4691082 has been open since 23 August 2026 and already contains my formal appeal. I am reporting the portal routing problem here; the moderation decision should remain in that private case.

Could the Help portal team confirm whether this redirect is intended and provide the supported appeal route for a flagged organization whose owner can still sign in?

Absolutely on the same boat -- had an organization flagged (15 years old, including a repo with 5k+ github stars and 10k+ repos depending on it) -- and cannot find any evidence for why the repo would be flagged or any way to appeal. No clue what to do next.