product-example 1 linked patterns checked
GitHub Docs: Reporting abuse or spam
Documents reporting users, organizations, repositories, issues, pull requests, discussions, comments, Marketplace apps, and contact-link abuse, including report destinations for GitHub Support and repository maintainers.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Report abuse | Choose report abuse when a user flags content, behavior, an account, or an object as potentially harmful, abusive, spam, illegal, impersonating, privacy-violating, or against community rules. | The Report action is reachable from the object being reported and carries object identity into the flow without asking users to manually re-enter obvious context. | Supports report entry points for users, organizations, repositories, issues, pull requests, discussions, comments, apps, contact links, maintainer routing, support routing, and form submission. |
Comparisons supported by this source
- Report abuse vs review queue vs comments vs security warning vs permission denied state vs notification center
GitHub documents report entry points, reportable object types, report destinations, reason selection, and support form submission.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub Docs. Last checked: .