product-example 1 linked patterns checked
GitHub Docs: About notifications and subscriptions
Documents GitHub notifications as updates for activity users are subscribed to, reasons a user receives notifications, inbox triage, customization, and notification retention.
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 |
|---|---|---|---|
| Follow / subscribe | Choose follow / subscribe when the user is opting into future update delivery from a specific target. | Activating Follow, Subscribe, or Watch creates or updates a subscription record for the named target, not merely a visual bookmark. | GitHub describes notifications as updates about activity users have subscribed to and documents notification reasons, customization, inbox triage, and retention. |
Comparisons supported by this source
- Follow / subscribe vs notification center vs mentions vs activity feed
GitHub describes notifications as updates about activity users have subscribed to and documents reasons for receiving notifications.
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: .