GitKraken Desktop Documentation

Contact support  
GitKraken Status  

GitKraken Client Release Notes

Behold the evolution of GitKraken Client! Find out what’s new, what’s fixed, or just take a trip down memory lane with a nostalgic swagger, remembering those bugs of yesterday.

Download Current Version Now

Check out our GitKraken Roadmap to see what we’re working on.

Version 8.10.3

Monday, November 7th, 2022

Bug Fixes 🐛

  • The client will no longer get stuck when creating a new file in-app.

Version 8.10.2

Tuesday, November 1st, 2022

New ✨

  • Workspace Overview section will now show Pull Requests for Bitbucket repos for the current user.

Improvements 🙌

  • When a GitLab token expires, GitKraken Client will now show a prompt to re-login. This should address previous issues working with GitLab repos.
  • Workspaces can now be viewed across machines and profiles. Be sure to sign into the same GitKraken account to access Workspaces on a different machine.
  • Improved Commit Graph responsiveness when bringing the app into focus.

Bug Fixes 🐛

  • Jira issues will no longer break if there is no vote field on an issue.
  • Removing your remote from the Left Panel no longer causes rows to overlap.
  • Links in blame commit messages will now open in an external browser.

Version 8.10.1

Tuesday, October 18th, 2022

Bug Fixes 🐛

  • Fixed an issue where some Linux distributions could no longer launch GitKraken Client.
  • Fixed an issue where Window Server could no longer launch GitKraken Client.

Version 8.10.0

“It’s electric!”

Monday, October 10th, 2022

Improvements 🙌

  • GitKraken Client has been updated to Electron 17.
  • New Tab layout has been rearranged to make it easier to access Repositories, Workspaces, and the Terminal Tab.
  • You can now double click a section header in the left panel to maximize that section. This option is also available in a context menu.

Bug Fixes 🐛

  • Fixed an issue where the breadcrumb in Azure repo tabs would direct users to add the repo to a Workspace when this is not supported.
  • Fixed an issue where the SSH key options were not being displayed for Azure and self hosted integrations.
  • Fixed an issue where the Workspace Overview page would say there are no PR’s/issues during initial loading.

Version 8.9.1

Wednesday, September 14th, 2022

Bug Fixes 🐛

  • Fixed an crash on some Windows machines when opening the Preferences menu.

Version 8.9.0

Wednesday, September 7th, 2022

“Ah! After 10,000 years I’m free. Time to conquer Earth!”

New ✨

“Alpha, Rita’s escaped! Recruit a team of developers with attitude.”

  • Team Overview – Added the Team Overview section for Workspaces:
    • Team Pull Requests – Shows all Pull Requests for repos in Team Workspace and provided quick actions.
    • Team Issues – Displays list of all Issues for repos in Team Workspace.
    • This view is in Preview with many more improvements coming. A link to submit feedback can be found at the top of the view

Improvements 🙌

Thanks to Alpha, the command center got some mighty upgrades.

  • Workspace UI improvements
    • GitHub users may open the in-app Pull Request Panel from Workspace sections.
    • Added the ability to switch issue tracker in the Workspace Overview page.
    • Added a gray draft PR indicator in the Workspace Overview page.
    • Repository and Pull Request sections in Workspaces have been updated to reflect the new styles in Overview.
    • Added colors to the last updated date displayed in the pull request and issue tables in Workspaces.
    • At Risk PRs are now highlighted with a ⚠️ icon in the PR Status column.
    • Team Overview for Workspaces associated with GitHub repos can be filtered by Author or Assignee.
  • Left panel improvements – Left panel filtering experience improved:
    • Issues and Pull Requests, which have separate, integration-specific filtering unaffected by the global filter, will automatically collapse while performing a global filter.
    • Sections can be collapsed and expanded while filtering.
    • We continue to listen to feedback and plan even more left panel improvements.
  • Added the keyboard shortcut Ctrl + Shift + E which opens checked repositories from the Workspace Repository section in your preferred external editor.
  • Jira Server connections now support authentication with personal access tokens (PAT).
  • In-app support forms have been removed in favor of linking to the support form on our website.

Bug Fixes 🐛

Rita made her monsters grow, but our megazord saved Angel Grove from their clutches.

  • Fixed an issue where GitLab Self-Managed remotes would not display a user’s avatar as the icon.
  • Fixed an issue where inputting an invalid token when signing in closes the token input box.
  • Fixed issues with checking out pull request branches from the Workspace Overview section.
  • Fixed an issue where searching in the Workspace Overview with upper case would not show any results.
  • Fixed an issue where having a pre-push hook fail when deleting a tag would cause a looping Oauth prompt to show up.
  • Fixed an issue where users could not delete tags from remotes.
  • Fixed an issue where editing profiles from Preferences -> Profiles could make it appear that the user had switched profiles.
  • Fixed an issue where the log-in screen had poor contrast on light themes.
  • Fixed an issue where commits would not immediately be inserted into the graph after using Show All Tags to unhide one or more tags.

Team Overview

Your teams have a new hub with the Team Overview in Workspaces.

This new broad view shows all Pull Requests and all Issues for the repos in your Workspace – giving you a high level view of your team’s coding efforts.

Team Pull Requests

If your Workspace repos are hosted on GitHub, you may filter the Team Pull Requests by assignee or author.

The Team Pull Requests sections has the following columns:

  • Last Updated
  • PR title with link to open the Pull Request in the hosting provider
  • PR Author
  • Repo name with link to open the repo in GitKraken Client
  • Review status
  • PR status – Shows status for “Draft” or “At Risk” Pull Requests
  • Checks – Shows CI/CD results
  • Lines added/removed
  • PR branch – Double click to check out directly in GitKraken Client
  • Shortcut to open the Pull Request Panel – GitHub Repos only

Team Issues

