Start
Hush docs
How Hush sorts your GitHub notifications, and how to make it work your way.
Hush reads your GitHub notifications and sorts them into what needs you and what is only FYI. It follows whose turn it is on every pull request and issue that involves you, sends a push only when something waits on you, and lets you act on GitHub (approve, comment, merge, mark Done) without leaving your inbox.
The idea in one minute
- Needs you is short on purpose. A thread is there only when you are the next person who must act: your review is requested, CI fails on your PR, someone replied to you, your approved PR is ready to merge. See what needs you.
- FYI is everything else: team mentions, watched repositories, bots, merged and closed work.
- Whose turn is one set of rules for the inbox and the Pull requests and Issues tabs. An item is in Needs you exactly when it is “Your turn”.
- Hush follows up by itself. When you approve, push a fix, or reply, the thread leaves Needs you with a note such as “✓ You approved”. When it needs you again, it comes back.
- Everything is a setting. Rules, views, sections, menus, and keys are in one settings.json that you can edit, export, and share.
Where to start
- New to Hush: Getting started.
- An org's repositories are missing: GitHub access.
- Too much noise, or not enough: Rules and Notifications.
- You like the keyboard: Keybinds.
- You want every option: settings.json.
For agents
Every page is also plain Markdown: add .md to its address (for example /docs/settings.md). /llms.txt lists the pages, and /llms-full.txt has all of them in one file. To change a user's setup, read For agents first.