When you visit any GitHub repository, you'll notice three important buttons near the top of the page:
⭐ Star
π Watch
π΄ Fork
Many beginners assume these buttons perform similar functions, but each one serves a completely different purpose.
Understanding when to Star, Watch, or Fork a repository will help you use GitHub more effectively, especially when exploring open-source projects and collaborating with other developers.
In this guide, we'll explain each feature in detail with practical examples and real-world scenarios.
What are Stars, Watch, and Fork?
These three features allow you to interact with repositories in different ways.
| Feature | Purpose |
|---|---|
| ⭐ Star | Save or show appreciation for a repository |
| π Watch | Receive notifications about repository activity |
| π΄ Fork | Create your own copy of a repository |
Although they appear together, they solve different problems.
Understanding the Repository Header
When you open a repository, you'll usually see something like this:
Student-Management-System
⭐ Star π Watch π΄ Fork
Each button has a different function.
Let's explore them one by one.
What is a GitHub Star?
A Star is similar to bookmarking or liking a repository.
When you star a repository:
It is added to your starred repositories.
You can easily find it later.
The repository owner sees that someone appreciated the project.
The total star count increases by one.
Starring does not download the project or create a copy of it.
Real-Life Analogy for Stars
Imagine visiting a library.
You find a programming book that you really like.
Instead of borrowing it immediately, you place it in your "Favorites" list so you can find it later.
A GitHub Star works in the same way.
When Should You Star a Repository?
You can star a repository when:
You want to study it later.
You find it useful.
You appreciate the developer's work.
You want to recommend it to others.
You don't want to lose track of it.
Many developers use Stars as a personal bookmark collection.
Example
Suppose you find this repository:
Java-DSA-Tutorial
You're currently learning Java and want to return to it later.
Simply click:
⭐ Star
The repository is now saved in your starred list.
Can You Remove a Star?
Yes.
Click the Starred button again.
GitHub removes the repository from your starred repositories.
There is no limit to how many repositories you can star.
What is Watch?
Watching a repository means you're interested in its ongoing development.
When you watch a repository, GitHub sends notifications about important activities.
Examples include:
New Issues
Pull Requests
Discussions
Releases
Security alerts
Watching helps you stay informed about project updates.
Real-Life Analogy for Watch
Imagine subscribing to a YouTube channel.
Whenever a new video is uploaded, you receive a notification.
Watching a GitHub repository works similarly.
Instead of videos, you receive updates about the project.
Watch Options
GitHub offers different notification preferences.
Depending on the repository and your settings, you may see options such as:
Not Watching – You won't receive notifications unless you're directly involved.
Watching – You'll receive notifications for most repository activity.
Custom – You can choose which types of events generate notifications.
This flexibility allows you to avoid unnecessary notifications.
When Should You Watch a Repository?
Watching is useful when:
You're contributing to the project.
You're waiting for new releases.
You're following an active open-source project.
You're interested in project discussions.
You want updates about bug fixes or new features.
For repositories you're only casually interested in, starring is usually sufficient.
What is a Fork?
A Fork creates your own copy of another person's repository under your GitHub account.
The original repository remains unchanged.
Your fork is completely separate, allowing you to:
Experiment freely
Add new features
Fix bugs
Practice coding
Contribute changes back to the original project
Forking is one of the most important features in open-source development.
Real-Life Analogy for Fork
Imagine your teacher gives every student a copy of the same assignment.
Each student writes their own answers on their own copy.
No student's work affects another student's copy.
A GitHub Fork works the same way.
You receive your own copy of the repository to modify independently.
Fork Workflow
The basic workflow looks like this:
Original Repository
│
▼
Click Fork
│
▼
Your GitHub Account
│
▼
Your Copy of the Repository
You can edit your copy without affecting the original project.
Example
Suppose you discover this repository:
Portfolio-Website
You want to customize it for yourself.
Instead of changing the original project, click:
π΄ Fork
GitHub creates:
yourusername/
Portfolio-Website
Now you own a copy that you can modify as much as you like.
Does Forking Affect the Original Repository?
No.
The original repository remains unchanged.
Only your copy is modified when you make changes.
If you later want the project maintainers to review your improvements, you can submit a Pull Request (which we'll cover in a future article).
Star vs Watch vs Fork
| Feature | Star | Watch | Fork |
|---|---|---|---|
| Saves Repository | ✔ | ✖ | ✔ (your own copy) |
| Receives Notifications | ✖ | ✔ | Optional |
| Creates a Copy | ✖ | ✖ | ✔ |
| Supports Contributions | ✖ | ✖ | ✔ |
| Shows Appreciation | ✔ | ✖ | ✖ |
| Best For | Bookmarking | Following updates | Making changes |
Which One Should Beginners Use?
If you're just starting with GitHub:
⭐ Star repositories you find useful.
π Watch repositories you're actively following.
π΄ Fork repositories when you want to experiment or contribute.
You don't need to fork every interesting repository.
Common Beginner Mistakes
Confusing Star with Fork
Starring only bookmarks a repository.
It does not create a personal copy.
Watching Too Many Repositories
Watching hundreds of repositories can generate many notifications.
Only watch projects you're genuinely interested in following.
Forking Unnecessarily
If you only want to read code or save a repository, starring is enough.
Fork only when you intend to modify the project or contribute to it.
Thinking Fork Means Collaboration
Forking alone does not contribute changes to the original repository.
To propose changes, you must submit a Pull Request after making modifications.
Frequently Asked Questions (FAQs)
Can I star my own repository?
Yes.
Although many developers don't do this, GitHub allows you to star your own repositories.
Can I fork a private repository?
Generally, you can only fork private repositories under specific permissions and organizational policies. Public repositories are the most common repositories to fork.
Will the repository owner know I starred their project?
Yes.
Your star contributes to the repository's public star count, and your profile may appear among users who starred the repository.
Can I delete a fork?
Yes.
A fork is just another repository under your account.
You can delete it at any time from the repository settings.
Does starring download the project?
No.
Starring simply bookmarks the repository on GitHub.
Best Practices
Star repositories that you want to revisit.
Watch repositories that you're actively following or contributing to.
Fork repositories only when you plan to modify or contribute to them.
Avoid watching too many repositories to keep notifications manageable.
Explore popular starred repositories to discover high-quality open-source projects.
Summary
Although Star, Watch, and Fork appear together on every GitHub repository, they serve completely different purposes.
A Star lets you bookmark and appreciate a repository. Watch keeps you informed about project activity through notifications. Fork creates your own copy of a repository so you can experiment, customize, or contribute without affecting the original project.
Knowing when to use each feature will help you navigate GitHub more confidently and participate effectively in the open-source community.
Comments
Post a Comment