Join our December Community Call as we build an AI assisted ATS with ToolJet, Supabase and Open AI! – RSVP
Back

How to Get More GitHub Stars: 12 Practical Ways

January 17, 2022
•
7 mins read
•

Author

Navaneeth Padanna Kalathil

Navaneeth Padanna Kalathil

Updated

To earn more GitHub stars, make your project easy to understand, try and contribute to, then share useful examples with the people it serves. Improve your README and quickstart, demonstrate a real use case, respond to feedback and give contributors manageable issues. Stars are signals of interest, not proof of active use or production readiness.

We launched ToolJet on GitHub in June 2021. When this article was first published in January 2022, we had more than 4,500 stars and contributions from more than 100 developers. The twelve practices below reflect that early experience; the screenshots are historical examples, not current repository metrics or a controlled attribution study.

For the current count, visit the repository. For interpreting growth rather than promoting a project, see our GitHub stars evaluation guide. This article focuses on earning relevant attention and helping people succeed with your project.

Start with these five checks

  • Can a new visitor explain the project’s purpose after reading the first screen?
  • Can someone follow the quickstart and reach a working result?
  • Are installation requirements, license and support channels clear?
  • Does each announcement show a useful change or example?
  • Can a first-time contributor find an issue with acceptance criteria and setup instructions?

1) Readme matters

A README is often a visitor’s first introduction to a repository. Explain the problem, show a short example or screenshot, and provide a tested quickstart. Link the license, contribution guide and support channel. Follow GitHub’s README guidance; use badges only when they communicate useful status. We used Shields.io for our early badges.

Our README at the time of the original article:

Open-Source - readme

Examples of projects with great Readme:
a) Github – nestjs
b) Github – typesense
c) Github – airbyte
d) Github – strapi

2) Documentation

Write documentation around the tasks users need to complete: installation, first successful use, troubleshooting, upgrades and deployment. Ask someone unfamiliar with the project to follow the instructions, then fix every unclear step. Link the source repository naturally from the docs. Docusaurus is one option for maintaining a documentation site.

Here are some projects with great documentation:
a) Docs.nestjs
b) Docs.n8n.io
c) Guides – rubyonrails
d) Plotly – python
e) Docs.mapbox

3) Drive visitors from your website to GitHub

Open-Source - drive visitors from website to github

Give interested website visitors a clear link to the repository, ideally near documentation, installation instructions or a working example. Explain what they will find there. A useful tutorial can introduce the project more effectively than repeated requests for stars. Keep the repository link accessible without interrupting the user’s main task.

4) Be active in developer communities

Participate in developer communities where your project solves a relevant problem. Answer the question first, disclose your connection to the project and follow the community’s promotion rules. For example, a charting-library maintainer can explain a React charting approach and link a working example when it directly helps.

Play nice. Do not try to link to your project if it does not add any value to the discussion.

5) Email campaigns

You might already have users signed up for your website. Add a link to your GitHub repository in the welcome email.

Do not spam people who haven’t signed up for your updates.

Open-Source - trending repositories on github

Appearing on GitHub Trending coincided with increased visibility in our early launch experience. Treat it as a possible outcome, not a dependable acquisition plan. We cannot provide a guaranteed star threshold or a formula for inclusion. Focus on useful releases and relevant distribution rather than attempting to manufacture a spike.

7) Ask for feedback from relevant communities

A Reddit post in r/reactjs by u/navaneethpk titled

Communities such as ProductHunt, Hackernews, Reddit communities, etc may find your project useful. This can bring in more visitors and stargazers to your repository.

Target only the relevant communities. If you think majority of the members won’t find your project interesting, it is not a relevant community. Spamming can cause more harm than good. Also, it’s just not nice.

8) Grow a community

Choose a support channel your users can access and your maintainers can sustain. That may be GitHub Discussions, a forum, Slack or Discord. ToolJet used Slack during its early growth. Keep durable answers in public documentation or searchable issues so useful knowledge is not lost in chat, and avoid opening more channels than you can support.

Play nice. Appreciate the work of others.

9) Add a public roadmap

Publish priorities and explain how users can suggest or discuss changes. A maintained issue list or project board is enough to start. Distinguish ideas from committed work and shipped features. An abandoned roadmap can confuse users more than a modest, regularly updated list.

10) Share useful updates on social channels

Use the channels where your intended users already discuss their work, whether X, LinkedIn, Mastodon or a specialist forum. Share a short demonstration, a release with a concrete benefit or an engineering lesson. Link the relevant example and repository. Measure useful visits and feedback rather than posting the same star request repeatedly.

11) Respond to feedback

Acknowledge feedback, ask for reproducible details and explain the next step. Set realistic response expectations for your maintainer capacity. Close the loop when an issue is fixed, and explain respectfully when a request does not fit the project.

Do not try to evade negative feedback, work on it if it aligns with your vision, otherwise politely explain.

12) Add relevant labels for contributors

Use GitHub’s good first issue label for genuinely approachable work. Include setup steps, expected behavior, acceptance criteria and a maintainer contact. A label alone does not make an issue beginner-friendly. Review contributions constructively and keep the available issues current.

Measure whether the attention helps

Use GitHub repository traffic to inspect visitors, full clones, referring sites and popular content when you have the required access. GitHub exposes visitor and clone data for the past 14 days, so record comparable windows if you need a longer baseline. Referrer reporting is incomplete and excludes some sources.

Alongside stars, track successful installations, useful issues, merged contributions and returning users where you have a reliable measurement. Record release dates and distribution channels. A launch spike does not establish that a specific tactic caused growth or that those visitors became users.

Frequently asked questions

Can I get GitHub stars without paying?

Yes. People can discover a useful project through documentation, examples, relevant discussions and releases. These activities take maintainer time and do not guarantee a number of stars. Avoid bought stars, bots and reciprocal-star schemes; they do not demonstrate genuine adoption.

How do I star a GitHub repository?

Sign in to GitHub, open the repository and select Star near the top of the page. GitHub’s starring guide explains how to organize and revisit saved repositories. Starring is different from watching notifications or using the software.

How many GitHub stars make a project successful?

There is no universal threshold. A specialist library and a broad developer platform have different audiences. Evaluate whether the project solves its users’ problems and remains maintained; star counts alone cannot show that.

No. The practices in this article can help people understand and discover your work, but they do not guarantee Trending placement. Build a sustainable release and support process instead of relying on a single visibility spike.

Explore the ToolJet repository if its use case fits your work. Feedback, reproducible bug reports and useful contributions are welcome.

Join us

About the author

Navaneeth Padanna Kalathil

Navaneeth Padanna Kalathil

CEO & Founder -ToolJet

Read image
woman in glasses works on a laptop, with a software interface
Hop on AI native app development rocketship!

Build internal apps with AI, connect your data, and refine them in a visual builder.

Thank you! Your submission has been received!
Read image
woman in glasses works on a laptop, with a software interface
Hop on AI native app development rocketship!

Build internal apps with AI, connect your data, and refine them in a visual builder.

Try for Free

Thank you! Your submission has been received!
G2 Rating details

Customers rate ToolJet Momentum Leader in Low-Code Development Platforms

Talk to Us