GitHub

One extension, five palettes, one sign-in: your pull requests, issues, repositories and notifications as rows, and GitHub's own search typed into the panel. Enter opens the thing on GitHub; the other actions copy, check out, merge, close or mark read without leaving the keyboard.

Pull Requests lists yours (is:open author:@me), the ones waiting on your review (review-requested:@me), and yours merged within merged_days, sectioned Mine, Review requested, Merged; the filter dropdown has the same three plus All and Hidden. The row is the title with owner/repo #n under it, a state dot (green open, grey draft, violet merged, red closed) and tags for the checks (checks ✓ / ✗ / …), the review decision (approved, changes requested, review), draft and conflicts, then the updated date. The palette opens with the detail pane: the body, the latest comments and reviews, and under them the repository, author, branch, size, every check by name, who approved, who asked for changes, reviewers, labels and dates (fetched when the cursor rests).

Issues is what is assigned to you, mentions you, or you opened, in that order, an issue in two lists listed once. Rows carry the first two labels, the comment count and the updated date; the pane the body, the latest comments and the milestone. Create issue at the top is a form (repository, title, body) whose submit opens the new issue.

Mute (cmd+m on a pull request or issue row, m in the bar popovers) keeps one out of every list, the bar counts and the popovers until you unmute it. Ignore until it changes (cmd+shift+i on a row, i in the popovers) does the same until anything about it moves: an update (a push, a comment, a review, an edit), its checks, its review decision or its mergeability, which then bring it back by themselves. The Hidden filter of either palette lists both, sectioned Muted and Ignored until it changes, with Unmute or Show again on the row. It is kept in pal's storage, not on GitHub, and a hidden thing keeps its notifications. Either ends on its own once it has nothing left to do: an id a fetched list shows merged or closed is dropped on that listing, and one no list has carried for thirty days is dropped too, each drop logged.

Repositories is yours (owner or collaborator, by push date), your default_org's recently pushed, and your starred ones, sectioned so. Rows show the description, tags for private, archived and the language, the stars and the push date; the pane adds forks, open issues, the default branch, the clone url and the local clone when one sits under repos_root. Create repository is a form (owner, name, description, private).

Notifications is every unread thread, sectioned by reason (Review requested, Mentioned, Assigned, Your threads, Comments, State changed, CI, Security, Subscribed), newest first inside one; the first row is the unread count. Enter marks the thread read and opens it, so the count is honest when you come back. The pane shows the pull request's or issue's text and latest comments behind a thread about one.

Search GitHub takes GitHub's syntax as you type: free text, repo:owner/name, is:pr, author:login, label:bug. Results come nearest first, each once: Involved (involves:@me), Your organisations (your account and your organisations), Repositories (yours first), Everywhere, Users. A query naming repo:, org: or user: skips the organisations tier. Your cached pull requests and issues are matched loosely too, so a typo still finds them; they show at once, at the top of Involved. Filters Everything, Issues and PRs, Repositories, Users. Each tier is its own request, sent together; a keystroke waits 300 ms for the next before asking, each tier's rows join below as soon as the tiers above them are in, and the search row's sweep runs until the last lands (about 2 s). Other people's pull requests come without the checks, review and conflicts tags, which GitHub computes per result; yours carry them from the cached lists.

Keyboard

Marked rows (⌘-click, ⇧-click for a range, ⇧↑/⇧↓) take every action above at once except Checkout branch, Open path and Mark all as read: several PRs or issues open in one go, the copies land one per line, mute, unmute, merge, close and mark ready go through them all (the question says how many). The PR, issue and notification popovers mark the same way: Enter opens each marked row, c copies them, m mutes (or, in notifications, marks read) them all, i ignores them until they change. Space in a popover previews the row under the cursor: the pull request's or issue's text and latest comments (a notification's too, when it is about one), with Enter and its c/m keys still working there.

Setup

Sign in one of two ways: install the gh CLI and run gh auth login (the extension asks gh auth token at most every five minutes), or set the token setting to a personal access token with repo, notifications and read:org (the config file holds a keychain: reference, never the value). With neither, each palette is one hint row saying how to sign in; Enter on it opens the token settings. A token GitHub rejects is the same row with GitHub's message.

Every request has a 10 s timeout. Pull Requests, Issues and Search are one GraphQL request each; Repositories and Notifications are REST with ETags, so a re-list that changed nothing costs no rate limit. The rows are kept in the extension's storage, so a restart still has them and an outage shows the last ones; while the rate limit is exhausted a hint row at the top says when it resets.

Settings, [extensions.github]:

prs item settings, [bar.items."github/prs".settings]:

Each bar item is hidden at zero; show = "always" under its [bar.items."github/<id>"] keeps the glyph on the strip anyway, muted, with an honest tooltip and the same popover (docs/config.md).

The bar item Pull requests is hidden at zero. When it has work, the strip is the bucket summary of your own pull requests: red blocked (conflicts, failing checks or changes requested), amber active (checks running or review required), green ready to merge, muted waiting. A review asked of you is someone else's work: it is in the popover's last section, and on the strip as a blue count only with review_requests. Its popover opens the same story: sections in that order, each row the PR title, owner/repo#n, the specific state badge and age. Six rows fit; the rest is "and N more in pal". ↑/↓ (or k/j) move the cursor, a click focuses a row, Enter opens it on GitHub, c copies its URL, r refreshes, and p opens the full Pull Requests palette.

The bar item Issues is hidden at zero. The strip counts assigned, mentioned and issues opened by you; the popover uses the same buckets in that order. Rows show the issue title, owner/repo#n, labels, comment count when present, and age. Six rows fit; the rest is "and N more in pal". ↑/↓ (or k/j) move the cursor, a click focuses a row, Enter opens it on GitHub, c copies its URL, r refreshes, and p opens the full Issues palette.

The bar item Notifications shows the unread count as a badge (hidden at zero), refreshed every five minutes and on show, wake and a network change. Its popover is the inbox at a glance: the unread threads grouped by repository (newest repository first, a count per repository), each with a colour rail for the subject's type (pull request and issue green, release blue, discussion violet, commit grey, checks amber, security red), its title, a badge for the reason GitHub gives (mention red, review violet, assigned blue, CI and state amber, security red, yours and subscribed grey, and the rest) and its age. Every thread is a row; the popover scrolls. The ring is the cursor: ↑/↓ (or k/j) move it, a click on a thread puts it there. Keys: Enter (or o) marks the thread read and opens it on GitHub, m marks it read and the list redraws with the count (with threads marked by ⌘-click, ⇧-click or ⇧↑/⇧↓, m marks all of them read at once), a (or ⌘⇧A) marks everything read and the popover reads "All caught up", p opens the Notifications palette, ⌘C copies the thread's URL. On a second account the title carries its name ("4 unread (Work)").

What it does not do

• Review from the panel: approving, commenting and requesting changes happen on GitHub; the pane only shows them.
• Repositories beyond yours, your organisation's recent ones and your stars: anything else is found through Search.
• Notifications older than what GitHub returns as unread; read ones are not listed.
• Checkout without a clone: Checkout branch needs the repository already cloned under repos_root and gh on PATH.

Platforms

macOS and Linux, the same on both. Open in editor uses code when it is on PATH, else the system opener on the folder.