Team Issues will show all GitHub Issues, GitLab Issues, Jira Cloud Issues, Jira Server, or Trello cards associated with the repo.

With Team Issues, it’s easy to switch between Jira or Trello and back to either GitHub Issues or GitLab Issues. If you select Jira or Trello, you can also filter by project so that you only see issues that matter to you.

The Team Overview is in Preview, and feedback is welcome. A link to submit feedback can be found at the top of the view.

Workspace UI updates

GitKraken Client v8.9 also updates the UI for the Repositories and Pull Request sections in Workspaces – providing clearer information at a glance through updated color coding and iconography.

Overview > My Issues > Set Issue Tracker

You may now switch the Issue Tracker provider from the My Issues section in the Overview tab.

Left panel improvement

In the left panel, you may now expand or collapse sections when filtering the left panel.

We plan to continue pushing more left panel improvements in future releases. Thanks for your feedback so far!

Version 8.8.0

Wednesday, August 10th, 2022

The signs are all around us…and they’re pointing to an epic release of GitKraken Client v8.8.

New + Improved ✨

No yield signs here – we’ve made it easier to get connected to your favorite Git client with Single Sign On for multiple providers.

  • Single Sign On

  • Overview in Workspaces

    • A new Overview section has been added to Workspaces that focuses on the work most important to you across all the repos in a Workspace.
  • Partial stash

    • Right-click on a single file or a selection of files in the commit detail panel to see options for stashing and applying changes.
  • Left panel improvements

    • Sections in the left panel are now always visible and don’t scroll out of view.
    • Individual sections in the left panel can now be resized.
    • Aliases for submodules will now be displayed in the left panel.
  • New Tab view updates

    • The Recent and Favorite Repos lists have been moved to the top of the Repositories section for easier access.
  • More autosuggest in GitKraken CLI

    • Autocomplete for git remote prune and git remote update will now suggest remotes.
  • Fixed crashes and improved performance by approximately 2X to 3X when opening very large conflicts.

  • Improved the app performance when loading commit details.

Bug Fixes 🐛

GitKraken exterminators have eliminated most signs of bugs…

  • Users who installed GitKraken on Linux via Snap will no longer crash when opening file selection dialogs.
  • Resolving large conflicts with the context menu options will no longer crash GitKraken.
  • Fixed accounts not being listed when initializing a repo in a hosting provider.
  • GitKraken will now close open workspaces if the workspace was deleted from the organization.
  • Workspaces with no repositories will no longer load unexpected pull requests in the pull request section.
  • Fixed an issue where opening selected repositories within a workspace would open all repositories.
  • Fixed an issue where creating a new profile does not set a default organization even if the user belongs to an organization.
  • Fixed display issue for Google icon from the Google login/signup form.
  • Fixed a timing issue where the branch column would not show up for a workspace when you first create a workspace.
  • Fixed an issue where users could not create a workspace if the icon size was too big.
  • Removed unnecessary comment count column from Azure Workspaces.

Single Sign On

What is Single Sign On (SSO)?

Let’s first review the Wikipedia definition of SSO:

“Single sign-on is an authentication scheme that allows a user to log in with a single ID to any of several related, yet independent, software systems.”

The above diagram depicts what a typical SSO setup entails. These are the applications or actors involved in the setup:

Directory Server: A Directory Server is an application that stores information about the “objects” that belong to an organization. An object can be: printers, computers, shared folders, users, groups (a group is just a group of users). Some objects can contain other objects, which then allows them to reflect hierarchical structures.

  • Examples of Directory Server applications are:
    • Microsoft Active Directory
    • Oracle Identity Governance (OIG) Suite
    • Jump Cloud

Identity Provider: An identity provider (abbreviated IdP or IDP) is a system entity that creates, maintains, and manages identity information for principals and also provides authentication services to relying applications within a federation or distributed network. An IdP provider stores 3 main components: Users, Groups, and Applications.

  • Examples of Identity Provider applications are:
    • Okta
    • Azure Active Directory
    • Google Identity Platform

The Identity Providers provide services that allow third party applications to authenticate their users.
The authentication mechanism they provide is called “Oauth”, which allows third party applications to authenticate users without accessing/storing their password.

Requirements and configuration

GitKraken may now initiate an Oauth authentication flow with the following supported Identity Providers (IdPs)

  • Azure Active Directory
  • Okta
  • Google Identity Platform

Please note that your IdP will first need to be configured before setting up the connection in GitKraken. For assistance, please contact your IdP administrator or consult the IdP documentation for help.

Additional requirements:
SSO is only configurable by the GitKraken Owner or Admin and you must be subscribed to either the Teams or Enterprise plan.

Ready to get started? Then follow the How to set up SSO in GitKraken documentation.

Signing in with SSO

GitKraken Client users should see a new option to Sign in with SSO from the login screen.

After clicking Sign in with SSO, the SSO form will open and ask for an email address to use for SSO login. GitKraken will then check the email and determine whether the email address belongs to a single IdP for SSO. When the email address is successfully identified, the user will be taken to that IdP to login.

If the email is not recognized, GitKraken will display a message that no IdP was found.

Once authenticated, the user may use GitKraken Client.

Workspace Updates: Overview

Workspaces now have a personalized Overview section 🎉

This will provide you with a summary of all Pull Requests, Issues, and WIPs relevant to you for the repos grouped in your Workspace.

  • My Pull Requests: shows all PRs opened by you, assigned to you, or awaiting your review
  • My Issues: shows all issues created by you, assigned to you, or that mention you.
  • Work in Progress: shows all branches with uncommitted changes

We’re excited to centralize key information that is relevant to the user. Now instead of hunting for these pieces of information separately, you can get a holistic view of what you’re working on.

