Settings reference

Most settings take effect as soon as you change them; there is no Save button. They are kept in plain JSON files in Revue's config folder, so you can also back them up, sync them or edit them by hand (see Files, sync and settings for one computer).

Open Settings#

• Press Ctrl+, (Cmd+, on macOS), or
• click the gear button (Settings) in the title bar, or
• click the Settings tab once it's open.

Settings opens as a tab in the main window. The sidebar lists its sections; with no text field focused, j / ↓ go to the next section and k / ↑ to the previous one. Middle-click the Settings tab to close it.

A warning triangle on the Settings tab or gear means some repositories you work with have no local clone set (see Repository sections).

Shared or kept on this computer#

Your settings are shared with your other computers when you sync Revue's config folder. Some cards have a small Shared / This computer switch in their title. Click it to keep that card's settings on this computer only: other computers keep their own value, and this one never sends its value to them. Click again to share it again (this computer's value then becomes the shared one).

Cards with the switch: Theme, Density, Language, Focus mode, Text, Default apps, Slack (under Apps), Language servers, Updates and a repository's Local clone.

Three settings are always kept on this computer, whatever the switches say: the token store switch (Where tokens are kept) and the clone folders (Where repositories are cloned).

Advanced: how the switch works

• Shared settings are in settings.json in the config folder; settings kept on this computer are in settings.local.json in the data folder, which is never synced. The switch's tooltip shows the exact path.
• The switch moves whole JSON keys. For example Text moves ui_font, code_font, text_size and code_text_size together, and Local clone moves local_repos, the clones of every repository at once.
• credential_store, clone_folder and clone_folders are only ever read from and written to settings.local.json. If another computer's settings.json has them (written by hand), they are ignored.
• The merge rules are on Files, sync and settings for one computer.

Appearance#

How Revue looks. Details and guides: Themes, fonts, focus mode and languages.

Advanced: theme keys

• The Theme card's switch moves dark, dim, follow_system, theme_dark and theme_light together.
• dim is from before themes had names. Revue keeps it in step when you pick Revue Dim.
• A theme id that isn't known (for example an imported theme deleted on another computer) falls back to Revue Dark or Revue Light.
• Imported color and code themes are files in the config folder (color-themes/, code-themes/), so they sync with it.

Behavior#

Notifications#

Desktop notifications, shown by the system while Revue runs, when something happens to a pull request that concerns you: "alice approved acme/web#42" with the pull request's title. Clicking one opens its pull request in Revue (on macOS the notification can't be clicked through). Never for what was there when Revue started, for what you did yourself, twice for the same thing, or for the pull request on screen in the focused window. Not in the browser version. Kept on this computer only (notifications in settings.local.json).

Where they come from lists your accounts:

• GitHub and Forgejo: their notifications, read with the pull request list (every minute and a half; GitHub's minimum interval is respected and an unchanged answer doesn't count against its rate limit). Only a pull request whose notification changed is read again. Clicking a notification marks it read on the service too.
• Bitbucket has no notifications to read: Revue compares the pull request list between its updates. It tells review requests, approvals, requested changes and failing checks, but not who approved, nor comments or merges.
• A sign-in that can't read notifications says so there, and gets the same as Bitbucket until it can: on GitHub a fine-grained token (they can't read notifications; Revue's own sign-in and a classic token with the repo or notifications scope can), on Forgejo a token without the read:notification scope (sign-ins made before Revue asked for it). Sign in again under Accounts, then click Check again.

The system must show notifications: on Linux a notification daemon (most desktops have one), on Windows notifications allowed for Revue, on macOS for Script Editor (which shows them for Revue).

Apps#

What Revue opens things in. More: Clones, worktrees and opening in your tools and Links and opening from anywhere.

Language servers#

Go to definition and Find references in the Code tab work without installing anything. Language servers make them more precise. Full guide: Language servers.

Advanced: language server keys

