How do you actually grow on GitHub? More followers, stars, and visibility

[KunalSiyag]

🏷️ Discussion Type

Question

Body

I've been building projects and exploring open source, and one thing I'm curious about is how developers actually grow on GitHub.

A project can be genuinely useful, well-built, and documented, yet barely get any attention.

Meanwhile, some repositories take off and gain thousands of stars. Like they have zero pull requests, no forks, no contributors other than the creators but still get 1000's of stars within a week. How???

For those who've managed to grow their GitHub presence: How? What did you change? Did you refer to something?

I'd love to hear real experiences, especially from developers who've grown their profiles from scratch.

What's one thing you wish you'd known earlier about growing on GitHub?

Guidelines

• I have read and understood this category's guidelines before making this post.

[saivamshidanthoju]

One thing I wish I had understood earlier is that building a good project and getting people to discover it are two different problems.

A useful project does not automatically get visibility. People need to discover it, understand its value quickly, and have a reason to try it.

Here are the practices I would focus on:

1. Solve a specific problem.
Projects that clearly solve one painful problem are often easier to discover and recommend than projects with many unrelated features.

2. Make the repository understandable in 30 seconds.
Use a clear README with the problem, a demo or screenshot, installation steps, a short usage example, and the reason someone should choose your project.

3. Share the project where its users already are.
Participate genuinely in relevant developer communities, answer questions, and share your project when it directly helps someone. Explain what you learned rather than posting the same promotional message everywhere.

4. Make contributing easy.
Add reproducible examples, good issue descriptions, clear contribution guidelines, and beginner-friendly issues. A simple setup process can make the difference between someone trying your project and leaving.

5. Focus on real usage, not just stars.
Stars can indicate interest, but they do not prove that a project is useful or actively maintained. Look at issues, feedback, repeat usage, external contributors, and actual adoption too.

Regarding repositories that gain thousands of stars in a week, there is no single explanation. They may receive attention from social media, newsletters, influential developers, launch platforms, or an existing audience. Some may also benefit from trends or coordinated promotion. A lack of pull requests or forks alone does not establish that the stars are fake.

My biggest takeaway: Build something specific, make it easy to try, and consistently show it to the people who need it. One genuine user who finds your project useful is a better starting point than chasing a large star count.

I'd also recommend tracking where your repository traffic and new users come from so you can repeat the outreach that actually works.

[yashganorkar005]

A Practical Step-by-Step Guide to Growing on GitHub

I think one of the biggest misconceptions is that building a good project automatically makes people discover it. In reality, building the project and getting people to notice it are two different tasks.

Here is a practical approach for developers starting from zero:

Step 1: Solve one specific problem

Instead of creating another generic to-do app, find a problem that a particular group of developers actually faces. A small, useful tool can be easier to promote than a large project without a clear purpose.

Step 2: Make the project easy to understand

When someone opens your repository, they should quickly understand:

• What problem does it solve?
• Why should they use it?
• How can they run it?
• What makes it different?

Add a clear README, installation instructions, screenshots or a short demo, and a few real usage examples.

Step 3: Make it discoverable

Add relevant GitHub topics, create a useful repository description, and use a clear social preview image. These small improvements help people understand and find your project.

Step 4: Don't just publish it and wait

Share your project where the people who need it already spend time. Depending on the project, that might be relevant Reddit communities, developer forums, Hacker News, technical Discord servers, or social media.

Don't simply drop a link everywhere. Explain the problem you solved, show a short demo, and ask for genuine feedback. Follow each community's self-promotion rules.

Step 5: Make it easy for people to try

A project that takes 30 minutes to understand may lose potential users before they even test it.

Provide a quick-start guide, sensible defaults, examples, and clear error messages. If it's an open-source project, add contribution guidelines and beginner-friendly issues where appropriate.

Step 6: Turn attention into engagement

Respond to issues, listen to feedback, fix bugs, and release useful improvements. People are more likely to return when they see that a project is maintained and that their feedback matters.

Step 7: Measure more than stars

Stars are useful, but they don't necessarily mean people use or contribute to a project. Also look at genuine usage, issues opened, discussions, forks, repeat visitors, and contributions.

But how do some repositories get thousands of stars in a week?

There isn't one universal explanation. Some launch into an existing audience, solve a timely problem, get shared by influential developers, appear in newsletters or curated lists, or benefit from a well-timed community launch. A repository can also attract many stars without attracting contributors; starring a project requires much less effort than installing, using, or contributing to it.

So I wouldn't judge a project's quality from its star count alone.

The biggest lesson: GitHub is where you host and collaborate on your code, but publishing alone doesn't guarantee discovery. Build something useful, explain its value clearly, get it in front of the right audience, and keep improving it based on real feedback.

Useful references:

• [GitHub Docs: Customizing your repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository)
• [GitHub Blog: 5 tips for promoting your open-source project](https://github.blog/open-source/maintainers/5-tips-for-promoting-your-open-source-project/)

[saivamshidanthoju]

One thing I'd add is to treat project promotion as an experiment rather than guessing what works.

For each project, I would:

• Add relevant GitHub topics and a clear one-line description so people can understand its purpose quickly.
• Create a short demo showing the project solving a real problem.
• Share it with a specific audience, such as developers who use the same framework or face the same problem.
• Check GitHub's traffic insights to see which external sites bring visitors and which content gets attention.
• Improve the README and onboarding based on questions people ask.

I'd also avoid judging growth only by stars. A project with 30 stars and users who regularly use it can be more valuable than one with 1,000 stars and no real engagement.

My biggest takeaway: Don't just ask how to get more stars; find out who needs your project, where those people discover tools, and what makes them return.

[ronitgupta138]

One big lesson: GitHub isn't a discovery engine on its own. People don't browse GitHub looking for random repos to star — stars come from external distribution.

The repos that blow up usually do 3 things well:

1. Solve one real problem painfully well: Don't build generic clones; build a tool that fixes a headache you personally faced (like a CLI tool, a performance optimization, or an SDK fix).
2. Pixel-perfect README: Add a 10-second GIF/demo right at the top, clear benchmark numbers, and a 1-command install. If someone can't understand what it does in 5 seconds, they bounce.
3. Show up where developers hang out: Share it on Reddit (r/rust, r/java, r/programming), Hacker News (Show HN), or tech Twitter. If it's useful, the community will star and share it.