This Overview section is in Previewmode, and we’d love to hear your thoughts and feedback. Just click on the Provide feedback on this view prompt in the upper left of the Overview page to tell us what you think.

Partial Stash Support

Sometimes you only need to stash some of the files in your WIP.

Partial stashing is now available through the Commit Panel. Right-click individual files, or multiple files, and select the Stash file option to stash those selected files and have their changes reset.

Apply changes from stash to working directory

With partial stash, you may now partially apply a stash. When a stash is selected, right click files in the right panel to apply their changes to the working directory.

Partial stash tips

  • You may name a partial stash by typing into the //WIP or summary section before creating the stash.
  • Select additional files for stashing or applying by holding down the Shift or Control key.
  • Applying a file from a stash does not remove the file from the stash – use this to safely explore!

Left panel improvements

Users may now resize sections inside of the left panel. Simply drag the edge of the panes to expand or contract a pane.

Additionally, the left panel section headers will now remain visible as you resize the window or left panel panes.

Don’t forget! In the previous release, we also made it possible to toggle left panel panes on or off. Use this to customize the view to fit your needs and tastes.

New Tab view updates

Many thanks to our users for submitting feedback! With this release, we’ve moved the Favorites and Recent Repos list towards the top of the New Tab view.

This should make it easier to access the repos you access regularly.

More autosuggest in GitKraken CLI

The git remote prune and git remote update commands will now suggest remotes in the GitKraken CLI.

Hopefully this saves you extra typing or the need to remember that remote name.

Version 8.7.0

Wednesday, July 13th, 2022

GitKraken Client v8.7 has been released! Whether you’re covering a tear, or just adding some flair – we’ve got you patched.

New + Improved ✨

We hemmed in some new threads.

Bug Fixes 🐛

We’ve stitched up a few loose ends.

  • Fixed issue related to GitKraken CLI’s autocomplete in Git Bash.
  • In Workspaces, users will be notified if attempting to open a deleted or unreachable repo from the repo details section.
  • Fixed task lists for GitLab issues showing &nbsp.
  • Commit graph will immediately update when the app performs a fetch or force push from the terminal.
  • Fixed issue where if two profiles both have the same repo tab open, switching profiles would cause issues to disappear from the left panel.
  • Changing accounts will now properly reset the selected Workspace.
  • In the Workspace Pull Request section, removing a filter and quickly selecting a PR will no longer generate a blank screen.

Patch Support

A patch, or patchfile, is a file describing changes between 2 files. Patch files can be used to distribute changes that a given user would like to make to a particular revision without codifying it onto a git server.

Patch files are especially useful in distributing changes to/from environments where SCM may not be available and remain widespread in older development flows.

With this update, users gain another way to share and save changes.

Create patch from commit(s)

Right-click on a commit in the graph to access the new option for creating a patch.

Click the Create patch from commit option and the app will prompt you to select the save location for the .patch file.

You may also use the Shift or Ctrl key to multi-select commits and then right click on the selection to access the same patch option.

Create patch from file(s)

From the commit panel, right-click on a file to access the Create patch from file changes option.

Like the option above, this will prompt you to select the save location for the patch file.

You may also use the Shift or Ctrl key to multi-select files and then right click on the selection to access the patch option.

Create patch from Command Palette

Click on the Command Palette icon on the toolbar, or use the keyboard shortcut Cmd/Ctrl + Shift + P to launch Command Palette.

Here, you may search “patch” to access the Create patch from working directory changes option and get prompted to select a save location.

Apply patch from Command Palette

Use the keyboard shortcut Cmd/Ctrl + Shift + P or click the wand icon in the top right of the UI to bring up the Command Palette. Type “Apply patch” to summon the Apply patch command, and select it to open your file explorer.

Select your .patch file to then apply changes to your working directory. From here, you may continue to modify files, move to stage and commit, or continue with your workflow.

GitKraken Client does not yet support generating patches from binary files. This is a preliminary release with better support coming, and if you have feedback please contact us.

Left panel improvements: toggle sections

The left panel can get crowded, so we want to be able to let users disable sections that are not relevant to them.

Now when you right click headers on the left panel, a context menu appears to remove or add sections.

Updated UI and layout for New Tab view

The New Tab view has been reorganized! There are now distinct sections for Repositories, Workspaces, Integrations, and Other app actions.

Be sure to try out the integrations!

Repo aliases in Terminal Tab titles

In our previous v8.6 release, the app provided the option to set an alias for a repository by right-clicking on the repo tab. With v8.7, the alias name will carry over when you open the repo in a Terminal Tab.

Fuzzy search in gk history and gk blame commands

From the GitKraken CLI, you may now use the fuzzy search to drill down on a file name when using the gk history and gk blame commands.

Just start typing the name of the file to filter the list of matching files, and then hit enter to select the file for the command.

Users may now search tabs by repo alias in the tabs list

In the toolbar, users may click this arrow icon next to the notifications icon to expand a list of all currently open tabs. With v8.7, you may now search using repo alias to filter the list further, and quickly jump to that tab.

Name branch when creating branch from issue

When viewing an issue from inside GitKraken Client, there is now a short text field for naming the branch when creating a branch from the issue.

Consider setting up Issue Tracker Integrations like Jira, Trello, GitHub Issues, or GitLab Issues to get access to this handy feature.

Git LFS performance improvements

On top of performance improvements from the previous release, GitKraken Client v8.7 brings even more boosts. Users will see faster performance when cloning LFS repositories with submodules and note much faster performance for general GitKraken Client actions.

Here are some actions that should see improvements:

  • Cloning a repo with LFS submodule
  • Merge
  • Reset hard
  • Undo a hard reset
  • Discard all changes
  • Discard unstaged changes
  • Discard submodule changes

Version 8.6.0

Tuesday, June 14, 2022

