# The GitHub repo should be ready before Hacker News arrives > A plain essay on HN launch proof: 24-hour star windows, posting time, repo readiness, Show HN limits, public launch tracking, and why bought GitHub stars damage trust. - Canonical HTML: https://growth.iangoh.com/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/ - Published: 2026-06-10 - Updated: 2026-06-10T06:39:08.000Z - Categories: Hacker News, GitHub, developer marketing - Niches: AI products, open-source tools, developer tools, LLM infrastructure, SaaS, technical founders ## On this page - Measure the first week, not only the first hour - Pick a posting window you can support - Make the repo useful before strangers arrive - The Show HN label is not the product - Turn the launch into data you can reuse - Do not poison the trust graph ## Start with these related tactics - [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/): Track GitHub stars at 24 hours, 48 hours, and 7 days after Hacker News before calling the launch a win or a miss. - [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/): Choose the Hacker News posting window deliberately because timing can change the GitHub proof a launch earns. - [HN repo ready before community attention](/growth-ideas/hn-repo-ready-before-community-attention/): Make the GitHub repo useful before the HN post lands because the attention can turn into forks, stars, and contributors quickly. A Hacker News launch is easy to remember badly. The founder remembers whether the post reached the front page. The repo remembers something more useful: who starred it, forked it, opened issues, tried the install path, and came back after the first burst. For an open-source AI tool, the GitHub repo is not a backend artifact. It is part of the launch page. ## Measure the first week, not only the first hour [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/) is the first operating habit. Track 24 hours, 48 hours, and 7 days. The diffusion study found average star gains of 121 in 24 hours, 189 in 48 hours, and 289 in a week after HN exposure. The point is not that every repo should hit those numbers. The point is that the shape of the curve tells you whether the launch created a quick glance or a trust trail. ## Pick a posting window you can support [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/) sounds tactical, but it is really about readiness. If timing can change the number of stars by hundreds, the launch window should not be random. Pick a time when the relevant readers are likely awake and when the team can answer comments, fix small docs problems, and watch the repo while the thread is live. ## Make the repo useful before strangers arrive [HN repo ready before community attention](/growth-ideas/hn-repo-ready-before-community-attention/) is the most practical move in the batch. A separate study found HN exposure was followed by significant increases in forks, stars, and contributors across AI GitHub projects. That means the README, install path, demo, examples, issue labels, and license are not polish. They are conversion surfaces for technical trust. ## The Show HN label is not the product [HN Show label after substance, not before](/growth-ideas/hn-show-label-after-substance-not-before/) keeps the founder honest. The diffusion paper found no statistical advantage from the Show HN tag after controls. The label can frame a good artifact. It cannot make an unfinished artifact feel ready. HN is unusually good at noticing that difference. ## Turn the launch into data you can reuse [HN public API launch tracker before vanity summary](/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/) is a small antidote to folklore. The research pipeline used public APIs and finished in under five minutes. A founder version can be much simpler. Save the post timestamp, score, comment count, GitHub stars, forks, contributors, issues, and docs clicks. Then write down what changed at 24 hours, 48 hours, and 7 days. ## Do not poison the trust graph [GitHub authentic star quality before star buying](/growth-ideas/github-authentic-star-quality-before-star-buying/) is the guardrail. Star count matters only because developers believe it says something about real attention. The fake-stars research is a warning: suspected fake-star activity surged in 2024, and the short-term lift can become a long-term liability. For a technical product, that is a terrible trade. Real stars, issues, forks, contributor notes, and external writeups age better. If I were preparing a technical launch this week, I would make the repo useful before the post, pick a window the team can support, measure the first week, and protect the trust graph like it belongs to the product. Because for developer tools, it does. If you want help turning technical launches, repo proof, and source-backed pages into a cleaner growth system, Ian Goh works with founders through Ian Goh advisory. ## Related GrowthDex tactics - [HN star-window ledger before launch retrospective](/growth-ideas/hn-star-window-ledger-before-launch-retrospective/) - Hacker News, GitHub, Developer Marketing - [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/) - Hacker News, Launch, Developer Marketing - [HN repo ready before community attention](/growth-ideas/hn-repo-ready-before-community-attention/) - Hacker News, Open Source, GitHub - [HN Show label after substance, not before](/growth-ideas/hn-show-label-after-substance-not-before/) - Hacker News, Launch, Positioning - [HN public API launch tracker before vanity summary](/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/) - Hacker News, Analytics, GitHub - [GitHub authentic star quality before star buying](/growth-ideas/github-authentic-star-quality-before-star-buying/) - GitHub, Developer Trust, Open Source ## Essay chronology - [Newer essay: The community should feel useful before it asks for growth](/blog/the-community-should-feel-useful-before-it-asks-for-growth/) - Community growth, Reddit, operator-led distribution - [Older essay: The answer should stay inspectable after the summary](/blog/the-answer-should-stay-inspectable-after-the-summary/) - AI visibility, support, brand trust ## Keep reading - [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) - community-led growth, launches, brand trust - [The product should keep a visible pulse](/blog/the-product-should-keep-a-visible-pulse/) - developer marketing, launches, brand trust - [The answer page is a sales call that does not end](/blog/the-answer-page-is-a-sales-call-that-does-not-end/) - answer-engine growth, founder-led content, developer marketing ## Continue through the blog - [AI products](/blog/#path-ai-products) - 3 essays in this path - [SaaS](/blog/#path-saas) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [arXiv: Launch-Day Diffusion: Tracking Hacker News Impact on GitHub Stars for AI Tools](https://arxiv.org/abs/2511.04453) · [GrowthDex source hub](/sources/arxiv-launch-day-diffusion-tracking-hacker-news-impact-on-github-stars-f/) - [arXiv: Social Media Reactions to Open Source Promotions on Hacker News](https://arxiv.org/abs/2506.12643) · [GrowthDex source hub](/sources/arxiv-social-media-reactions-to-open-source-promotions-on-hacker-news-ar/) - [arXiv: Six Million Suspected Fake Stars in GitHub](https://arxiv.org/abs/2412.13459) · [GrowthDex source hub](/sources/arxiv-six-million-suspected-fake-stars-in-github-arxiv-org/) - [Hacker News Show HN Guidelines](https://news.ycombinator.com/showhn.html) · [GrowthDex source hub](/sources/hacker-news-show-hn-guidelines-news-ycombinator-com/) ## Editing notes - Kept the essay on one plain idea: the repo is part of the HN launch surface. - Used research numbers as guardrails without implying every launch can copy the average star gains. - Made the tactics practical: measure windows, choose timing, prepare the repo, track public data, and avoid fake stars. - Cut broad launch language and kept the piece readable for founders who are not deep in HN culture. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.