Starring, Watching, Following: Social Features and Notifications

GitHub has three distinct, easily confused social/engagement features — starring, watching, and following — each serving a genuinely different purpose. Module 3 already covered repository watch levels in the context of notification management; this lesson places that alongside starring and following to clarify exactly how all three relate.

Learning Objectives

• Explain what starring a repository does and does not affect.
• Recall the different watch levels and their effect on notifications.
• Explain what following a user does.
• Understand how all three features contribute to GitHub's social and discovery layer.

Key Terms to Know Before Using GitHub's Social Features

• Starring: Bookmarking a repository, both as a personal reference and as a public signal of interest or endorsement, contributing to that repository's visible star count.
• Watching: Subscribing to notifications for a repository, at a level ranging from no extra notifications to full activity alerts (covered in Module 5's mentions and notifications lesson).
• Following: Subscribing to a specific user's public activity, appearing in your personal GitHub activity feed.
• Star count: The total number of users who have starred a repository, often used informally as a rough signal of a project's popularity or community trust.

How GitHub's Social Features Actually Work

**Starring** a repository is primarily a **bookmarking and endorsement** action — it saves that repository to your personal 'Starred' list for easy future reference, and simultaneously contributes to that repository's public **star count**, a number prominently displayed on the repository and often used informally (though imperfectly) as a rough signal of a project's popularity, quality, or community trust. Starring a repository does **not** subscribe you to any notifications about its activity — it's purely a bookmark-and-signal action, with no effect on what alerts you receive.

**Watching**, covered in depth in Module 5's mentions and notifications lesson, is specifically about **notification subscription**. Recall the levels: 'Not watching' (only direct mentions and your own participation notify you), 'Watching' (all repository activity notifies you), and 'Ignoring' (no notifications at all, even mentions). This is the feature that actually controls what alerts land in your notification inbox — entirely separate from starring, which has no notification effect whatsoever.

**Following** operates at the level of a **person**, not a repository — following a specific GitHub user subscribes you to their public activity, which then appears in your personal GitHub activity feed (visible on your own profile/homepage), showing things like repositories they've starred, new public repositories they've created, and other public actions. This is GitHub's closest equivalent to a social media 'follow', letting you keep loosely informed about what a specific developer you're interested in is publicly up to, without needing to check their profile directly and repeatedly.

Putting all three together with a clear mental model: **star** a repository to bookmark it and signal interest (no notifications). **Watch** a repository to control what notifications you actually receive from it (independent of whether you've starred it). **Follow** a person to see their broader public activity in your feed (independent of any specific repository). A common, sensible pattern: star many repositories you find interesting or want to reference later, watch only the small number of repositories you're actively working on or need full visibility into, and follow developers whose work you want to stay loosely aware of over time.

Star vs Watch vs Follow: Visual Walkthrough

Draw three separate icons with distinct effects. STAR icon: arrow to 'Personal Starred list + contributes to public star count' — labeled 'No notification effect.' WATCH icon: arrow to 'Notification inbox — controls what alerts you receive (Not watching / Watching / Ignoring)' — labeled 'No bookmarking effect.' FOLLOW icon (pointing at a person, not a repo): arrow to 'Your personal GitHub activity feed — shows that person's public actions' — labeled 'Operates on USERS, not repositories.' Caption beneath all three: 'Three independent features — using one does not imply or trigger the others.'

Star vs Watch vs Follow: Key Differences

Feature	Applies To	Primary Effect
Star	A repository	Bookmarks it + contributes to its public star count; NO notification effect
Watch	A repository	Controls notification volume (Not watching / Watching / Ignoring); NO bookmarking effect
Follow	A user (person)	Their public activity appears in your GitHub activity feed

Managing Watch Levels: Example Configuration

# These are all web-interface actions, not Git commands, but here's the conceptual mapping:

# Starring a repo (bookmark + public signal, NO notifications)
# → Click the "Star" button on any repository page

# Watching a repo (controls notifications, NO bookmarking)
# → Click the "Watch" dropdown, choose: Not watching / Watching / Ignoring

# Following a user (their public activity appears in YOUR feed)
# → Visit their profile, click "Follow"

# View your own starred repositories list at any time:
# https://github.com/your-username?tab=stars

Breaking Down the GitHub Social Features Example

This mapping reinforces that all three actions are independent, web-based interactions with genuinely different effects: starring bookmarks and publicly signals interest without any notification consequence, watching exclusively controls notification volume without any bookmarking effect, and following operates at the level of a person rather than a repository, populating your personal activity feed with that person's public actions. Visiting your own starred repositories list (a dedicated tab on your profile) is a common way to revisit projects you've bookmarked for later reference.

How Stars, Watching, and Following Are Used in Practice

• Star count is commonly (though imperfectly) used as an informal signal of a project's popularity when developers are evaluating which of several similar open-source libraries to adopt.
• Maintainers sometimes track star growth over time as a rough, informal engagement metric, though experienced engineers generally caution against over-relying on star count as a proxy for actual code quality or project health.
• Developers commonly follow well-known figures or teams in their specific technology area specifically to stay loosely aware of new projects or public activity, without needing to actively check in on them.
• Teams frequently advise new members to star (not necessarily watch) a handful of key internal or reference repositories for easy future access, while reserving full 'Watching' status only for repositories requiring their active, ongoing attention.

GitHub Social Features Interview Questions and Answers

Q1. What is the difference between starring a repository and watching it?

Starring bookmarks a repository to your personal list and contributes to its public star count, with no effect on notifications. Watching controls what notifications you actually receive about that repository's activity, with no bookmarking effect — the two are entirely independent features.

Q2. Does following a user relate to a specific repository, or something else?

Following operates at the level of a person, not a repository. Following a specific GitHub user subscribes you to their public activity, which appears in your own personal GitHub activity feed, letting you stay loosely aware of what they're publicly doing across all their projects.

Q3. If you star a repository, will you automatically receive notifications about its activity?

No. Starring is purely a bookmarking and public-signal action with no notification effect whatsoever. To receive notifications about a repository's activity, you need to separately set its watch level to 'Watching', which is an entirely independent feature from starring.

Star, Watch, Follow Quiz: Test Your Understanding

1. What does starring a repository do?

1. Subscribes you to all notifications for that repository
2. Bookmarks it to your personal list and contributes to its public star count
3. Follows every contributor to that repository
4. Automatically forks the repository

Answer: B. Bookmarks it to your personal list and contributes to its public star count

Explanation: Starring is purely a bookmark-and-signal action, saving the repository for personal reference and adding to its visible star count, with no effect on notifications.

2. Which GitHub feature specifically controls how many notifications you receive from a repository?

1. Starring
2. Watching
3. Following
4. Forking

Answer: B. Watching

Explanation: Watching, with levels ranging from Not watching to Watching to Ignoring, is the feature that specifically determines what notification volume you receive from a given repository.

3. What does following a GitHub user do?

1. Subscribes you to notifications for all of their repositories
2. Their public activity appears in your personal GitHub activity feed
3. Automatically stars all of their repositories
4. Grants you write access to their repositories

Answer: B. Their public activity appears in your personal GitHub activity feed

Explanation: Following operates at the person level, populating your own activity feed with that user's public actions, distinct from any repository-specific starring or watching behavior.

Common Mistakes With GitHub's Social Features

• Assuming starring a repository automatically subscribes you to notifications about it, when starring and watching are entirely independent features.
• Confusing following (a person-level feature) with watching (a repository-level feature), expecting one to substitute for the other.
• Over-relying on a repository's star count alone as a definitive measure of its quality or reliability, without independently evaluating the actual code and maintenance activity.
• Setting every repository of interest to 'Watching' rather than simply starring most and reserving watching for only the few requiring genuine ongoing attention (echoing Module 5's notification fatigue guidance).

Star, Watch, Follow: Exam-Ready Quick Notes

• Star: bookmark + public signal, contributes to star count — NO notification effect.
• Watch: controls notification volume (Not watching/Watching/Ignoring) — NO bookmarking effect.
• Follow: operates on USERS, not repositories — their public activity appears in your feed.
• All three are independent — using one does not trigger or imply the others.

Star, Watch, Follow: Key Takeaways

• Starring, watching, and following are three genuinely independent GitHub features, each serving a distinct purpose.
• Starring bookmarks and publicly signals interest; watching controls notification volume; following tracks a specific person's public activity.
• A sensible default pattern: star broadly for reference, watch narrowly for genuine ongoing attention, follow selectively for people whose work you want to stay aware of.

Frequently Asked Questions About GitHub's Social Features

Q1. What does starring a repository on GitHub do?

It bookmarks the repository to your personal 'Starred' list for easy future reference, and adds to its publicly visible star count, often used informally as a rough popularity signal. It has no effect on the notifications you receive.

Q2. Does starring a repository also subscribe me to its notifications?

No. Starring and watching are entirely independent features. To receive notifications about a repository's activity, you need to separately set its watch level, regardless of whether you've starred it.

Q3. What is the difference between watching a repository and following a user?

Watching applies to a specific repository, controlling how many notifications you receive from it. Following applies to a specific person, subscribing you to their public activity across GitHub, which then appears in your own personal activity feed.

Q4. Where can I see all the repositories I've starred?

Visit your own GitHub profile and click the 'Stars' tab, or go directly to github.com/your-username?tab=stars, to see the full list of repositories you've bookmarked.

Q5. Should I star or watch a repository I'm interested in but not actively working on?

Starring is generally the better choice for repositories you just want to bookmark or reference later, since it doesn't generate any notifications. Reserve 'Watching' for repositories where you genuinely need ongoing visibility into all activity, to avoid unnecessary notification volume.

Summary

GitHub offers three distinct, easily conflated social and engagement features. Starring a repository bookmarks it to your personal list and contributes to its public star count, functioning as a signal of interest or endorsement, but has no effect whatsoever on notifications. Watching, covered in depth in Module 5, specifically controls what notifications you receive from a repository, ranging from 'Not watching' through 'Watching' to 'Ignoring', entirely independent of whether you've starred it. Following operates at the level of a person rather than a repository — subscribing to a specific user's public activity, which then appears in your own personal GitHub activity feed. These three features are genuinely independent: starring a repository doesn't subscribe you to notifications, watching doesn't bookmark it, and following tracks a person's broader activity rather than anything tied to a single repository.