The work that moves a star count is never one launch post. It is the repository being ready when people arrive.
Write a README that answers the first question
The README should answer: what is this, why should I care, how do I run it, what does it look like and where do I go next. Lead with a one-line description, then a short demo GIF or terminal output.
Documentation is part of the product
A repository with a clear getting-started path gets shared. Cover installation, configuration, the main API or CLI and a real example.
Drive visitors from your website
Link the repository from your site, launch post and docs. A badge near the project description is a permanent path from owned traffic to the repository.
Be active in developer communities
Answer questions where they are asked, not with a link drop. A helpful issue response is more durable than a promotional comment.
Understand GitHub Trending
Trending is driven by recent star velocity and language/date filters, not lifetime totals. A launch with steady attention is more likely to appear than a single burst.
The takeaway
Fix the README, docs, demo and response loop first. Then a launch has somewhere to land.