How Open-Source Startups Got Onto GitHub Trending: 7 Lessons From the Gitroom Videos
An open-source repo gets onto GitHub Trending when several channels send it real attention in the same few days, and when that attention turns into issues, pull requests and forks, not only stars. That is the shared lesson of Nevo David's YouTube channel, most of it published under the name Gitroom, where he, who says he grew Novu from zero to 31,000 stars before founding Postiz, broke down how open-source startups grew. The case studies below are Digger, Wing, Keep, Mirrord, Kubescape and Papermark, plus his own launch of Gitroom and Postiz.
How we wrote this: we read the captions of nine of his videos and linked every claim to the second it is said. Star counts and results are as the speakers described them on camera; we have not audited them, and captions occasionally mishear names. We are not affiliated with Gitroom, Postiz or any company featured; links go to the original videos. For his own Postiz story, see our Postiz open-source interview answers and AI agents as a distribution channel. Disclosure: we sell a transcription service and are applying parts of this playbook to our own open-source work, so we have a stake in what works.
The case studies at a glance
| Project | What moved it, by their account | Where to watch |
|---|---|---|
| Digger | An honest engineering post on r/golang, then a YouTube reaction, Trending, a newsletter and Hacker News in one week | 02:27 |
| Wing | Six traffic sources at once, about 400 stars in 3 days | 00:02 |
| Keep | A Show HN that described the product through tools people already knew | 05:21 |
| Mirrord | Deep technical posts on Reddit that other people carried to Hacker News | 02:16 |
| Kubescape | A free tool released quickly after a government security guide | 03:10 |
| Papermark | One tweet shared with people the founder already knew | 02:53 |
| Postiz | Almost the same product relaunched with a different one-line description | 03:39 |
1. Stars alone do not get you onto Trending
The most useful warning on the channel is about stars. Nevo says a Hacktoberfest push once brought his Gitroom repository (then under an earlier name) about 3,000 stars and it still never trended, not even on the TypeScript feed (01:25). His explanation is that GitHub looks at real activity:
"GitHub knows that activity is not only stars." (01:09)
So the work before a launch is making the repo easy to contribute to: issues someone can pick up today, docs that explain how to run it, and a place to ask questions. In another video he says his early launches brought stars and users but few contributions, and that this is why they did not trend (00:02).
2. Stack your channels into the same week
The biggest results on the channel came from chains, not single posts. Digger's growth engineer describes a colleague's post on r/golang about rewriting the product from Python to Go in a week. A well-known developer YouTuber reacted to it, the video reached about 150,000 views, and the repo then hit GitHub Trending, a large developer newsletter and Hacker News (02:27). That chain kept Digger on Trending for about a week (12:21).
Here is the full interview as transcribe.so processed it: the chapters, section summaries and who said what come straight from the transcript, and the questions below are ones we wrote and answered from it. Press any timestamp to play the interview from that moment, or open a chapter to read that part.
Command Palette
Search for a command to run...
Chapters, section summaries, speaker turns and timestamps above are unedited transcribe.so output, so a few names are misheard ("Prime Agent" is ThePrimeagen). Speaker names come from the video's on-screen captions. The questions and answers were written by us from the transcript, with each claim linked to the moment it is said.
Open the full interview on its own page: How Digger trended on GitHub for a week.
Wing's launch was planned the same way: six traffic sources aimed at one short window, which Nevo says brought about 400 stars and a spot on Trending in three days (00:02). Not every source carried its weight. He notes that X converted to stars much better than LinkedIn (01:38), and that dev.to articles with a strong title and cover reliably drew 10,000 to 20,000 views, mostly from Google (02:33).
3. On Hacker News, describe yourself through tools people know
Keep's co-founder tells the story of posting a Show HN for a small command-line alerting tool, boarding a flight, and landing to about 600 stars (02:10). After a pivot they launched again and reached about 2,000 stars (02:41). His advice on positioning is to borrow familiar names; Keep framed itself as GitHub Actions for monitoring tools:
"Explain what you're doing by giving a reference to something that everybody knows." (05:21)
He adds that a second post of the same URL will probably be blocked, so the first launch linked the website and the second linked the GitHub repository (05:59). In a separate interview, Nevo advises linking a Show HN to the GitHub repository rather than the main website (14:01).
Mirrord's team took a slower route. They post in-depth engineering stories on Reddit and wait for someone else with Hacker News karma to submit them, which put them on the front page four or five times (02:16). Their co-founder adds that asking people to upvote made no difference, so they stopped (03:26). Digger's guest says the same about engineered pushes: they never worked, and the front page came only after the YouTube video had already made people curious (11:37).
4. On Reddit, tell the story and drop the pitch
Digger's r/golang post had no call to action beyond a disclosure and a link:
"There was no call to action at all. I think Reddit hates it." (05:56)
Wing shows the opposite. Nevo says its Reddit post used a hooky title and cover image, read like an advertisement, drew nasty comments and downvotes, and brought few stars despite about 20,000 views per subreddit (04:17).
His own launch is the clearest example of how much the sentence matters. He posted "Gitroom, schedule your open source launch week" on r/selfhosted and got replies like "it seems like you are deaf to your market" (03:39). He then relaunched almost the same platform as "Postiz, open source social media scheduling tool", framed against the schedulers people already used, and the comments asked for a Docker Compose file instead (05:20). His conclusion is that the product barely changed; the message did.
5. When news breaks in your field, ship a free tool
Kubescape is the case study about timing. ARMO's VP of Marketing describes the US NSA publishing Kubernetes hardening guidance in August 2021, and the CTO proposing a free open-source scanner instead of the usual blog post or webinar (03:10). They released a very basic tool quickly (04:12), and he says it got about 1,000 stars in its first week (06:22). The guest credits reacting first and giving people results in about two minutes (06:58), and the team kept the habit: when a new vulnerability is published, they blog about it first with a scan that checks whether you are exposed (12:00).
6. On Product Hunt, share one post with people you already know
Papermark's founder pushed a single tweet that linked to the launch, from an account with about 1,500 followers, and says it reached close to 100,000 views (02:53). He sent that tweet, not the Product Hunt link, mostly to people he already knew, and did not ask them to upvote (05:18). The launch reached #1 Product of the Day and took the repo from about 800 to over 1,000 stars (07:57). He later ran a launch week of one feature a day for five days (21:56), and contributors helped finish features he had shipped early (24:40).
7. Make contributing easy, then ask for contributions, not stars
Nevo's contributor advice is practical. Open at least 20 to 25 issues and tag them "good first issue" (03:32), keep easy work like refactors and repeatable integrations, and link each one to the docs (02:57). Run support in a Discord forum indexed by Answer Overflow so answers reach Google (07:03). His best contributor drive was an article about contributing to open source as a way to get hired, which he says filled the issues with volunteers (04:50).
What we will not copy
A few tactics that come up in open-source launch advice break platform rules or our own outreach rules, so we are leaving them out:
- Asking friends or groups to upvote. Reddit and Hacker News treat coordinated voting as manipulation, and Mirrord's own experience above says it did not help anyway.
- Rewarding people for stars. GitHub's terms forbid incentivized engagement; bounties and contests should pay for contributions, not stars.
- Emailing people whose address you found on GitHub. Nevo describes messaging contributors of similar repos one to one (10:18); our rule is to email only people who chose to hear from us, and to reach anyone else through public issues or community channels.
What to copy
- Write the one sentence first. "Open-source alternative to a tool people already know" gives the fastest context, as the Gitroom-to-Postiz relaunch shows.
- Make it easy to run and to contribute. Clear docs, a one-command install and real issues come before any launch.
- Stack channels into one week. An article, Reddit, Hacker News and your own audience, all pointing at the repo in the same days.
- Lead with an engineering story. Honest, technical posts travel; pitches get buried.
- Watch the news in your field. A free tool shipped the week something big happens beats a blog post shipped a month later.
- Ask people you know to look, not to vote. Papermark's founder says he did not ask anyone to upvote.
Frequently asked questions
How many stars do you need to get onto GitHub Trending?
None of these videos gives a threshold. What they describe is a burst of stars, forks, issues and pull requests within a few days, which is why the biggest results here came from several channels at once.
Should a Show HN link the website or the GitHub repo?
Nevo advises linking the GitHub repository. Keep used both on separate launches, because a repeated URL would probably be blocked.
Is posting your own project on r/selfhosted allowed?
Many self-hosting communities welcome open-source, self-hostable projects from their authors when the post is disclosed and useful. Read each community's current rules before posting, since they change.