GitHub Watch vs Star: what each actually does
Two buttons sit at the top of every repository: Star and Watch. They look interchangeable. They are not — and confusing them is the single most common reason people either drown in notifications or wonder why they never get any.
Star = bookmark. Nothing more.
Starring a repository adds it to the list of repos you can find later under Your stars. It feeds GitHub's recommendations and it's the number people see on the repo page. That's all.
Starring never sends you a single notification. If you starred a project hoping to hear about releases, you won't. (The closest thing: release announcements from repos you star can appear in your feed, but that's not a notification.)
Watch = subscription. Everything.
Watching a repo subscribes you to all conversations in it: every issue, every pull request, every comment, every discussion. On an active repo with dozens of contributors, watching means hundreds of notifications per week — which is why "watch" defaults to off unless you contribute.
The four watch states
| State | You get notified about |
|---|---|
| Participating (default) | Threads you created, commented on, were @mentioned in, or had assigned to you |
| All activity | Everything in the repo — every issue, PR and comment |
| Custom | A checklist: Releases, Issues, Pulls, Discussions, Security alerts — pick any combination |
| Ignore | Nothing, ever — not even direct @mentions |
The setting almost nobody finds: Custom watch
This is the fix for the two most common complaints at once:
- "I want to know when this repo ships a release, but not every issue" → Watch → Custom → tick Releases, untick everything else.
- "I'm mentioned in security discussions but I don't want the firehose" → Custom → Security alerts only.
How this connects to your unread count
Your notification inbox is built from three streams:
- Participating — anything you're personally involved in, regardless of watch status.
- Watching — everything from repos with All Activity or matching Custom settings.
- Subscriptions — individual threads you explicitly subscribed to (or were auto-subscribed to by commenting).
If your badge exploded overnight, check github.com → Settings → Notifications → Watching: one accidental click of "All Activity" on a busy repo is usually the culprit. If the badge never moves despite active teams, you're probably relying on a star where a watch was needed.
Triage the noise without touching your watches
DevNotify shows every notification in one menu bar list with per-repo filtering — keep your watches exactly as they are, and just see the ones that matter first. Free to try, $19 for a lifetime license.
Download DevNotify for macOS Buy license — $19Quick reference
- Star = save for later + public endorsement. No notifications.
- Watch (default) = only threads you participate in.
- Watch (All Activity) = the full firehose.
- Watch (Custom) = pick releases/issues/pulls/discussions/security individually.
- Ignore = total silence for that repo.