Use case / use-case
Draft a Show HN from your GitHub release, then submit it deliberately.
Hacker News rewards human, non-promotional launches, so S2P prepares a Show HN-ready title and body from your release and leaves the submission to you - it never auto-firehoses to HN.
Draft a Show HN, you submit
S2P prepares a title and first comment shaped for Show HN, then stops. You submit deliberately, because that is what Hacker News rewards.
No firehose to Hacker News
S2P never auto-posts releases to HN. Automated promotional submissions get flagged, so the deliberate, human path is the only one S2P supports here.
Value-first framing
The draft leads with what you built and why it is interesting to builders, not a marketing headline, which is how Show HN earns attention.
Channel fit
Show HN rewards deliberate, human launches.
Hacker News is unforgiving toward automation and promotion, so the winning move is a well-timed, honest Show HN that you submit yourself, not a scheduled blast from a tool.
Title formula matters
A strong Show HN title is plain and specific: what it is and what it does, often with the repo or live link, and no hype words.
Lead the body with the why
The first comment should explain the problem, what you shipped, and what you learned, which is the framing S2P drafts from your release.
Timing and presence are on you
Show HN rewards being around to answer questions, so you pick the moment and stay in the thread - S2P only prepares the copy.
Workflow
From GitHub release to a Show HN you submit by hand.
Connect GitHub, pick the release worth a launch, generate a Show HN-ready title and body, then submit it yourself when the timing is right.
- Trigger a Show HN draft from a milestone release, not every patch.
- Draft a plain, specific title and a value-first body from the release.
- Edit the framing so it reads as a builder sharing, not a promo.
- Submit the Show HN yourself and stay to answer questions.
- Keep the prepared copy linked to the source release for reference.
Sample Show HN draft
Show HN: We built approval rules so GitHub releases never post to social unreviewed. It detects a release, drafts channel copy, and routes it to a reviewer first. Here is why we built it and what we got wrong on v1 - feedback welcome.Keep exploring
Related pages
FAQ
Questions teams ask
Does S2P auto-submit releases to Hacker News?
No. S2P never auto-posts a firehose to Hacker News. It drafts a Show HN-ready title and body, and you submit it deliberately when the timing is right.
Why does S2P not automate Hacker News submissions?
Because Hacker News rewards human, non-promotional launches and flags automated promotion, so a deliberate, hand-submitted Show HN performs far better than a scheduled blast.
What exactly does S2P prepare for Show HN?
It drafts a plain, specific Show HN title and a value-first body that explains the problem, what you built, and what you learned, framed from your GitHub release.
Can I edit the Show HN draft before posting?
Yes. The draft is a starting point. You rewrite the title and body to sound like a builder sharing, then submit it yourself and stay to answer questions.
