hush
Open Hush

Guides

How to follow GitHub notifications in an RSS or Atom reader

GitHub has no documented feed for your notifications inbox. Use the Atom feeds for releases and commits, the REST API, or a private Hush feed of your Needs you list, FYI, or a saved view.

Short answer

GitHub does not give your notifications inbox an RSS or Atom feed. It has unsupported Atom feeds for public activity, such as https://github.com/OWNER/REPO/releases.atom, and a REST API for notifications. Hush gives each inbox tab and each saved view a private Atom feed that you can paste into any feed reader.

What GitHub has

Atom feeds for public activity

Add .atom to some GitHub addresses to get a feed:

Address Feed of
https://github.com/OWNER/REPO/releases.atom The releases of a repository.
https://github.com/OWNER/REPO/commits/main.atom The commits on one branch.
https://github.com/USER.atom The public activity of a user.

A GitHub Docs maintainer wrote that these feeds are "intentionally undocumented and unsupported", so they can change. They do not include your notifications: no review requests, mentions, or CI results.

If you only want to know about releases, you do not need a feed: open the repository's Watch menu, choose Custom, and select Releases.

The REST API

The notifications API (GET /notifications) lists your notification threads. A small script can turn it into a feed, but you must run it, keep a token for it, and decide what each entry says.

Get a feed of your notifications with Hush

Hush can make a private Atom feed of any inbox tab: Needs you, FYI, Needs you + FYI, or one of your saved views.

  1. Sign in at app.hush-gh.com.
  2. Go to Settings → Inbox → Views and feeds.
  3. Choose the feed button (the RSS icon) next to a tab. Hush makes the feed and copies its address.
  4. Paste the address in your feed reader, a Slack feed app, or a script.

Hush shows the address only once: it keeps only a hash of it. If you lose it, make a new one.

Keep the address secret. Anyone who has it can read the feed, with no sign-in. If it leaks, open the feed button's menu and choose New feed URL or Turn off feed. The old address stops working at once.

What each entry has

  • The title: what happened and the title of the thread, such as "CI failed on your PR: Fix login".
  • The link: the thread's main action on GitHub, such as the files to review.
  • The repository, the number, why GitHub notified you, and the newest comment.
  • The author, and the list (action or fyi) as a category.

The feed has the threads that are in the tab now, newest first. A thread that you mark Done leaves the feed. When a thread has new activity, its entry gets a new ID, so most readers show it as new again. The feed can be up to 2 minutes old. See Feeds.

A feed for one topic

Make a saved view, then make a feed of it. For example, a view of releases, and a view of failing CI:

{
	"views": [
		{ "id": "releases", "name": "Releases", "base": "inbox", "query": "type:release" },
		{ "id": "ci", "name": "Broken CI", "base": "action", "query": "needs:fix-ci" }
	]
}

The feed of a view stops working when you delete the view.

When to use what

  • Releases of projects that you use: GitHub's releases.atom. It needs no account.
  • Your own notifications, sorted, in a reader: a Hush feed of Needs you or a saved view.
  • Push to your phone in place of a reader: see push notifications for review requests and CI.

Sources

Last checked: 3 October 2026.