The Repository List
The list on the left is where you choose what to look at. Arrow to an
entry and press Enter, or double-click it. Typing a letter
jumps to the next entry starting with it, except F, which
adds the selected repository to favorites or removes it (see Favorites).
It is in this order:
- ★ Favorites, with how many you have, for example “★ Favorites (12)”. See Favorites.
- Activity: your GitHub feed. See Activity.
- Starred Repositories: the repositories you have starred, with how many, for example “Starred Repositories (7)”. See Starred and Watched Repositories.
- Watched Repositories: the repositories you watch, with how many.
- Notifications, with how many are unread, for example “Notifications (12 unread)”. See Notifications.
- My Work: open issues and pull requests that need you, with how many once it has loaded. See My Work.
- My Organizations: the organizations you belong to, with how many, for example “My Organizations (3)”. See My Organizations and Shared With Me.
- Shared With Me: other people’s repositories you have been made a collaborator on, with how many. It is only there when there is at least one.
- Your saved searches, each marked with a magnifying glass, for example “🔍 NVDA braille bugs”. See Saved searches.
- Repositories you opened by address, each marked with a pin, for example “📌 nvaccess/nvda — NVDA, the free and open source screen reader”.
- Your own repositories, most recently pushed first, each followed by its description, up to 100.
The first seven are always there, so the same keystrokes from the top of the list always reach them. The first four are where they were before Notifications, My Work and My Organizations arrived. When the list first loads, the status bar says how many repositories it found: “Loaded 42 repositories. Select one to view issues and PRs.”
The notification, starred and watched counts are asked for once the
list is up, so they appear a moment after the names, without moving you
from the entry you are on. If GitHub can’t be asked, the entry shows
just its name rather than a number that might be wrong. Opening Starred
or Watched, or pressing R in it, brings its count up to
date, so a repository you starred on the web since GHManage started is
counted then.
Opening a repository shows its Issues & PRs. Use
Ctrl+2 through Ctrl+0 to reach its other
views.
Opening a repository or a GitHub address
File → Open Repository or Address…
(Ctrl+Shift+O) opens any repository on GitHub, yours or
not, without cloning it, and goes straight to most things inside one.
Type or paste:
owner/name,https://github.com/owner/nameorgit@github.com:owner/name.gitto open the repository on its issues and pull requests. It is added to the repository list with a pin, where it stays between sessions until you remove it.The address of an issue or pull request (
…/issues/12,…/pull/12,…/pull/12/files) to open the repository’s issues with that one selected. When it is not among those loaded, closed say, it is fetched and added, as Go To Issue does.A commit (
…/commit/<sha>) to open the commits with it selected. A commit that isn’t among the default branch’s latest is fetched and shown first.A release (
…/releases/tag/v1.2), a workflow run (…/actions/runs/<id>) or a branch (…/tree/<branch>) to open the releases, the workflow runs or that branch’s commits.A list (
…/releases,…/pulls,…/actions,…/labels,…/branches,…/tags,…/commits) to open that view.A branch’s history (
…/commits/<branch>) opens that branch’s commits; a workflow file (…/actions/workflows/ci.yml) opens Workflows.
Any other address inside a repository, a file, the wiki or a
discussion say, opens the repository on its issues, and the status bar
says GHManage has no view for that page. A branch whose name has a
/ in it can’t be told apart from a folder in a
…/tree/ address, so that opens the repository too. Only a
repository’s own address pins it: a link from an email to an issue, a
file or anything else in a repository opens without adding to your
list.
Addresses can be pasted as they come: wrapped in
<…> or brackets, followed by a full stop or comma, in
any mix of upper and lower case. Only github.com is read; addresses on
other GitHub hosts, gists, raw files and the API get the “Couldn’t read
that” message.
When the clipboard already holds a GitHub address, the box starts
with it filled in, so opening a link you have copied is
Ctrl+Shift+O and Enter. If you copied a whole
sentence or paragraph, the first GitHub address in it is the one
offered.
A person’s or organisation’s address says so on the status bar; GHManage has no profile view. An address it cannot read at all gets “Couldn’t read that. Use a github.com address or OWNER/NAME.”
Removing a repository from the list
Delete in the repository list, or File → Remove
from List, takes the selected repository out of the list. It
never deletes anything on GitHub. The status bar confirms it, for
example “Removed owner/name from the list.”
That works for every repository in the list: ones you opened by address, and your own. GitHub still lists your own repositories each time the list loads, so GHManage keeps a note of the ones you removed and leaves them out. When some are left out, the status bar says how many when the list loads, for example “Loaded 20 repositories (3 hidden).”
After a removal you are on the row that took its place, so you can go on down the list.
To put one back, choose File → Hidden Repositories….
It lists the repositories you have removed: move to one and press
Enter (the Show Again button) to put it
back in the list. The window stays open for the next one, and closes on
its own when none are left; Escape closes it. Opening a
hidden repository by its address with File → Open Repository or
Address… brings it back too.
The entries at the top, organizations included, are always there. A saved search is removed the same way, but it can’t be brought back, so GHManage asks first.
Forks
GitHub turns issues off on a fork by default, and the issues and pull requests that matter live on the repository it was forked from. So when you open a fork, its Issues & PRs and Labels come from that upstream repository, and the status bar says so, for example “you/nvda (issues from upstream nvaccess/nvda)”. Pull requests opened only within the fork itself are not shown. Branches, commits, releases, workflows and the rest are the fork’s own.