Code of Conduct
What article is affected?
content/support/contacting-github-support/creating-a-support-ticket.md, specifically the Free, Pro, & Team reusable under "Creating a support ticket."
What is unclear?
The article says that people who do not see the open a support ticket link can still contact GitHub Support to report account, security, and abuse issues. It does not explain how to reach that permitted contact path.
This creates a gap at the exact point where free-account users need instructions. After opening the Support portal, they may see product or topic choices that do not clearly match a policy or account report. The article does not say which supported route exposes the account/security/abuse form, how to proceed if the first screen offers Copilot in GitHub Support, or how the flow differs from the paid-product open a support ticket link described immediately above it.
Suggested documentation outcome
Please document the current, supported steps for a free-account user to submit an account, security, or abuse report when the open a support ticket link is absent. The guidance could clarify:
- where to start in the Support portal;
- which option leads to the permitted account/security/abuse contact form;
- what to do when the displayed product or topic choices do not describe the report; and
- whether Copilot in GitHub Support is an optional first step or a required route to the form.
The exact labels should come from the current Support portal and be reviewed by a GitHub Support subject matter expert, since this public repository cannot establish the intended routing from the UI alone.
Why this is worth documenting
This is not a request to expand free-plan support entitlement. It is a request to make the article's existing entitlement actionable. The current note promises a valid contact path but leaves the reader without the steps needed to find it.
Code of Conduct
What article is affected?
content/support/contacting-github-support/creating-a-support-ticket.md, specifically the Free, Pro, & Team reusable under "Creating a support ticket."What is unclear?
The article says that people who do not see the open a support ticket link can still contact GitHub Support to report account, security, and abuse issues. It does not explain how to reach that permitted contact path.
This creates a gap at the exact point where free-account users need instructions. After opening the Support portal, they may see product or topic choices that do not clearly match a policy or account report. The article does not say which supported route exposes the account/security/abuse form, how to proceed if the first screen offers Copilot in GitHub Support, or how the flow differs from the paid-product open a support ticket link described immediately above it.
Suggested documentation outcome
Please document the current, supported steps for a free-account user to submit an account, security, or abuse report when the open a support ticket link is absent. The guidance could clarify:
The exact labels should come from the current Support portal and be reviewed by a GitHub Support subject matter expert, since this public repository cannot establish the intended routing from the UI alone.
Why this is worth documenting
This is not a request to expand free-plan support entitlement. It is a request to make the article's existing entitlement actionable. The current note promises a valid contact path but leaves the reader without the steps needed to find it.