GH-900 ยท Collaboration tools
How do GitHub notifications work?
Watching, participating and custom subscriptions, the notifications inbox, email versus web delivery and how to reduce noise.
Key points
- You are subscribed by watching a repository, by participating in a thread (commenting or being @mentioned) or by a custom watch for chosen event types.
- Notifications arrive in the web or mobile inbox and by email.
- Unsaved inbox items are kept for 3 months, and you reduce noise by narrowing what you watch.
Source: https://docs.github.com/en/subscriptions-and-notifications/get-started/configuring-notifications
Practice questions
Which action subscribes you to a conversation automatically?
- Commenting on it or being @mentioned
- Starring the repository
- Forking the repository
- Cloning the repository
Show answer
Answer: A. Commenting on it or being @mentioned
Participating, by commenting or being mentioned, subscribes you to the thread. Starring, forking and cloning do not.
Where can GitHub notifications be received?
- The web inbox
- GitHub Mobile
- A gist feed
- A wiki sidebar
Show answer
Answer: A. The web inbox, B. GitHub Mobile, C. Email
Notifications go to the web inbox, GitHub Mobile and email. Gists and wikis are not delivery channels.
Unsaved notifications stay in the inbox forever unless you delete them.
Show answer
Answer: False
False. Unsaved inbox notifications are kept for 3 months; saving one keeps it indefinitely.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
