Repositories and branches

The Repositories page#

Open it with Repositories in the title bar, or press Ctrl+G (Cmd+G on macOS).

The page lists one signed-in account's repositories at a time, grouped by organization (on Bitbucket, by workspace and project). Repositories you opened recently come first, marked Recent; the rest follow, most recently active first. Each row shows the repository's description, default branch, a lock for private ones, and when it was last updated.

• Click a row (or select it and press Enter) to open the repository in a tab of its own.
• Click a group's header to fold or unfold it. Fold all groups and Unfold all groups sit next to the filter. Groups start folded each time Revue starts.
• With more than one account, or once you've starred a repository, tabs appear next to the title: Favorites first, then one per account.
• Refresh (Ctrl+R, Cmd+R on macOS) lists everything again and tells you what's new.

Finding a repository#

Type in the filter (Filter repositories, or type owner/repo or a link…, or press / to jump there). The filter is forgiving: case and accents don't matter, and the letters only need to come in order.

• After you type two characters, Revue also asks the service, so repositories past the pages loaded show up too (searching the service… at the bottom).
• Type owner/repo or paste a repository's web address to open a repository that isn't listed at all. It shows first in the list, marked Open.
• At the bottom, Load more lists the account's next repositories.

Advanced: what each service lists

Service	Listed	Grouped by
GitHub	Repositories you own, collaborate on, or that belong to your organizations, last pushed first	Owner
Bitbucket Cloud	Each of your workspaces' repositories, last updated first	Workspace · project, with the project's key
Forgejo, Codeberg, Gitea	Repositories you own or contribute to, last updated first	Owner, with a tag naming the server

• Pages are 50 repositories each (per workspace on Bitbucket).
• Repositories of the pull requests in your lists are included even when the account's listing doesn't have them.
• On Bitbucket, a project's key (such as ABC) shows on its group. When a connected Jira site has a project with that key, the key links to it (Open the ABC project in Jira).
• A pasted address of github.com or bitbucket.org names that service; any other server is taken as a Forgejo or Gitea server. A bare owner/repo is tried on every service you're signed in to.
• The Recent list keeps the last 12 repositories you opened.

Favorites#

Star a repository with the star at the end of its row, or select it and press f. Starred repositories of every account are listed together under the Favorites tab, in the order you starred them.

On the Favorites tab, move a repository with the arrows that appear on hover, or with Alt+↑ and Alt+↓. Starring and unstarring never scrolls the list away from what you were looking at.

Ignoring a repository#

The crossed-out eye on a row ignores the repository: it disappears from the lists, and so do its pull requests. Once something is ignored, an Ignored button appears at the top: turn it on to see the ignored repositories (dimmed, tagged Ignored) and click the eye again to stop ignoring one. You can also manage them in Settings → Ignored repositories (see Settings).

Cloning from the list#

The download icon on a row clones the repository, signed in as the account it's listed for. Once cloned, the icon turns into a folder whose tooltip says where. Revue then uses that clone for worktrees and for the Code tab. See Clones, worktrees and opening in your tools.

Keys on the Repositories page#

Right-click a row for Open in background tab (a tab of its own, without leaving the list), Copy link and Open in browser.

A repository's tab#

A repository opens in its own tab, titled owner/repo · branch. The header shows the repository, its description, and these controls on the right:

• The branch button (it shows the branch name): the branch whose history is listed. Click it to switch to another; the default branch comes first, then branches you committed on last. Press Enter to take the first match.
• Open buttons for your editor, terminal and file manager. They open your local clone, or, when you have none, the source at the commit on screen (downloaded first). See Clones, worktrees and opening in your tools.
• Refresh (Ctrl+R), Repository settings (ticket links and the local clone for this repository), and Open on GitHub / Bitbucket / Forgejo (o).

Below the header are five tabs, also reachable with the number keys:

There's one tab per repository and branch. If another tab already shows the branch you switch to, Revue goes to that tab instead. Close a repository tab with Ctrl+W (Cmd+W on macOS); right-click it to pin it so it comes back next time.

Commits: a branch's history#

The left side lists the branch's commits, newest first, with lanes showing merges and branches splitting off, like git log --graph. Branch names sit on the commits they point at, and merge commits are tagged Merge.

• Click a commit to see its changes on the right.
• Shift+click another to see the whole range: every change from the older one to the newer one, both included.
• Step through commits with j / k or the arrow keys. Stepping past the bottom loads older commits; so does Load older.
• Filter by message, author or hash… narrows the list (press /). Paste a commit hash that isn't loaded yet and Revue fetches that commit for you.

Above the diff, the bar says what you're looking at: the commit's title, author, date and short hash (click the hash to copy the full one), and its message. For a range, it shows how many commits and their hashes.

The diff works like a pull request's (see Reviewing the diff), without the review parts:

• s switches Split / unified.
• b shows or hides the changed files beside the diff (remembered).
• n / p (or Ctrl+↓ / Ctrl+↑) jump to the next or previous change.
• Click a file's header to fold it. Images, fonts and Markdown show previews.
• The code icon, Browse the code at this commit, opens the Code tab at that commit.

Right-click a commit for Copy link, Open in browser, Copy commit message, Copy full hash and Copy short hash.

Advanced: history details