You don’t have to be a an intergalactic Space Ranger to know that when it comes to navigating a repo, fast is good. You’ll be seeing performance improvements…performance improvements everywhere, with the release of GitKraken Client v8.6.

New ✨

You’ve got a friend in GitKraken.

  • Users can now create Workspaces using Bitbucket Server repos.
  • Users can now select Git Bash as their default shell in Windows for GitKraken CLI.
    • Users can set Git Bash as their default terminal by navigating to PreferencesTerminalDefault Terminal and selecting “Git Bash” from the dropdown menu.
  • Repo and Terminal Tab aliases:
    • Users can now set an alias for a repository.
      • To set an alias, users can right-click on a Repo Tab and select the Alias repository option.
      • Setting an alias through a Repo Tab will cause GitKraken Client to store that name for the repo and reference it as an “Alias Repository”.
    • Users can set an alias for individual Terminal Tabs.
      • To rename any Terminal Tab, users can right-click on the tab and select the Rename tab option.
      • Setting an alias to a Terminal Tab results in only renaming that specific tab.
  • Users can now set GitKraken Client to skip submodule updates while performing Git actions, either globally or per repo.

Improvements 🙌

Faster for LFS, big repos, and beyond.

  • Git LFS performance improvements:
    • Users will see faster performance when cloning LFS repositories.
    • Users will note much faster checkout times in LFS repositories.
  • Sections in the left panel will now be collapsed by default.
  • Users can now set the maximum number of commits shown in the Commit Graph as low as 500 commits.
    • To set the shown commit limit, navigate to PreferencesGeneral and look for Max Commits in Graph towards the bottom of that menu.
  • Users will note improved performance when the open repo has a large number of stashes.
  • When creating a pull request from a branch that starts with an issue ID (e.g, GK-123-feature-branch), a link to the associated issue will now be added to the pull request description automatically.

Bug Fixes 🐛

