1. Make the first ten seconds count
Most visitors decide whether to star within seconds of landing on your repo. Everything they need to decide should be above the fold of your README.
- A one-line pitch that says who it is for and what it does. "A CLI that turns your Git history into a changelog" beats "A powerful, flexible tool".
- A screenshot or short GIF of the thing working. People star what they can see.
- Install and run in one command, copy-pasteable.
- A live demo link in the repo's About box if it runs in a browser.
2. Fill in the About box and topics
The description, website and topics in the About box are what GitHub shows in search results and on topic pages. Add five to ten topics people actually search for, such as the language, the framework and the problem (for example cli, nextjs, automation). Upload a social preview image under Settings so links to your repo look good when shared.
3. Launch where your users already are
A repo nobody sees gets no stars, however good it is. Share it in a few places that fit, and write for each audience instead of pasting the same link everywhere. The guide to promoting an open source project lists where to post and what to say.
4. Keep shipping
Stars come in bursts around launches, releases and posts. Tag releases, write short release notes and share each meaningful update. A repo with a commit last week looks alive; one untouched for a year rarely gets starred, even when it still works.
5. Ask, once
A single line at the end of your README, such as "If this saved you time, a star helps others find it", works better than you would expect. Don't put it at the top, and don't beg.
6. Swap stars with real developers
Early on, the hardest part is getting in front of anyone at all. On StarSwap you add your repo with a one-line pitch, then swipe through repos from other builders and star the ones you like on GitHub. The more you give, the more your own repo is shown. Browse what's trending this week to see which pitches work.
What to avoid
Don't buy stars or use fake accounts. GitHub's Acceptable Use Policies prohibit fake accounts and automated or inauthentic activity, suspicious stars can be removed, and a repo with thousands of stars but no issues, forks or activity looks fake to anyone who checks. Real stars from real developers are slower, but they are the ones that bring users and contributors.
Questions
How many GitHub stars is a good number?
For a personal side project, 16 stars unlocks the Starstruck achievement and 100+ puts it ahead of the vast majority of public repositories. Popular libraries run into the thousands.
Is it allowed to swap GitHub stars?
Starring a repo you genuinely like from your own account is normal GitHub use. What GitHub's policies prohibit is fake accounts, bots and automated or inauthentic starring. On StarSwap every star is given by a signed-in developer from their own account, one swipe at a time.
Do GitHub stars help my repo get found?
Yes. GitHub search can sort by stars, many curated lists use star counts, and GitHub Trending is driven by recent star activity, so more stars generally means more visibility.