• History loads 50 commits at a time.
• While the filter has text, the graph lanes are hidden (the matches aren't a continuous history), and the count reads "N of M loaded". When nothing matches but older commits exist, Revue says so: load older commits to search further.
• A hash is looked up on the service once it is 7 to 40 hexadecimal characters long.
• The graph shows up to 8 lanes in Commits; wider histories are clipped so the text keeps its room.
• The repository's first commit has nothing before it, so it has no diff.
• Files matching your auto-fold patterns start folded, and ignored files are withheld until you ask for them, as in pull requests (see Settings).

Graph: every branch at once#

The Graph tab shows the history of all branches together, newest first, with up to 32 lanes and every branch's name on its tip. It reads each branch a page at a time, so the bottom line says how much is in ("120 commits · 8 of 12 branches"). Load older reads further back.

Click a commit to select it, and double-click it to see its diff in Commits.

Branches#

The Branches tab lists every branch with its last commit, author and date. Branch names with slashes nest into folders (feature/login sits in a feature folder). Folders that hold your branches, or the current one, start open.

• Click a branch to see what it changes against the default branch: exactly what a pull request from it would show.
• Double-click it, or click its history icon, to switch to it: its history then fills Commits. The branch whose history is listed is tagged Current; the default branch is tagged Default.
• Filter branches… narrows the list (press /).

Sorting and "only mine"#

Next to the filter:

• Sort picks the order: Recently updated (newest last commit first, the default), Oldest first (longest untouched first), Name (A to Z), or Author (by the last commit's author). The default and current branch always stay on top.
• Only my branches (the person icon) shows only branches you committed on last.

Both choices are remembered.

Advanced: who counts as "you"

The services only tell Revue who made a branch's last commit, not who created or pushed it. So "your branch" means a branch whose last commit is yours, matched by any of:

• your account's login or profile name on the service,
• the name or email your local clone commits with (git config user.name and user.email).

A branch someone else committed on after you isn't yours here. If none of these are known, the list says Who you are isn't known here: sign in, or set the clone's git user.

A branch's pull request#

When you pick a branch, the bar above its diff says what it is compared with ("feature against main") and shows its pull request, if it has one: open, draft, merged or closed. Click it to open the pull request in Revue.

On the row itself:

• A branch with an open pull request shows its number (#42). Click it to open the pull request.
• A branch without one shows the Open pull request icon. The same button is in the bar above the diff. See Opening a pull request.
• The bar's History button switches to the branch's history in Commits.

If your local clone is checked out on a branch that has no pull request yet, a line at the top of the list says so ("Your checkout is on fix-login") with an Open pull request button, or Push and open pull request when the branch isn't pushed yet.

Right-click a branch for Copy link and Open in browser, plus Open the pull request in a background tab, Copy the pull request's link and Open the pull request in the browser when it has an open one.

Advanced: when "Open pull request" shows

A branch offers to open a pull request only when:

• it isn't the default branch,
• it has no open pull request, and Revue has finished listing the repository's open pull requests (it looks through up to the same number of pages as a pull request stack does),
• the repository was loaded from the service (not from your local clone).

Only pull requests from the repository's own branches count: a fork's branch with the same name isn't this one. The default branch has no diff here: pick another branch, or look at its commits under Commits.

Pull requests#

The Pull requests tab lists the repository's pull requests: each with its state, title, number, author, branch and last update. Click one to open it.

• Search pull requests: title, #number… searches as you type.
• State: Open (the default), Merged, Closed or All.
• Mine shows only yours; Review requested only those awaiting your review.
• Show drafts includes or hides drafts.
• Sort: Recently updated, Newest or Oldest.
• At the bottom, page through the results and pick how many per page (10, 20 or 50, shared by all paged lists).

The filters are kept per repository until you quit Revue. When nothing matches, Show all pull requests resets them.

Right-click a pull request for Open in background tab, Copy link, Open in browser and Copy Revue link (see Links and opening from anywhere).

Per service

• Review requested isn't available on Forgejo, Codeberg and Gitea: their API can't list a repository's pull requests by reviewer.
• Closed means closed without merging (declined, superseded on Bitbucket).
• The total ("57 open") shows when the service reports it.

Code#

The Code tab shows the repository's source at the commit on screen: the commit or range picked in Commits or Graph, or the branch's latest commit. With a local clone, Revue reads the code from it (as a worktree) instead of downloading it.

• Ctrl+P (Cmd+P) goes to a file, Ctrl+F finds in the open file, and Ctrl+Shift+F finds in all files.
• A file's History can open another commit here, with the file open.

Everything about the Code tab is on Browsing code.

When the service can't load a repository#

If the service doesn't load a repository (it's down, or your access changed) and you've set a local clone for it, Revue reads the branches, history and code from the clone instead. A banner says so: Showing your local clone at … : GitHub didn't load this repository. The Pull requests tab and checks need the service and stay off. Try again asks the service again.

Without a clone, the tab shows the error with Retry and Set a local clone, which opens the repository's settings.

Projects#

The Projects page (in the title bar once a Jira account is connected, or Ctrl+J, Cmd+J on macOS) lists each Jira account's projects, with the repositories that belong to each. Click a repository to open it.

A repository is listed under a project when:

• it's filed in the Bitbucket project with the same key,
• its ticket link rules link that project's keys (tagged link rule), or
• its open pull requests mention that project's tickets (tagged from PRs).

It works like the Repositories page: a filter, folding projects (Fold all projects, Unfold all projects), Hide empty projects (on by default), stars with a Favorites tab across every Jira account, Open in Jira on each project, and the same keys. More on Jira in Jira.

Guide: Look at what a branch changes#

1. Press Ctrl+G and open the repository.
2. Press 3 for Branches.
3. Type part of the branch's name in the filter.
4. Click the branch: its changes against the default branch appear on the right.
5. To see its commits one by one, double-click it, then press 1.

Guide: Review a range of commits#

1. Open the repository and stay on Commits.
2. Switch branch with the branch button at the top right, if needed.
3. Click the oldest commit you want.
4. Shift+click the newest one: the diff shows everything in between.
5. Press 5 to browse the code as it is at the newest commit.