Guide

How to Get Your Project on GitHub Trending

Last updated: 2026-06-03

Landing on GitHub Trending can put a project in front of tens of thousands of developers in a single day. There is no secret submission form and no way to buy your way on legitimately — the list is computed from real activity. But the activity it rewards is specific and somewhat predictable, which means you can prepare for it. This guide explains what actually drives the ranking and how to give a launch the best honest shot at it.

First, understand what the ranking rewards

The single most important thing to internalise is that GitHub Trending does not rank by total stars. It ranks by recent star velocity — roughly, how many new stars a repository gains within a window (a day, a week, a month) relative to the normal background rate. A two-year-old project with 40,000 stars that gains 50 today will not trend; a brand-new repository that gains 300 stars in an afternoon almost certainly will.

That single fact reframes the whole problem. You are not trying to be big; you are trying to be suddenly interesting to a lot of people at once. Everything below follows from that. For the full mechanics, see our guide to how the rankings work.

Prepare the repository before you launch

Most of the stars that push a project onto the list are decided in the first few seconds a visitor spends on the page. If the repo is confusing, they leave without starring. Before you share anything, make the project legible at a glance:

A clear name and one-line description. The repository description field shows up on the Trending list itself. Make it a plain-English sentence a stranger understands — what it is and who it is for — not an internal codename or a vague tagline.
A README that sells in the first screen. Open with a single sentence explaining the problem you solve, then a short demo: a GIF, a screenshot, or a three-line code sample. Reviewers and casual visitors decide in seconds whether to read further.
Repository topics. Add relevant topics (the tags under the repo title). They help GitHub's own discovery surfaces and clarify the project's category.
A license and basic hygiene. A license file, a short contributing note, and no obviously broken install instructions all raise the share of visitors who trust the project enough to star it.

Time the launch

Because the daily list is about velocity, when the stars arrive matters as much as how many. A burst concentrated into a few hours moves the ranking far more than the same number of stars spread thinly over a week.

Pick a single launch moment rather than quietly pushing the repo public days early. You want the spike, not a slow trickle that never crosses the threshold.
Aim for when your audience is awake. For a developer-tools audience that skews toward the Americas and Europe, a weekday morning US time tends to catch both continents. Adjust for your real audience.
Have the README, demo and links ready before you post anywhere — the first hour is when momentum is won or lost.

Where to share it

Trending is downstream of attention you generate elsewhere. The repositories that climb are almost always being discussed somewhere first. Realistic channels, roughly in order of impact for technical projects:

Hacker News (a "Show HN" post) — a front-page thread can single-handedly trigger a trending day.
Reddit — relevant subreddits for your language or domain, where self-promotion rules allow.
X / Mastodon / Bluesky — a clear thread with a demo, especially if anyone with reach reshares it.
Developer newsletters and aggregators in your niche, which often pull from the same launches.
Communities you already belong to — Discord servers, Slack groups, forums — where sharing is welcome and not spam.

Write the external post for humans, not for the algorithm: explain the problem, show the result, and link the repo. The stars follow genuine interest.

What not to do

It is tempting to look for shortcuts. Avoid them — they range from ineffective to account-ending:

Don't buy stars or use "star-for-star" rings. Artificial engagement violates GitHub's Acceptable Use Policies and can get a repository or account flagged or removed. Trending's ranking also discounts patterns that look inorganic.
Don't beg in a way that annoys. Mass-DMing people to star your repo burns goodwill faster than it earns stars.
Don't fake the product. A launch that over-promises gets a spike and then a wave of disappointed visitors who never come back — the opposite of what you want.

Sustain it beyond the spike

A single daily appearance is nice but fleeting. The projects that benefit most turn one good day into lasting momentum: they respond to issues and pull requests quickly while the attention is high, ship a visible follow-up soon after, and keep posting progress. A repository that shows up across the daily, weekly and monthly views is sending a much stronger signal than a one-day wonder — and that staying power is what converts a trending moment into real users and contributors.

Set realistic expectations

Not every good project trends, and trending is not a measure of quality — it is a measure of attention at a moment in time. Plenty of excellent libraries never appear because their audience is small or their value is slow-burning rather than viral. Treat a trending appearance as a useful amplifier for a launch you were going to do anyway, not as the goal itself. The durable win is the users and contributors who stick around after the list has moved on.