GitHub.
Turn every release into content — and publish blog posts straight to your repo.
what it does
GitHub connects two ways. Publishing: ReachPill commits finished blog articles as clean markdown to a repository you choose, so your static site or CMS build picks them up. Release updates: when you ship a release, ReachPill reads the release notes and turns them into on-brand posts across your channels — and, if you like, a blog article — automatically, on your normal review workflow. It compares the new version against the last, leads with what actually improved, and won't re-announce what already shipped. None of it requires handing over your codebase.
how it connects
Pick how ReachPill sees your releases
Public repo: paste the URL and ReachPill reads your public releases feed — nothing to grant. Private and hands-off: install the read-only GitHub app and choose exactly which repositories it can see. Or keep every key yourself: drop a short GitHub Action into your repo (or point a repo webhook at ReachPill) so your release notes are pushed to us, with no standing access at all.
Choose your channels and cadence
Set which social channels a release should post to, and whether to also draft a blog article. Leave autopilot on and releases post themselves; turn it off to generate on demand.
Review the first one, then relax
Your first release always waits for your approval, so you see a real post before anything goes live. After that, releases publish on their own — or keep the review step on every one, your choice.
what you get
- Product updates announced the moment you ship, with zero extra steps
- Posts that lead with what improved — version-compared, never a raw changelog
- No codebase access required: public feed, a push-based Action, or a read-only, repo-scoped app
- Blog articles committed as clean markdown straight to your repository
- Every post on-brand and on your normal review workflow