GitHub Star Sustained Growth Playbook

⚠️ Scope Differentiation:

gingiris-opensource

= Launch burst (0→1K in 72h). This skill = Sustained monthly growth (1K→10K→60K+).

Star Geographic Distribution & Launch Timeline

Applicable for the launch phase (to be used with

gingiris-opensource

)

• No single country/region should account for more than 20% of stars, which is an implicit threshold for getting on GitHub Trending.
• Tools: star-history.com (growth trend) · OSS Insight (geographic distribution, developed by Chinese developers)
• Launch sequence: Overseas promotion in the first week, domestic promotion (Moments / Chinese communities) only in the second week.
  • AFFiNE real case: Gained 6000 stars in the first week of open-sourcing, almost all from overseas channels.
• Reference rhythm for well-supported projects: Prepare at least 2-3 months in advance; 4000-6000 stars in the burst week, reaching 10000 stars in three weeks.

Healthy Benchmark for Star Geographic Distribution

Benchmark summarized by researching star distributions of well-known open-source projects like VSCode / Vue / AppFlowy in the week before AFFiNE's open-sourcing (oral recall, numbers marked with ≈)

• Hard rule: No one in the team posts on Moments in the first week of open-sourcing, prioritize English content — to avoid polluting the global distribution with Chinese circle traffic. AFFiNE's ≈6,000 stars in the first week matched the benchmark of well-known projects (China ≈19%).
• Counterexample lesson: After the team posted on Moments in the second week, China's share surged to ≈35% and never dropped since — once the distribution is polluted, it's basically irreversible.
• Anti-pattern: Asking friends to get 500-1,000 stars in the first two days is a comfort zone behavior, which will pollute the real signal of "testing the global market temperature".

README User Path Loop (Star CTA Loop)

AFFiNE open-source battle-tested SOP: Any user path that jumps out must be able to jump back to click the star.

1. Enumerate all user exit paths: README→official website; README→developer documentation; README→community (Discord, etc.).
2. Add reverse links back to GitHub README on every exit page: Official website, documentation site, community page all link back.
3. Add a star CTA at each backlink position ("If you like us, please give us a star on GitHub").
4. Loop self-check: Walk through each path to confirm users can jump back to the repo in one step and see the star guide from any exit.
5. Update README/official website with phases: Revise immediately when strategic goals change (e.g., shifting to commercialization), don't keep it unchanged.

Star Traffic Funnel Discipline

• All channels link back to GitHub instead of the official website: Links posted on Reddit / Twitter / Medium / directory sites all point to the repo, ensuring all traffic sees the star guide in the README.
• Let users get the value from README within 30 seconds, and directly guide them to click the star.
• Post different themed content on each channel in the first week, don't copy-paste the same article.
• Check GitHub Insights traffic sources every day in the first week of scaling, and decide which channels to focus on maintaining in the next few days; "maintenance" = talk to potential users on the channel, not paid marketing.
• Direct message the Twitter follower list of competing products: Send targeted DMs to followers of Notion / Miro-like competitors on launch day, AFFiNE's battle-tested conversion brought ≈hundreds of stars (oral number).
• Strategic shift signal: Stop focusing on GitHub itself after reaching ≈6,000 stars, shift to 1v1 user chats + building user communities.
• Never buy stars: AFFiNE never bought stars. When stars grew too fast, multiple investors wrote crawlers during DD to verify star sources, which were completely clean — buying stars will definitely be detected during due diligence.
• Look at growth rate not absolute value: Star growth rate (not total) is the signal for financing and Trending; GitHub Trending has an account permission system, it's not solely based on stars.

Core Objectives

Monthly Execution Framework (300 Star/Month Cadence)

1. Content Rhythm

2. Community Operations

3. Event-Driven Growth

4. Contributor System

1. Good First Issues — Clearly labeled, low threshold, with mentor responses
2. Regular Contributor — Accumulate 3+ merged PRs → Join Contributors list
3. Core Contributor — Responsible for specific modules → Repo write access
4. Maintainer — Code review rights + community management rights

• Label 3-5 Good First Issues per week
• First response to PR within 24h
• Monthly Contributor Spotlight (social media highlight)

5. Ambassador Program

• Exclusive badge + README acknowledgment
• Early access to new features
• Invitation to annual offline events
• Referral rewards (10-15% affiliate model)

• Has spontaneously shared the project on social media
• Has certain influence in technical communities (1K+ followers)
• Willing to produce 2+ pieces of content per month

Channel Priority Matrix

Budget Allocation (Monthly $2K-5K Tier)

Note: Automated outreach must comply with platform rate limits and anti-spam policies. Always respect opt-out requests.

Data Funnel

Impression
  → GitHub Repo Visit (CTR 2-5%)
    → Star (Visit→Star conversion rate 10-30%)
      → Clone/Fork (5-10% of Stars)
        → Contributor (1-5% of Forks)
          → Paid User/Enterprise Lead

Battle-Tested Benchmarks (Data Sources)

AFFiNE Star Timeline (Firsthand Source)

• Reddit Evidence: Subreddits like r/selfhosted, PKM brought tens of thousands of traffic, accumulating at least 2,000 stars (≈3-4 out of 10 posts went viral, others didn't or were removed).
• Credibility Endorsement: Zero paid marketing, never bought stars. Multiple investors wrote crawlers during DD to verify star sources, which were completely clean.
• Expectation Management (self-reported): Copying this SOP doesn't guarantee "6,000 stars in one week", but reaching 1,000–3,000 stars in 3 months is relatively easy, and other teams have already replicated it successfully.

Full SOP Reference