How to Get More GitHub Stars: The Definitive Guide
We grew AFFiNE from 0 to 33,000 GitHub stars in 18 months. This guide covers every tactic we used — what worked, what failed, and what actually moves the needle.
Why I Wrote This
When I started marketing AFFiNE, I couldn't find a comprehensive guide on growing GitHub stars. Most articles were surface-level fluff:
- "Write good documentation" (okay, but then what?)
- "Share on social media" (which platforms? how?)
- "Build a community" (how do you start with zero users?)
This guide is different. It's the tactical playbook I wish existed when we started.
Table of Contents
| Section | What You'll Learn |
|---|---|
| Part 1 | Why stars matter (and don't matter) |
| Part 2 | The first 100 stars (bootstrap phase) |
| Part 3 | 100 to 1,000 stars (content + community) |
| Part 4 | 1,000+ stars (scaling + virality) |
| Part 5 | GitHub Trending strategies |
| Part 6 | Common mistakes to avoid |
Part 1: Why GitHub Stars Matter
The Real Value of Stars
Stars are credibility, not customers.
What stars actually give you:
- ✅ Social proof when pitching investors
- ✅ Trust signal for potential users
- ✅ Visibility on GitHub Trending
- ✅ Team motivation metric
- ✅ Contributor attraction
What stars DON'T give you:
- ❌ Guaranteed users or revenue
- ❌ Product-market fit
- ❌ A sustainable business
Use stars as a stepping stone, not a destination.
The Credibility Threshold
| Star Count | What It Signals |
|---|---|
| < 100 | "New project, unknown" |
| 100-500 | "Some traction, worth trying" |
| 500-1,000 | "Legitimate project" |
| 1,000-5,000 | "Established, active community" |
| 5,000+ | "Industry-recognized" |
| 10,000+ | "Major project" |
Your first goal: Cross the 1,000 star threshold as fast as possible.
Part 2: The First 100 Stars
This Phase Is "Artificial" (And That's OK)
Your first 100 stars should come from people you know. Don't pretend otherwise.
Why this matters:
- New visitors check star count before engaging
- < 100 stars = low conversion rate on everything else
- You need this baseline before content marketing works
Tactics for 0→100
1. Personal Network Outreach
Message everyone you know in tech:
"Hey! We just open-sourced our project. Would mean a lot if you could check it out and star it if you find it interesting."
- Keep it personal, not mass-blast
- Target developers who might actually use it
- Follow up individually
2. Workspace/Conference Hustle
- Print QR code to your repo
- Walk around coworking spaces
- Chat with developers at conferences
- Ask during coffee/lunch breaks
3. Existing Communities
- Company Slack/Discord
- University alumni networks
- Previous colleague groups
- Online communities you're already part of
More tactics: The Cold Start Problem for GitHub Projects: How to Get Your First 1,000 Stars
Part 3: 100 to 1,000 Stars
Shift to Organic Growth
Once you hit 100, your tactics should become authentic and scalable.
Content Strategy
Four types of content that work:
| Type | Example | Purpose |
|---|---|---|
| Direct | "Introducing [Project]" | Explain what you built |
| Tutorial | "Build X with [Project]" | Show practical usage |
| Listicle | "10 OSS tools for Y" | Reach broader audience |
| Building in Public | "How we solved X" | Build community |
Key principles:
- Every post needs a clear CTA ("Star us on GitHub")
- Include repo link in multiple places
- Use visuals (GIFs, screenshots)
Content deep dive: Developer Marketing Playbook: How to Reach Technical Audiences in 2026
Distribution Channels
Tier 1 (High Impact):
- Reddit (r/programming, r/opensource, niche subreddits)
- Hacker News (unpredictable but high ceiling)
- Product Hunt (good for launches)
Tier 2 (Medium Impact):
- Dev.to, Hashnode, HackerNoon
- Twitter/X (dev community)
- Discord/Slack communities
Tier 3 (Long-term SEO):
- Your company blog
- GitHub Awesome Lists
- Documentation sites
Channel breakdown: GitHub Repo Promotion: 15 Channels That Actually Drive Stars
Awesome Lists Strategy
GitHub "Awesome" lists are curated collections (awesome-python, awesome-react, etc.).
How to get added:
- Find relevant awesome-* repos
- Read their contribution guidelines carefully
- Make sure your project meets their criteria
- Open a PR with proper formatting
Pro tips:
- Some lists require minimum stars, tests, or docs
- Chinese awesome lists have higher acceptance rates (75% in our experience)
- Start with smaller, niche lists before big ones
Part 4: Scaling to 1,000+
The Compound Effect
After 1,000 stars, growth accelerates. You'll get:
- Organic discovery on GitHub
- Mentions in newsletters
- Unsolicited blog posts
- Contributor applications
Your job shifts from "pushing" to "amplifying."
Community Building
Create a home for your users:
- Discord server (preferred for dev tools)
- GitHub Discussions
- Dedicated forum
Engage consistently:
- Respond to issues within 24 hours
- Thank contributors publicly
- Share community wins
Community tactics: Developer Marketing 101: How to Grow Your Open Source Project
Combining with Product Hunt
Product Hunt can accelerate GitHub growth dramatically.
The playbook:
- Build PH launch → drive traffic to GitHub
- Spike in stars → hit GitHub Trending
- Trending → more organic stars
- Leverage momentum for press/community
PH + GitHub synergy: Product Hunt for Open Source: The Step-by-Step Playbook
Part 5: GitHub Trending
Why Trending Matters
GitHub Trending page is massive exposure:
- Thousands of developers browse it daily
- One day on Trending = 500-2,000 new stars
- Creates cascading visibility
Factors That Affect Trending
| Factor | Impact |
|---|---|
| Star velocity | High — stars per hour/day |
| Recent activity | Medium — commits, issues, PRs |
| Language category | Medium — less competition in niche languages |
| Account signals | Low — but new accounts count less |
Trending Tactics
Coordinate your push — Launch content, notify community, post on social all in the same 24-48 hour window
Time it right — Weekdays, avoid holidays, mornings PT
Pick your language — "TypeScript Trending" easier than "All Languages Trending"
Sustain momentum — Don't just spike; maintain activity for multiple days
Complete breakdown: GitHub Star Growth: 7 Proven Tactics That Got Us 33k Stars
Part 6: Common Mistakes
1. Launching Too Early
Promoting with < 100 stars = low conversion on everything.
Fix: Get your first 100 from your network before any public promotion.
2. One Big Push, Then Nothing
Growth requires consistency, not single events.
Fix: Plan ongoing content/promotion, not just launch day.
3. Ignoring Issues
Nothing kills a project's reputation faster than unresponded issues.
Fix: Respond within 24 hours, even if just to acknowledge.
4. Poor README
Your README is your landing page. First impressions matter.
README checklist:
- [ ] Clear one-sentence description
- [ ] Screenshot or GIF at top
- [ ] Quick start guide (< 5 steps)
- [ ] Feature list
- [ ] Contributing link
- [ ] License
5. No Clear CTA
If you don't ask for stars, you won't get them.
Fix: Include "⭐ Star us on GitHub" in content, docs, and social posts.
The AFFiNE Journey: Timeline
| Month | Stars | Key Events |
|---|---|---|
| 0 | 0 | Launch |
| 1 | 1,000 | Product Hunt #1, initial PR |
| 3 | 5,000 | Reddit viral post |
| 6 | 10,000 | Consistent content strategy |
| 12 | 25,000 | HN front page, multiple Trending |
| 18 | 33,000 | Sustained organic growth |
Full case study: How I Got 33K GitHub Stars: The Complete Marketing Playbook
Complete Resource Library
GitHub Growth
- How I Got 33K GitHub Stars: The Complete Marketing Playbook
- GitHub Star Growth: 7 Proven Tactics That Got Us 33k Stars
- GitHub Star Growth: 10K Stars in 18 Months (Real Data)
- The Cold Start Problem for GitHub Projects
- GitHub Repo Promotion: 15 Channels That Actually Drive Stars
Product Launch
- Product Hunt for Open Source: The Step-by-Step Playbook
- Product Hunt Launch: The Complete 2026 Playbook for #1
- Open Source Launch Checklist: 127 Tasks
Developer Marketing
- Developer Marketing Playbook: How to Reach Technical Audiences in 2026
- Developer Marketing 101: How to Grow Your Open Source Project
- Open Source Marketing: The Complete Guide for 2026
Key Takeaways
- First 100 stars are artificial — Get them from your network
- Content + Distribution = Growth — Write once, distribute everywhere
- Consistency beats intensity — Weekly content > one viral post
- GitHub Trending is the multiplier — Coordinate your efforts for spikes
- Stars ≠ users — But they build the credibility to get users
Free Resources
📘 Gingiris Open Source Marketing — Complete OSS marketing playbook
📗 Gingiris Launch Playbook — Product launch strategies
📙 Gingiris B2B Growth — PLG and SLG growth tactics
Got questions? Drop a comment or find me on Twitter @iris_carrot.
Top comments (0)