How do you star a GitHub repository?

Open any public repo, say acme/rocketdb. Look at the top right of the page, up above the file list. There are three buttons in a row: watch, fork, star. The one you want is star. Click it once. That is the entire action, there is no step two.

If you're signed out, GitHub pauses and asks you to sign in (or make an account, which is free). Do that, and it brings you back to the repo, where one more click on star does it. Once it registers, the button flips to read "starred" and the little count beside it goes up by one.

On a phone it's the same idea, the star button just sits near the top of the repo screen instead of the corner. One tap. (GitHub reshuffles its buttons every so often, so if the layout looks new to you, just find the word "star" and the star icon. They always travel together.)

Every repo you star gets saved to one place: your stars tab. Go to GitHub.com/you?tab=stars (swap "you" for your own username) and the full list is there, newest first. It's a bookmarks folder you built one click at a time, and it's genuinely useful for finding that tool you starred at 2am and forgot the name of.

If the list gets long, you can sort it into star lists: small named buckets like "tools I actually use" or "read the source later." That filing is for you, private by default, nobody else sees how you organize things. The flip side of your list is a repo's stargazer list, the roster of everyone who starred it. More on that idea here: what is a GitHub stargazer.

Same button, backwards. Once you've starred something, that top-right button reads "starred." Click it again and it unstars: the count drops by one, and you come off that repo's stargazer list. No confirmation dialog, no drama, no message sent to anyone.

Does it hurt the project? Barely. One star is one small vote, so pulling it is one small vote back. Maintainers are not sitting there watching for a single un-star. Star freely, unstar freely. It's the lowest-stakes button on the whole site, which is kind of the point of it.

More than it looks like from where you're sitting. A star is one vote in GitHub's social-proof signal, and that signal turns up in a few real places: search ranking (starrier repos tend to surface higher for a query), the trending page, and the plain human gut-check where a visitor sees "1 star" next to "12,000" and decides how seriously to read the README.

Worth being precise about what the number is, though. The star count is an aggregate: it tells the world how many people liked a repo, not who those people are. It's a great headline and a weak address book. How GitHub folds those aggregate signals into what rises is here: how does GitHub trending work.

So your one click genuinely helps a project you like. It nudges visibility, it feeds the count, and it puts you on record as someone who showed up. Small, but real, and free.

You turn into a stargazer. The count goes up by one, and your username gets added to that repo's list of people who starred it. GitHub doesn't fire off a personal "dev-priya just starred you" ping to the owner, so it's quiet, but you are on the record, visibly, by name.

Now flip it around, because this is the part that matters if the repo is yours. Those stargazers are your first audience: the developers who saw acme/rocketdb and raised their hand. The count tells you how many. The names tell you who, and the who is the whole point. (GitHub recently narrowed who can browse a repo's full stargazer list from the public page down to its admins and collaborators, but as the owner you keep sight of your own. That's the current reality to plan around.)

That owner-first read is exactly what warmstars is built on: it takes a repo owner's own stargazers and turns them from a number into named people, from public data only, with a public email for many of them. The fuller walkthrough is in how to see who starred your GitHub repo. Your first users are often already on that list. You just have to look at it.