GitKraken's UI helps make sense of Git. Below we cover the layout and what the icons represent.
From left to right, GitKraken displays a left reference panel, center graph, and the Commit Panel when working with a repository.
In addition to Undo and Redo, the main toolbar houses common repo actions.
Many actions performed in GitKraken can be undone. If an action is undoable, the Undo button will be a solid color ready for action.
What if you undid something, only to realize that you didn't want to undo it? GitKraken also has a Redo button so you can undo your undos.
Pull changes from your remote repos with this button. See the button next to the icon? Click that to customize the type of pull you want to perform:
- Fetch All
- Pull (fast-forward if possible)
- Pull (fast-forward only): equivalent of
git fetch git merge --ff-onlyin the CLI
- Pull (rebase): equivalent of
git fetch git rebasein the CLI
Tip: If you find yourself repeatedly performing the same pull actions, set the default pull type by clicking the circle icon to the pull type's left. The default selection will appear as a green circle icon.
Push changes to the remote repo as set in your upstream.
Create a branch on your current local repo.
Stash your work-in-process (
// WIP) changes.
Ready to restore your
// WIP? Pop that stash and carry on as you were.
Note: Toggle the toolbar labels by navigating to Preferences UI Preferences and toggling the
Show toolbar icon labels checkbox.
Left reference panel
Referred to as the left "ref" panel, GitKraken shows the properties below specific to your repository. The panel and each pane can be collapsed or expanded as needed.
References to local branches — pointers to specific commits allowing work to be separated.
If you need help with branches, visit our Branching and Merging page.
References to remote branches.
Set sail into pushing and pulling remotes for more.
This shows active requests for merging one branch into another. With the GitHub or Bitbucket integration, new PRs can be created directly from GitKraken.
Create your Pull Request to get your contribution merged.
These represent active pointers to commits but never move. Tag, you're it!
Stored file changes in the working copy.
For saving your loot to play with later, here's more on stashes.
A Git repository in a subdirectory of the current repository.
Git-inception with submodules anyone?
The Commit Panel is where files and changes from your working directory are staged and committed.
The three parts in order of operations on the staging panel are:
- Unstaged Files — Watched files in your working directory that have changed since the last commit.
- Renamed, deleted, new, or modified files appear here.
- Staged Files — Files manually added to the index that are ready to commit.
- Individual lines, hunks, or all of the changes can be added
Commit Message — recording staged changes to the repository
- Summary: The brief but meaningful message supporting your commit. This text will appear in the graph.
- Description: The extended message to provide more details behind the changes.
Also, here is a quick color guide for the file symbols:
This panel can also be fixed on the bottom of the client. Just click the icon in the upper right corner of the Commit Panel.
For deeper waters on staging, dive into committing work.
The graph in GitKraken is the core of your repo and a representation of the Directed Acyclic Graph (DAG). Your commits are displayed here, along with commits from other contributors.
Each row of the graph represents one commit, and the top is always for the latest changes. An interactive //WIP (Work-In-Progress) node will show if the working directory has changed since the last commit.
Branches and tag labels on the left side of the graph are pointers to specific commits, and each vertical column represents a branch currently available on the repository.
Columns can intersect through merge commits as shown in the graph legend. As also shown, multiple branches can be at the same place of a single commit and can be both local and remote.
For a given vertical track, you can read from bottom to top, and right to left to see how changes are introduced into a focused branch.
For more details on the interface, like soloing remotes, visit Hiding and Soloing.