Twigest
Twigest

GitHub to email

GitHub digest: release notes without the notification noise

Add a public repository with the gh:owner/repo shortcut. Twigest reads that repository's public releases feed, keeps the release link and folds the entries into the same scheduled briefing as your other sources.

No card for your preview · Card-required 7-day trial

Twigest sources page showing the source shortcuts including gh:owner/repo for GitHub releases

One shortcut, no token

Type gh:owner/repo (or paste the repository URL) on the RSS & YouTube page. Twigest reads the public releases feed GitHub exposes, so there is no token, app or OAuth consent to manage.

Release notes keep their link

Each entry in the briefing links to the release page, so you can read the changelog yourself instead of trusting a summary.

A developer briefing, not a firehose

Pair repository releases with Hacker News, engineering blogs as RSS feeds, subreddits like r/programming and the accounts you follow on X. One email instead of five notification streams.

On your schedule

Daily, weekdays or specific days at your delivery time. Email everywhere; Telegram and Slack on Pro.

How it works

  1. 1Add the repositoryEnter gh:owner/repo, or paste https://github.com/owner/repo. The shortcut is normalised to the repository's public releases feed.
  2. 2Releases are collectedNew releases are read on Twigest's collection cycles with their titles, links and publish dates.
  3. 3The briefing is assembledEntries are scored and summarised together with your other sources for the delivery window you chose.
  4. 4Delivered by emailEmail on every paid plan; Pro adds Telegram and Slack, and outgoing webhooks can push digests into your own tooling.

What it is not

  • Releases, not everything: Twigest reads the repository's public releases feed. Issues, pull requests, commits, discussions and GitHub Trending are out of scope for this source.
  • Public repositories only: private or internal repositories need credentials and are not collected.
  • Not real-time: releases reach the next scheduled briefing, not the second they are published.

Questions

How do I get GitHub releases by email?

Add gh:owner/repo as a source under RSS & YouTube. Twigest reads the repository's public releases feed and includes new releases in your scheduled digest.

Do I need a GitHub token or app?

No. The shortcut points at GitHub's public releases feed, so there is nothing to authorise and no API key to rotate.

Can I follow several repositories?

Yes. Each repository counts as one source: Starter allows 10 sources, Pro 30, and higher plans more.

Does it cover GitHub Trending or issues?

No. This source is deliberately limited to releases of the repositories you name; GitHub does not publish those other surfaces as feeds, and Twigest does not scrape them.

Can I mix it with Hacker News and blogs?

Yes, and that is the usual setup: release notes for what changed, Hacker News and subreddits for the discussion, RSS feeds for the long-form writing.

How much does it cost?

Starter is $9/month or $90/year (10 accounts, 10 feeds, 3 keywords, 3 topics, daily digests). Pro is $19/month or $190/year (30 accounts, 30 feeds, 10 keywords, 5 topics, plus Telegram and Slack delivery). Both include a card-required 7-day trial; new users can see one preview without a card.

Try it with your own sources

One preview without a card, then a card-required 7-day trial.