• A server with no entry in lsp_choices is off. An entry without "off": true is on.
• args empty means the server's usual arguments.
• Which servers suit a repository is detected once per repository and kept in settings-cache.json (detected_language_servers, detected_reasons), on this computer only. Servers stopped by hand in the Code tab are kept there too (stopped_servers, by checkout folder).
• Per-repository choices are in repo_servers (see Repository sections).

Accounts#

Sign-ins to GitHub, Bitbucket Cloud, Forgejo (Codeberg, Gitea), Jira and Slack. How to sign in to each: Accounts and signing in.

Slack messages#

Who people are on Slack and what Revue posts there. Without a connected Slack workspace, this section only says so, with Connect Slack in Accounts. Full guide: Slack.

The last channel picked per repository is remembered in slack_messages.channels.

Diff#

Defaults for a newly opened pull request. The diff toolbar (and its keys) changes them for the open pull request. More: Reviewing the diff.

Remembered from the diff toolbar#

These have no card in Settings. Revue remembers them when you toggle them in a diff, for every pull request:

Ignored files#

One list of patterns for generated files, lock files, snapshots and the like. Matching files start collapsed in diffs (one click expands them), and Find in Files skips them unless you tick Include ignored files.

Advanced: pattern rules and the default list

• A plain name matches in any folder; a path with / matches from the repository root; * and ** are wildcards.
• The default list: package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock.yaml, bun.lock, bun.lockb, deno.lock, Cargo.lock, go.sum, flake.lock, poetry.lock, uv.lock, Pipfile.lock, pdm.lock, composer.lock, Gemfile.lock, mix.lock, packages.lock.json, pubspec.lock, Podfile.lock, Package.resolved, *.min.js, *.min.css, *.map, *.snap, __snapshots__/**, dist/**, build/**, out/**, .next/**, *.generated.*, *.g.dart, *.pb.go, *_pb2.py, *.designer.cs, *.import, *.uid, .godot/**, *.meta, *.unity, *.prefab, *.asset.
• When a new Revue version adds patterns to the default list, they're added to your saved list once (ignored_defaults tracks this). Patterns you removed later stay removed.

Ignored repositories#

Repositories you ignored are left out of the Repositories and Projects pages, the Ctrl+K list (Cmd+K on macOS) and the Settings sidebar, and their pull requests are left out of the pull request list and its counts. Ctrl+K still finds them when its search asks the services.

Storage#

What Revue keeps on disk, and where. Paths and syncing: Files, sync and settings for one computer.

About#

About is pinned to the bottom of the sidebar.

Repository sections#

Below the fixed sections, the sidebar lists REPOSITORIES: the ones with open pull requests and the ones you set something up for, grouped in folders like on the Repositories page. Detect clones for all searches your home folder for clones of the listed repositories, then lets you choose which to set. A repository without a clone shows No local clone set.

Each repository's section has these cards:

Only in settings.json#

A few things are kept with the settings but changed elsewhere in the app:

• favorite_prs, favorite_repos, favorite_projects: what you starred (f in the lists).
• untracked_accounts: the accounts with Track off.

What Revue remembers rather than what you set (open and pinned tabs, recent items, the list's filters, panel widths) is in state.json, not settings.json.

All settings.json keys#

Every key, alphabetically. "File" says where it lives: shared = settings.json (or settings.local.json when switched to This computer), local = always settings.local.json, state = state.json, cache = settings-cache.json. A key that's missing takes its default.

Advanced: editing settings.json by hand

• Revue notices when a settings file changes on disk (edited by you, or synced from another computer) and reads it again; no restart needed.
• If settings.local.json doesn't fit (a wrong type, say), Revue ignores it and uses the shared settings alone. A shared file that can't be read gives the defaults.
• Revue rewrites settings.json when it saves, so your own formatting there isn't kept. settings.local.json is only rewritten when what it holds changes.
• Keep the JSON valid. A settings.json Revue can't read counts as empty, and the next change you make in the app saves the defaults over it.
• Keys of state.json or settings-cache.json found in a settings file (saved by 0.17 or older) are moved to their own files the first time Revue reads them.