You are a sad, strange little bug, and you don’t have my pity.

  • When creating a new branch from an issue, users will see the input box as expected.
  • When working with remote branches in the left panel, the context menu will remain available.
  • GitLab avatars will now more consistently display correctly.
  • Branches will immediately refresh when a checkout is performed in a Terminal Tab.
  • Users connected to an Azure DevOps integration using Azure’s older hostname style (eg. {organization} will now be able to use Workspaces and the Pull Requests section in the left panel.
  • Users leveraging Azure DevOps Workspaces will no longer see a misleading ‘Add a Repository’ button in their Workspace. Users will need to visit Azure DevOps directly to add repositories to their Workspaces.

Version 8.5.0

Tuesday, May 17th, 2022

The GitKraken team is proud to announce these improvements to Workspaces, Teams, and the GitKraken CLI. Lower your blast shield, trust your feelings, and prepare for the release of GitKraken Client v8.5.

New ✨

Git is what gives a dev their power…It binds the galaxy together.

  • GitKraken WorkSpaces now support Azure DevOps repositories.
    • Any Workspace created for Azure DevOps will automatically include repos for a selected Azure Project.
    • Workspaces can currently support up to 100 repositories for an Azure Project.
  • Visual interactive rebase can now be initiated from the GitKraken CLI, which you can access from a Terminal Tab or a Repo Tab by clicking the Terminal icon in the top toolbar.
    • Users can type either gk rebase -i or gk rebase --interactive along with two refs to open the interactive rebase view. If only one ref is passed it will perform the rebase of the branch currently checked out onto the specified ref.

Improvements 🙌

An elegant Git client for a more civilized age.

  • Git LFS Improvements:
    • Users will experience a reduced delay in updating the graph and commit detail panel when selecting commits in LFS enabled repos.
    • Note: Significant work towards reducing checkout times for LFS repos is underway and we plan to include these improvements in the GitKraken Client v8.6.0 release, scheduled for June.
  • When creating a new Team, members can now be added as part of the creation process.
  • Team members are now sorted by username in the Teams section, found in the left panel of GitKraken Client.
  • Improvements to GitKraken Workspaces:
    • Workspaces can now be shared as Team Workspaces, allowing users to share the Workspace with specific teams within their Organization.
    • In the Workspaces Repository view, clicking on the name of a repository will open it in a Repo Tab.
      • Users can view repository information by clicking on the Open Repository Details option, found on the right side of the Repositories view.
    • Organization admins and owners will see a new “Show All Workspaces” checkbox, allowing a simplified way to see all available Workspaces.
    • Users can now leverage GitHub’s search syntax when using the Workspaces Pull Requests view search.
    • Users will find more options for filtering in the Workspaces Pull Requests view. The new options include:
      • “Opened by Me”, to show pull requests that were opened by the user. This filter is available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
      • “At Risk”, to show any pull requests that are not drafts and have been open for longer than 7 days. This filter is currently only available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
      • “By repository”, to limit the view to a single repo within the Workspace. This filter is currently available for Azure DevOps, GitHub, GitHub Enterprise, Gitlab, and Gitlab Self-Managed repositories.
  • For Windows users, GitKraken Client will now respect the core.longpaths setting in .gitconfig. Previously, GitKraken Client had its own longpaths setting independent of the user’s .gitconfig setting.
    • On Windows, core.longpaths now only applies to the files in the working directory, not in the .git directory, to maintain compatibility with Git for Windows.
  • GitKraken CLI autocomplete will now be able to suggest more than one argument in these commands:
    • git add
    • npm install
    • npm remove
    • yarn add
    • yarn remove
  • Notifications with a Call to Action will now be marked as read when the CTA is clicked.
  • Users encountering merge conflicts can now right-click on the conflicts shown in the Commit Panel to reveal new options for easier and faster conflict resolution. The new options available are:
    • “Take current”, which applies the changes from the branch currently checked out to resolve the conflict.
    • “Take incoming”, which applies the changes from the incoming branch to resolve the conflict.

Bug Fixes 🐛

Bugs…You will never find a more wretched hive of scum and villainy.

  • GitKraken Client will now open as expected for users on OpenSSL 3 Linux distributions such as Ubuntu 22.04 and Fedora 36.
  • Users will see increased performance when opening a commit diff for very large images. Large images will now display as a binary file Instead of producing an error.
    • For large files, such as images and other media, we recommend using Git LFS.
  • Dotted graph lines will no longer take precedence when overlapping with solid lines in graph views.
  • Users can now type in the GitKraken Terminal as expected on a wider range of OS versions.
  • When un-hiding a remote, users can continue hiding or un-hiding remotes without waiting for the triggered automatic fetch to resolve.
  • Azure DevOps integrations and all self hosted integrations will now work properly on our new Teams license tier.
  • Users with hundreds or thousands of Azure DevOps Projects will see improved performance when integrating Azure DevOps.
  • Users can now use quotation marks when naming Workspaces.
  • All Organization and Team actions will remain available after using the login screen.
  • The scrollbar in the GitKraken Terminal will now remain clickable in all situations.
  • When a user pushes many files up at once to GitHub, they will no longer experience an OAuth infinite loop.
  • Opening repositories via gitkraken --path <path> when GitKraken is already open will now work as expected.

Version 8.4.0

Tuesday, April 12th, 2022

We want to help teams cut out all the jibber-jabber when working with pull requests across multiple repos. Get ready for GirKraken Client v8.4, a release that will have you saying “I love it when a pull request comes together.”

New ✨

I pity the tool that does not have Workspaces or the GitKraken CLI.

  • GitKraken Workspaces:

    • Workspaces now include a Pull Requests view!
      • Users can filter PRs to see items “Assigned to me”.
      • At-risk pull requests are highlighted through a label and filterable.
      • Selecting any GitHub pull request now shows the user a new Pull Request view that presents users options to quickly manage PRs across a whole Workspace.
    • Clicking on any repo in a Workspace now shows see more info and options. Users will see the repository’s README, as well as quick access buttons to open the repository in a Repo Tab, Terminal Tab, or on the remote repository’s hosting provider.
  • GitKraken CLI:

    • The Terminal button in a Repo Tab’s toolbar will now open the GitKraken CLI inside a Terminal Panel, instead of opening a new Terminal Tab. Users can still open new Terminal Tabs through a New Tab, the Command Palette, or through any Terminal’s context menu.
    • Users can toggle the Terminal Panel on and off by pressing the Terminal button in Repo Tab toolbar, through keyboard shortcut Ctrl+`, the Command Palette, the Terminal Panel’s context menu, or options in the GitKraken Client’s View menu. Toggling the Terminal Panel will turn it on or off across all Repo Tabs.
    • A Terminal Panel session can also be terminated by executing the exit command. This will only close the Terminal Panel and not the Repo Tab. Toggling the Terminal Panel back on will initialize a new terminal session.
    • Unlike with the Terminal Tabs, navigating to a different working directory in a Terminal Panel will not change the repository opened in the Repo Tab.
    • The following gk commands are available in the Terminal Panel:
      • gk blame
      • gk diff
      • gk history
      • gk help

Improvements 🙌

Making GitKraken Client a mean, clean Git managing machine.

  • Users will now see helpful icons when shown GitKraken CLI Autocomplete suggestions, helping clarify to which command the suggestion is related.
  • Git LFS users will see improved performance checkouts.

Bug Fixes 🐛

Shut up, bugs!

  • Filtering Autocomplete suggestions by name will work as expected.
  • After selecting between multiple Autocomplete suggestions that have the same prefix, further suggestions will disappear as expected.
  • Users will no longer be allowed to create Workspaces for repositories on unsupported versions of GitLab Self-Managed services.
  • Bitbucket Server users will now see the branches correctly populated when creating Pull Requests.

Version 8.3.3

Wednesday, March 16th, 2022

The improvements to GitKraken Client keep Marching forward.

Improvements 🙌

  • Users creating an account or signing in will see an improved user experience

Version 8.3.2

Monday, March 7, 2022

What is Keif’s favorite kind of bug? The fixed ones!

Bug Fixes 🐛

  • GitKraken Client now supports GitHub’s new GraphQL query types. GitHub users will now see creating, commenting and reviewing pull requests work as expected.

Version 8.3.1

Monday, February 28, 2022

Spring is almost here, but we couldn’t wait to bring you these improvements in GitKraken Client v8.3.1.

Improvements 🙌

Though short, February is filled with lots of love and sweet improvements.

  • GitKraken CLI:
    • Users who want to use the GitKraken Terminal when opening repositories in external terminals, alt/⌥ + T, can now set this as the default by navigating to PreferencesGeneralDefault External Terminal and selecting “GitKraken Terminal” from the dropdown menu.
    • When hiding the visualization panel orientated to the top of the window, the toolbar will remain in place at the top.
  • Themes:
    • Users can customize the terminal colors together with the rest of their custom themes. This update removes the Terminal Theme setting from the PreferencesTerminal menu.

Bug Fixes 🐛

The early birds of spring get the bugs.

  • GitKraken Client will remain responsive when adding an issue tracker integration supporting a large number of assignable users.

Version 8.3.0

Monday, February 14, 2022

The GitKraken team is going for the gold medal in speed and usability! Sharpen your blades and get ready for the release of GitKraken Client v8.3!

New ✨

I got a need…a need for speed.

GitKraken Client v8.3 introduces a new ARM64 compatible version, offering native support for Apple Silicon architectures, as used in Macs with M1 chips.

GitKraken Workspaces are now available for repositories hosted on GitHub Enterprise and GitLab Self-Managed.

Improvements 🙌

There are no speed limits on the road to success.

  • Mac users will get optimal performance without needing to run the ‘Big Sur workaround’ from a terminal, which had been required to fix the partial signature issue introduced in macOS Big Sur.

  • Fedora 35 users will no longer need to pass the --no-sandbox flag to launch GitKraken Client.

  • GitKraken CLI:

    • New Terminal settings added under PreferencesTerminal.

      • Default Directory – Users can now set the default directory where new Terminal Tabs will open when initiated from the “New CLI Tab” button in the Repo Management Tab or from the Comand Palette.
      • Line Height – Users can set how much space appears between each line printed to the terminal.
    • Autocomplete suggestions have been added for git flowcommands.

    • Any user created global or local Git aliases will be shown as autocomplete suggestions.

    • The git reset command will now suggest staged files too.

    • Autocomplete suggestions for git add will show relative paths when called from inside a subfolder.

    • The visualization panel will automatically open after making the initial commit in a new repo.

    • Right mouse clicking in a Terminal Tab will open a new context menu allowing users to open new Terminal Tabs, paste into the terminal, and close the terminal, among other actions.

  • Themes:

    • Users can customize the commit graph colors in their custom themes. Examples of // graph colors have been added to the default theme files. Users can refer to PreferencesUI Customization -> Theme to locate the GitKraken Client theme folder on their computer.

Bug Fixes 🐛

You take a crash, you get back up, and next time you succeed. That’s a great feeling.

  • Pull requests filtering in the left panel is no longer case sensitive.
  • Users on GitLab Self-managed +13.8 will no longer get directed to a 404 page when selecting Generate a token on GitLab.
  • When using the Pull Request panel for forks using Azure DevOps based repositories, users will no longer see a no options error on the form.
  • GitKraken CLI:
    • Using reverse search (ctl+r) will no longer cause unintended autocomplete suggestions.
    • Updated autocomplete suggestions for git gc, fixing spelling issues.
    • Autocomplete suggestions for paths with spaces in them have been improved.

Version 8.2.1

Tuesday, December 21, 2021

Everyone needs elbow room.

Improvements 🙌

  • The Workspaces tab can now be closed to save space in the tabs bar while not in use. A small icon has been added to quickly reopen the tab when needed.

Version 8.2.0

Monday, December 13th, 2021

Get ready for a multiverse bending reveal! We are unleashing the cosmic power of GitKraken Workspaces with the release of GitKraken Client v8.2!

New ✨

We have helped users progress and seen them accomplish wonders.

Introducing GitKraken Workspaces

GitKraken Workspaces save teams time by providing an easy way to group repositories, take actions against multiple repositories at once, and quickly onboard new team members.

GitKraken Workspaces allow you to gather and access all the required repos for your project in a single tab in GitKraken Client. The new GitKraken Workspaces tab shows you the status for the last branch that you checked out, how far ahead and/or behind in commits you are, and if there is an active WIP for each included repository.

GitKraken Workspaces can be created as Personal, only visible to you, or Shared, visible to all members of your Organization.

  • Users can access GitKraken Workspaces from the new “Workspaces” tab in the tabs bar, from the New Tab view, from the command palette, which can be opened with the keyboard shortcut cmd/ctrl + p, or from the newly added repository breadcrumb in any Repo Tab.
  • Users can view details and trigger the following actions on any or all of the repositories in a workspace at once:

    • Clone multiple repositories at once. This will help teams quickly onboard a new team member or get a new computer up and running.
    • View the last checked out branch for all repositories and see if a branch is ahead/behind a remote.
    • View work in progress for all repositories, including the number of files modified, added, renamed, or deleted.
    • Perform a fetch for all or a selection of repositories.
    • Open multiple repos in GitKraken Client, or in an external editor, such as VS Code, IntelliJ, Atom, or Sublime Text.
    • Open any repository in the associated hosting service website.
  • GitKraken Workspaces can currently contain repositories hosted on,, or


  • Users may now create their own custom GitKraken Client themes.

    • For more information about creating a new custom theme, checkout our Themes documentation or navigate to gitkraken/themes/
  • Users will find two new themes when navigating to PreferencesUI Customization menu.

  • Users can now sync their GitKraken theme with their system theme, if their OS supports it.

Activity status:

  • An activity status will now display on the avatars of members in your GitKraken Organization or Team, indicating if they are actively using GitKraken Client. This activity status icon is visible in the Team View section in the Left Panel, or in the Organization view in Preferences.

  • Users can manually set their status to “Active” or “Away” by selecting the circle icon in the top right corner, or by opening the Profile/Account dropdown menu.

GitKraken Workspaces and Activity status are currently unavailable for Self-Hosted and Stand-Alone customers.

Improvements 🙌

When you love something, you improve it.

  • GitKraken CLI:

    • Users can now customize the behavior of the ↹ Tab key when using auto-complete in a Terminal Tab. This setting can be found under Preferences Terminal Tab Behavior.
    • Users can customize the cursor used in a Terminal Tab. This can be configured in Preferences TerminalCursor Style. Users can select either Block, Underline or Bar for their cursor.
    • Auto-complete suggestions will now show branches and tags as options when running git diff or git reset commands.
    • The gk diff command now supports tags and branches as options.
    • Auto-complete suggestions have been added for npm and yarn.
  • When users open the pull request panel and click on a pull request while the left panel is minimized, GitKraken Client will now open the pull request view.

Bug Fixes 🐛

We came here years ago to protect users from these bugs.

  • When using the GitKraken CLI, suggestions will disappear as expected after auto-completing a command with escaped characters in the path.

  • After using GitKraken Client to execute a cherry-pick and resolving any arising conflicts, the Git CLI will no longer report that a cherry-pick is currently active.

  • When creating a pull request in a repository with a large number of forks, users will no longer have to wait as all forks are being fetched before opening the dropdown menu.

Version 8.1.1

Tuesday, November 9th, 2021

Get ready to celebrate the release of GitKraken Client v8.1.1 with these puns you can tell next time you are hanging out at the ol’ foo bar. If you don’t get these jokes, whoami to judge?

Improvements 🙌

Sudon't want to miss out on these new improvements.

  • GitKraken CLI Preview:

    • GitKraken CLI users can now use git help to display help information about using Git.
    • Windows users will now see an auto-suggest option for the cd command.
    • Users changing directories in a Terminal Tab will see auto-suggest options showing the end of the folder path rather than just the beginning. This is useful when long directory names are present.
  • Users can choose from more Keif options for their avatars when creating or editing their Profiles.

Bug Fixes 🐛

There are only 10 kinds of bugs: the ones we have fixed and the ones that we have not identified yet.

  • GitKraken CLI Preview:

    • Improved Terminal Tab support for custom fonts, such as Nerd Fonts and Powerline fonts.
    • Users leveraging oh-my-posh in Powershell using custom themes will now see and be able to select auto-suggest options.
    • Users can now resize the commit panel in a Terminal Tab.
    • All Mac users are now able to use the gk commands.
    • Windows users leveraging “Constrained” language mode in Powershell can now execute gk commands.
    • Users can now resize the merge editor tool as expected when the visualization panel is positioned to the left or right in a Terminal tab.
  • When working with GitHub and GitLab wiki repos, GitKraken Client will no longer throw an error message about being unable to fetch pull requests.

  • If a user checks out a commit while in Solo mode, they will now see the HEAD reference displayed.

  • Users fetching GitHub pull requests will no longer see timeouts.

Stand-Alone & Self-Hosted 🏢

There is no place like ~

  • The GitKraken CLI Preview is now available for Self-Hosted and Stand-Alone customers.

Version 8.1.0

Thursday, October 14th, 2021

Autumn brings sweaters, pumpkin spice, and apple picking. It is also bringing some awesome updates to GitKraken Client as we release v8.1.0!

New ✨

The seasons continue to change and so does GitKraken Client…for the better!

  • GitKraken Client can now identify weak SSH keys and provide an easy way to remove and replace them. Read more on the GitKraken blog.

Improvements 🙌

It’s the time of year to reap the harvest of new improvements to the GitKraken Git client.

  • GitKraken CLI:

    • GitKraken CLI users can now use reverse search as expected by typing Ctrl+R` in the terminal.
    • Mac users will now see the LANG environment variable pass automatically to the shell process.
    • When selecting an auto-suggest option with the mouse, GitKraken Client will now refocus on the terminal prompt.
    • The GitKraken CLI now supports 256 colors.
    • Mac and Linux users will now see auto-complete suggestions for the cd command.
    • When running gk blame or gk history, users will now see suggestions when navigating from inside a repository’s subdirectory after typing ../.
    • Users will now see auto-suggest options for the git gc command.
    • In addition to showing or hiding the visualization panel, users can now orient it to the top, bottom, left, or right, as well as toggle the right-side commit panel using the visualization panel toolbar.
  • The user interface for user profile settings under the [Preferences] menu has been improved.

  • Users can now open specific comments on from the comments inside GitKraken Client’s pull request or issue views.

  • Users who are not using GitKraken Integrations will no longer be repeatedly prompted for credentials for each remote when connected to repositories with multiple remotes sharing the same hostname.

Bug Fixes 🐛

As the leaves fall, so do these bugs.

  • The overall reliability of notification delivery has been improved.
  • Auto-complete for Windows users leveraging the GitKraken CLI has been improved.
  • Windows users will no longer see a Named Pipes error when running gk commands in a terminal tab.
  • Using gk diff in the GitKraken CLI will produce properly parsed numerical SHAs.
  • When discarding a large number of files in a repository, the repo will fully load as expected.

Version 8.0.1

Tuesday, September 28th, 2021

Everyone: “I am loving v8.”
GitKraken: “Let’s make the experience even better!”

Improvements 🙌

  • GitKraken Client users can now search for a particular tab and navigate the menu using the keyboard when using the tab dropdown menu.

Bug Fixes 🐛

  • Replaced the SSH key generation library with one that generates stronger keys. Read more on the GitKraken blog.
  • Gitflow branch folders and tag folders collapse and expand as expected when selected in the left panel in GitKraken Client.
  • Layout and options have been optimized in the Organization panel in GitKraken Client’s Preference view.

Version 8.0.0

Tuesday, September 21st, 2021

“It began with the forging of the Great Rings Kraken.”

The true power of the Fellowship of developer collaboration is unleashed in GitKraken Client’s v8.0!

New ✨

“One tool to rule them all,
One tool to find them,
One tool to bring them all
and in the Git log bind them.”

Introducing the GitKraken CLI Preview

The GitKraken CLI adds a Git-enhanced, keyboard-driven, terminal experience to GitKraken Client. Get the powerful Git visualizations GitKraken Client is known for—like the commit graph—in the context of a Terminal Tab. Plus auto-suggest and auto-complete for Git commands to help you drive (and learn) Git faster, with fewer mistakes.

Dive deeper into file changes with the gk commands. Use the command gk history to see File History and gk blame to see what has changed in a file or commit and who made those changes.

During the GitKraken CLI Preview we are looking for feedback to help improve this feature. Please use the Feedback form linked in the bottom right corner of your GitKraken Client app, or email us at [email protected].

  • Users can open Terminal Tabs in a number of ways:

    • Clicking the “New Terminal Tab” button after opening a New tab in GitKraken Client.
    • From the “Terminal” button in the toolbar of a Repo tab (opens the current repo in a Terminal Tab).
    • From the Command Palette (Ctrl/Cmd + P).
    • When working in a Terminal Tab, you can open a new Terminal Tab with the key combination Ctrl/Cmd + T. The new Terminal Tab will open in the same working directory.
  • Auto-complete and auto-suggest make building Git commands easier than ever before in the GitKraken CLI. This feature works for users of PowerShell for Windows, ZSH and Bash for Mac/Linux.

    • Auto-complete and auto-suggest are configured for the most common Git commands, but we are continuing to build out this feature and would love feedback on which commands and parameters you want added.
    • Please be aware that other auto-complete programs could potentially cause the GitKraken CLI auto-complete to stop working. You may need to uninstall or disable those other programs to use this feature.
    • Note: If you switch shells, you’ll need to set the new shell as default in your operating system settings and restart your computer for auto-complete to continue working as expected.
  • Some of the legendary Git visualizations that GitKraken Client is known for are also accessible within Terminal Tabs. To quickly view the commit graph, file diff, history, and blame view, simply type these commands:

    • gk panel: toggles the visualization panel on or off. You can also reposition the panel to the top, bottom, left, or right by adding those parameters to the command. For example gk panel right moves the panel to the right of the screen.
    • gk graph: shows the graph view. While this command has similar behavior to gk panel, even allowing repositioning of the graph with the same top, bottom, left, or right parameters, this command also returns to the graph if you’re in a different view and has subcommands for toggling the graph columns with the keyboard.
    • gk history and gk blame: open the history or blame panel for a specified file.
    • gk diff: shows changes between commits. If no commit SHAs are provided, it will use your WIP and HEAD. If only one commit SHA is provided, it will be compared with HEAD.
    • gk --help: shows the list of available gk commands. You can also use –help on a specific gk command to see its arguments.
    • A toolbar above the panel will display the current repository name, branch, tag, and the number of changes pending to be pulled and/or pushed. Clicking this toolbar will toggle the panel on or off.
    • For Free accounts, this visualization panel will only be accessible within publicly-hosted repositories.
  • A Terminal section has been added to the Preferences menu that allows Terminal Tab customization:

    • Font choice. Changes to this setting will only apply to new Terminal Tabs.
    • Font size.
    • Enable auto-complete & auto-suggest.
    • Default the visualization panel position when opening a new panel: top, right, bottom, or left.
    • Show the visualization panel by default. This will apply only when opening new tabs.
    • Terminal theme.

The GitKraken CLI Preview is currently unavailable for Self-Hosted and Stand-Alone customers.

Deep Linking

“Oh, it’s quite simple. If you are a friend, you speak the password, click the link, and the doors will open.”

We’ve added the ability to share deep links to specific remote repositories, commits, branches, and tags in GitKraken Client. This allows users to more easily collaborate and save time when working in issue queues or Git pull requests.

  • When shared, these links will both open and focus GitKraken Client to the linked repository. The links will focus GitKraken Client on the commit, branch, or tag specified. When specifying a branch, the latest commit of that branch will be focused.
  • The links can be found in GitKraken Client’s context menus under Copy link to remote/commit/branch/tag.

Jira App Integration – Git Integration for Jira

“It’s the Jira ticket that’s never started that takes the longest to finish.”

GitKraken Client now works with the Git Integration for Jira app to allow quick navigation between the client and Jira when viewing commits and file diffs related to Jira issues.

  • In GitKraken Client, you’ll find buttons and links to open the following in Git Integration for Jira:

    • File diffs – within the file diff view and in file context menus.
    • Commits – context menu when right-clicking commits in the graph.
  • In the Git Integration for Jira, anywhere you view commits and diffs will automatically have links to open them in GitKraken Client.

  • To leverage GitKraken’s Git Integration for Jira integration you will need to:

    • Connect Jira Cloud Integration in the GitKraken Git Client.
    • Select Jira Cloud as the Issue Tracker for a repository.
    • Select a Jira Project.
    • Install Git Integration for Jira on the same Jira Cloud instance as the Jira Project.

      Improvements 🙌

      “Even the smallest update can change the course of history.”

  • The Fuzzy Finder is now the Command Palette!

    • We’ve renamed the Fuzzy Finder to the Command Palette. You can still open the command palette through the keyboard shortcut Ctrl/Cmd + P, or through the new magic wand icon in the toolbar.
  • Tab navigation has been significantly improved when many tabs are open at once.

    • We have improved the tooltips to provide both tab title and repo information.
    • Tooltips will now instantly appear when hovering the entire tab, not just the title.
    • A new dropdown list has been added to the tabs bar to help with tab navigation.
  • Reopening tabs after a “close all tabs to the right”, a “reopen closed tab” will now reopen only one tab at a time, instead of all that were closed at once.

  • An option to “Quote Reply” has been added for comments in the PR view.

  • The profile menu now shows the Organization associated with the current profile.

  • A “Cancel Rebase” button has been added at the top right of the Interactive Rebase panel for easier access.

  • We have improved form, prompt, and modal keyboard navigation and submission.

  • Improved user experience for the login form.

Bug Fixes 🐛

“You (bugs) shall not pass!”

  • Styling of long branch names in the right panel has been improved.
  • Users will no longer see issues for remotes without access to a repo, as happens when users leave an organization or when forks are deleted.
  • When using the delete key to erase spaces in a URL, the cursor will behave as expected.
  • The Pull Request icon has been added back to branch labels in the graph.
  • The bottom of Diff views are no longer cut off when the file mode changes.
  • Relative paths are now allowed in hooksPath.
  • All users are now able to select a project for GitLab and GitLab-Self-Managed issues on the left panel.
  • If Sublime Text 4 is installed, it will now be detected and appear in the external editor dropdown.
  • Debouncing has been added in the left panel search. Searches will be executed when you stop typing, instead of on each letter, making it easier to find what you’re looking for.
Have feedback about this article? Did we miss something? Let us know!
On this page