Amazing work Github team

This looks like a really useful improvement! 🚀 Having support, documentation, learning resources, community, and account information available through a single portal should make finding the right resources much easier.

The Copilot-powered search is especially interesting. It would be great if the search could continue improving with more context-aware results and direct links to relevant documentation or troubleshooting steps.

Looking forward to trying out the new experience once it becomes available for my account. 👍

A promising direction for GitHub Support

Centralizing support, documentation, learning resources, community content, and account-related information behind a single portal is a significant architectural improvement.

The Copilot-powered search is particularly interesting because the main challenge with GitHub support has historically been discoverability, rather than the absence of documentation. A unified search layer could reduce the need to determine first whether an issue belongs to GitHub Support, Community Discussions, Docs, or the status system.

One feature that would make this especially useful is context-aware troubleshooting. For example, when a user searches for a specific error, the portal could surface:

1. The relevant official documentation.
2. Known incidents or GitHub Status entries.
3. Relevant Community Discussions.
4. Known limitations or GitHub Changelog entries.
5. The appropriate support path based on the user's plan and permissions.

It would also be valuable if search results clearly distinguished official documentation from community-generated answers, so users can immediately understand the authority and freshness of the information.

Since the rollout is gradual, feedback on search relevance, result quality, and navigation between these resources should be particularly useful during this phase. Looking forward to seeing how help.github.com develops as the rollout reaches more accounts. 🚀

Hi @github ,one thing that could make the new portal especially useful is giving search results more context from the user’s actual issue.

For example, if someone searches an error or billing problem, it could show the relevant docs, current incidents, known limitations, and the correct support path together. It would also be helpful to clearly distinguish official GitHub guidance from Community answers so users know which information is authoritative.

The unified portal looks like a good step toward making GitHub support easier to navigate. 🚀

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?

Portal routing question: where should a general organization/account inquiry be submitted?

I am signed in as the owner of https://github.com/motiq-hr. After selecting my account or organization, the available choices are Copilot, Codespaces, Repositories, Education, Sign-in issues, and Billing and payments. I cannot find a general account/organization or username inquiry category; the existing forms require unrelated issue-specific information.

Our question is whether there is a permitted way to contact the owner of the already-taken username motiq (whose public profile has no contact details), or whether Support can forward a polite request about a voluntary username change. We understand the Username Policy: no request for release based on apparent inactivity, no forced transfer, no payment, and no trademark complaint. We are not asking Community to change an account or disclose private contact details.

Could the Help portal team point us to the appropriate private contact route, or confirm that such inquiries are not supported? A general-inquiry category or an explicit explanation would make the portal clearer. Thank you.