The console

The console is for people who like to type Git commands. Open it with Console in the rail, or with Control and the backquote key (Control with `). It opens along the bottom of the window. Drag its top edge to change its height.

Typing commands

Typing git switch with suggestions, then git log drawn as a small graph

Type a command such as status, log or switch main. You can leave out git. Press Tab, or use the arrow keys and Enter, to take a suggestion. The suggestions come from the open repository:

You typeGitkeen suggests
The start of a commandCommands, each with a short description.
A - after a commandThat command’s options, each with a short description.
A place that takes a branchThe branches. For switch and merge, the current branch is left out.
A place that takes a fileThe changed files. After restore --staged, the staged files.
A place that takes a commitThe recent commits with their subjects, and the tags.
stash pop and similarThe stashes, with their messages.

The Up and Down keys bring back the commands you typed before in this repository. Command or Control with L clears the console.

Results as pictures

Gitkeen draws the result of these commands. Show raw output switches to Git’s own text.

CommandHow the result is shown
statusThe files in groups: conflicts, staged, not staged and untracked. Click a file to open its diff.
logA small graph with the branches and tags. Click a commit to select it in the main graph.
diff and showThe change in colour, with each file’s code colours.
branchEach branch, with how many commits it is ahead of and behind its upstream.
stash listEach stash, with its message, branch and age.

When a command fails, Gitkeen says what went wrong in plain words and how to fix it.

Learning the commands

When you use a button, the console shows the Git command that does the same thing. You can learn the commands while you work.

What keeps the console safe

  1. The console runs Git only. It does not start a shell, so |, ;, && and $(…) are refused as you type.
  2. Only everyday Git commands are allowed, and none of the options that make Git start another program.
  3. A command that can lose work shows what it will do before you press Enter. After Enter it asks again, with Run it and Cancel.
  4. Before such a command runs, Gitkeen saves a recovery point for each branch, file, tag or stash it could lose. The Undo panel can put them back.
  5. A command that would wait for an editor opens Gitkeen’s own editor instead. rebase -i opens the rebase editor, add -p opens the diff viewer to stage hunks, and commit without a message opens the commit panel.

Edit this page on GitHub