product-example 1 linked patterns checked
GitHub Docs: Managing disruptive comments
Documents hiding and unhiding comments, choosing hide reasons, editing comments, visible edit history with actor and timestamp, redacting sensitive information, delete permissions, delete as last-resort moderation, and timeline events for deletions.
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 |
|---|---|---|---|
| Comments | Choose comments when the core object needs attached discussion, review feedback, annotation, or follow-up notes that remain separate from the object's primary editable content. | Submitting a comment creates a durable item with stable ID, author, timestamp, body, anchor, visibility scope, and notification behavior. | GitHub moderation guidance supports hide, unhide, edit history, redaction, delete permissions, delete timeline events, and reasoned moderation. |
Comparisons supported by this source
- Comments vs textarea vs feed vs activity log
GitHub moderation guidance supports hide, unhide, edit history, redaction, delete permissions, delete timeline events, and reasoned moderation.
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: .