Skip to content
GitTree
العربية
Files and tools

Find actions with the command palette

The command palette runs any GitTree command by typing part of its name, and also jumps to branches, commits, files and open repositories. Press Ctrl+Shift+P (⌘⇧P on a Mac), type, and press Enter.

FreeUpdated

Works in GitTree Free: every local Git feature, once you are signed in.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. Search modes
  6. If something goes wrong
  7. Questions
  8. Related

Before you start

  • Most commands act on the repository in the current tab, so open one first. App-wide commands (Preferences, new tab, zoom) work anywhere.
  • The palette runs commands inside GitTree. It is not the docs search on this site.

Where to find it

  • Press the shortcut below from anywhere in the window.
  • Or open Help in the status bar at the bottom and choose Command Palette….
ActionmacOSWindows and Linux
Open the command palette⌘⇧PCtrl+Shift+P
Show every keyboard shortcut⌘/Ctrl+/
Open the Feature Guide⌥HAlt+H

Steps

  1. Open the palette

    Press Ctrl+Shift+P (⌘⇧P on a Mac). The Command Palette opens with > already typed: it is searching commands, in the repository named under its title.

    Animation: the command palette opens, “branch” is typed and the matching branch commands are listed with their shortcuts
    Typing “branch” lists every command about branches; the highlighted one runs on Enter.GitTree interface with a demonstration repository.

  2. Type part of the command’s name

    Type any word of it, such as branch, stash or zoom. Results show each command’s area and, when it has one, its shortcut, so you learn the shortcut as you go.

  3. Choose with the arrow keys and press Enter

    Move with ↑ and ↓ and press Enter, or click a row. A command that cannot run right now says why (for example, it needs a selected commit). Escape closes the palette without running anything.

  4. Search something other than commands

    Replace > with another prefix to change what the palette searches: @ for branches and tags, # for commits by message or SHA, : for files, and repo for the repositories open in your tabs.

Expected result

The command runs exactly as it would from its button or menu, with the same confirmations. Commands you ran recently are listed first the next time you open the palette with an empty search.

Search modes

What each prefix searches
TypeSearchesExample
>Commands>zoom
@Branches and tags (refs)@main
#Commits, by message or SHA#fix typo
:Files of the repository:src/main.ts
repo Repositories open in your tabsrepo web

If something goes wrong

The shortcut does nothing

Another app or your system may use the same keys, or the binding was changed. Open the palette from Help › Command Palette… in the status bar, then check the binding in Preferences › Keyboard Shortcuts.

A command is listed as unavailable

It needs something the tab does not have yet: an open repository, a selected commit or file, or a connected account. The reason is shown next to it.

“No matches”

Check the prefix: with > the palette searches only commands. Remove it, or type the prefix for branches (@), commits (#) or files (:).

Questions

Is it like the command palette in VS Code?

Yes, the idea and the default shortcut are the same: type what you want to do instead of looking for the button.

Related