GitKraken Changelog

What's new in GitKraken 9.13.0

Mar 7, 2024

NEW:
Added the ability to add reviewers to a new Azure Devops PR.
Select users from your Azure DevOps project to be a reviewer or required reviewer in the Create Pull Request panel.
IMPROVEMENTS:
Focus View is improved to make it even easier to take action on your most important work. Open the Focus View tab to see an actionable list of your PRs, Issues, and WIPs.
Focus View will now show hosting service connection status from the Hosting Service dropdown, and provide a link to Preferences if not connected.
Added the ability to select a repo for issues in the Focus View that are not tied to a repository.
Selecting a Cloud Workspace in the Workspace dropdown in the Focus View now ensures the correct hosting service for that Workspace is selected.
Experimental Feature – Git Executable:
Added rebase support.
Added pull (rebase) support.
Added checkout suppport.
LFS improvements by calling git-lfs directly.
Upgraded to Electron 28.
Upgraded libgit2 to 1.7.2.
BUG FIXES:
Fetch:
Fixed an issue where a remote can’t be fetched again until GitKraken Client is restarted.
Fixed an issue on macOS where GitKraken Client might not find the GPG path.
Fixed an issue where Jira Issues for the Focus View would not load if the token was expired.
Fixed an issue where the Focus View filter Needs my review would show reviewed pull requests.
Fixed a regression where a remote couldn’t be fetched while a different remote was already fetching.
Fixed a regression where fetch spinners on remotes in the Left Panel would take a long time to appear.
When trying to fetch while a remote is already auto-fetching in the background, the fetch spinner will appear on the remote and any error that occurs will be shown.
Experimental Feature – Git Executable:
Fixed an issue with LFS repositories where credentials were blocking the application in some cases.
Focus View:
Fixed an issue where Focus View items were not sorted.
Fixed an issue where Focus View items would not be removed when merged (pull requests) or set to done (issues).
Fixed an issue where pull requests would not load in the Focus View when filtering with a Bitbucket Workspace.
There is still a known issue where pull requests from a forked repository will not appear unless the base and fork are both within the Workspace.
Fixed an issue where the Focus View would appear in Self-Hosted and Serverless clients
Workspaces:
Fixed an issue where Azure DevOps Workspaces would show duplicate repositories in the repositories page.
Improved reliability at loading Workspace repositories.
Background colors for added/removed lines in the diff editor now correctly respect theme variables.
Fixed an issue where line endings were not honored when merging LFS pointers when AutoCRLF is enabled.
Fixed an issue where, if the user became logged out, GitKraken Client wouldn’t acknowledge that the user was logged out and wouldn’t allow the user to log back in.

New in GitKraken 9.11.1 (Jan 11, 2024)

New in GitKraken 9.11.0 (Dec 15, 2023)

NEW:
Added new actions to Focus View items:
Merge pull request
Close pull request
Update issue status
Mark issue as closed
Open pull request/issue in the browser
Added new ways to share Cloud Patches:
You can now set link permissions on your Cloud Patch links to allow access to Anyone with the link, Anyone in my org, or Only collaborators.
You can now share Cloud Patches directly with members of your organization by selecting specific users when creating a Cloud Patch.
You can now view Cloud Patches shared with you in the Cloud Patches Left Panel section under Shared with Me.
You can now create Cloud Patches from the Command Palette (Ctrl/Cmd+P).
You can now use the left and right arrow keys (as well as h and l) to navigate between a commit in the Commit Graph and the first file in that commit.
IMPROVEMENTS:
Experimental Feature – Git Executable:
Added merge support.
Add pull support when the selected branch is not active.
Added new log level GIT_SILLY to get extra info about git and ssh commands in logs.
Added new UI Customization setting in preferences to use generic hosting service icons in branch/tags.
BUG FIXES:
The commit message view in the Commit Panel now resizes properly when rebasing.
Fixed an issue where SSH signed tags would display the signature in their tooltip.
Fixed an issue where pull requests for GitHub Enterprise would not load in Workspaces.
Fixed an issue where dragging a Commit Graph label onto a Left Panel branch could present a fast-forward option for the wrong remote.
Fixed an issue where you could not scroll horizontally on the Commit Graph using the mouse wheel or the two-finger scroll on a trackpad.
Fixed an issue where navigating between commits using the up and down keys did not move the vertical scroll bar if the branch/tag column was hidden in the Commit Graph.
Fixed an issue where the Commit Graph could display a black region after closing an issue view.
Fixed an issue where the Commit Graph would not always take you to the commit when searching.
Fixed an issue where grouped branch/tag nodes would not expand after losing focus on Windows and Linux.
Fixed an issue where synced Azure Workspaces would have duplicate entries in the repositories page.
Moved the branch/tag icons after their name label in the Commit Graph.
Fixed a case where the Focus View was in an infinite loading state if no issue tracker is selected.
Fixed an issue where detached heads were displayed in the TAGS section instead of the BRANCH section of the Left Panel.
Fixed an issue where the context menu would not display when dragging a tag into a local branch.
Fixed an issue where cloning repos from Workspaces would not work if at least 1 repo failed to fetch data.
Fixed flicker on commit selection when holding up/down on the Commit Graph.
Improved performance in the Commit Graph when moving between commits using the up/down keys.
Fixed an issue where inviting users to an organization would silently fail.
Added missing options for detached head context menu: Copy commit sha, Solo, Hide, Create patch and Create cloud patch.
Fixed an issue where GitLab Self-Managed Workspaces would not load repos, merge requests, or issues if a repo was deleted.
Fixed an issue where some deep links may not be recognized by GitKraken Client.
Fixed an issue where patch files containing multi-byte characters could fail to apply.
New actions from Focus View
Focus View is wonderful for reviewing a list of all your pull requests, issues, and WIPs for the repositories in your Workspace. With this release, you may now access actions like "Merge" and "Close" for pull requests, along with options to "Update Status" to update the status field of an issue.
Set permissions for Cloud Patches:
Cloud Patches are here to make it easy to share code and quickly get feedback. This release adds permission settings to the Cloud Patch creation process.
Choose between making the Cloud Patch available to anyone with the link, to people in your GitKraken organization, or to specific collaborators. When you share with a specific collaborator, that person will see the Cloud Patch in the Left Panel when they next open GitKraken Client.

New in GitKraken 9.9.2 (Oct 16, 2023)

New in GitKraken 9.9.1 (Oct 7, 2023)

New in GitKraken 9.9.0 (Oct 5, 2023)

NEW:
Experimental Feature – Cloud Patches:
Share your work with others by creating a Cloud Patch from any WIP node.
Select a WIP to access "Share all files as cloud patch" button in the Commit Panel.
Create a Cloud Patch from staged changes.
Apply a Cloud Patch by following a Cloud Patch URL to open in GitKraken Client and then review the contents in the Commit Panel.
Cloud Patches are organized in the Left Panel, where you may re-apply a patch to your working directory or re-copy the URL.
Focus View now supports pinning and snoozing for PRs and ISSUES.
Experimental Feature – New Commit Graph:
Added "Compact Graph Column" option from Commit Graph settings gear.
Drag and drop to reorder columns.
Added inline commit descriptions.
Improved performance when resizing the app window.
This feature will be defaulted on for all users.
IMPROVEMENTS:
Experimental Feature – Git Executable:
Added revert commit support.
Added pageant ssh agent support.
Focus View now displays an issues status.
BUG FIXES:
Experimental Feature – Git Executable:
Fixed an issue where the commit graph would fail to load in some cases.
Conflicting git config fetch.pruneTags will only be allowed for the main remote.
Fixed a problem with remote actions when a non-standard SSH port was used.
Fixed a problem in Git Executable with known_hosts file on Windows.
Commit signing with SSH can now use a different SSH key than the one used for credentials.
Fixed an issue where the commit message viewer did not change its height when clicked.
Fixed a missing option to remove a repo for Azure Workspaces whose repos were manually added.
Fixed an issue where locating an Azure repo in a Workspace did not save its location.
Fixed a bug where GitLab issue descriptions would disappear when clicking the edit button in the issue view panel.
Fixed an issue where some macOS icon sizes would look distorted.
When immediately committing a cherry-pick or revert:
If there is a conflict, hooks will not be executed.
If there are no changes, no empty commit will be generated.
Fixed an issue where repositories could not be deleted on Windows.
Fixed an issue where the incorrect date/time format would sometimes display in the settings UI.
Fixed an issue where the incorrect locale would sometimes be used for date/time formatting.
Removed unnecessary scroll bars around the commit message field.
Fixed the following issues with gitkraken:// deep links:
Fixed an issue where opening a deep link would prompt users to select a repo even if one of those repos is the active tab.
Partially fixed an issue where opening a deep link would prompt users to select a repo, but only offer slightly-rephrased versions of the same file path. (Some issues are still known with regards to letter casing on Windows, and uncommon file paths.)
Focus View no longer loads Jira Issues set to Done.

New in GitKraken 9.8.2 (Sep 17, 2023)

New in GitKraken 9.8.1 (Sep 8, 2023)

New in GitKraken 9.8.0 (Sep 8, 2023)

New in GitKraken 9.7.1 (Aug 16, 2023)

New in GitKraken 9.7.0 (Aug 10, 2023)

New in GitKraken 9.6.1 (Aug 7, 2023)

New in GitKraken 9.6.0 (Jul 13, 2023)

NEW:
GitKraken Insights in Workspaces:
GitKraken Insights has been moved from the Pull Request page to its own Insights page.
Added a "Last updated date" timestamp.
Added a refresh button for an easier time updating Insights metrics.
Azure DevOps Workspaces:
Users may now create a manually managed Azure DevOps Workspace from a Workspace synced with an Azure Project.
IMPROVEMENTS:
Git Executable:
The Git Executable feature will now be enabled by default for all GitKraken Client users.
Added support for SSH commit signing while using the Git Executable. Commit signing will need to be configured in your gitconfig for now (via gpg.format, user.signingKey, and gpg.ssh.allowedSignersFile). Note that actions that do not currently use the Git Executable (like rebasing) will still use GPG for signing.
Added support for SSH strict host key checking.
Resize commit messages in the Commit Panel to see more (or less) of the message.
First select a commit in the graph to access the resize handle for the commit message in the Commit Panel.
Improved performance of View all files on large repositories.
BUG FIXES:
Pull request panel will once again auto-populate with the commit message when the pull request contains only one commit.
When the experimental "Git Executable" feature is enabled, SSH settings for specific integrations will no longer be overridden by the SSH agent.
Cloud Workspaces:
Fixed Azure DevOps projects not appearing when creating/editing a Cloud Workspace.
Fixed MENTIONED and ASSIGNED TO ME filters on Azure DevOps Cloud Workspaces.
Cloud Workspaces that have already been fetched will no longer disappear when there is an interruption fetching Cloud Workspaces (such as losing connection to the Internet).
Fixed an issue of cannot read properties of null (reading 'match') when using the Git Executable experimental feature.
Failure cases in Workspaces have better error messaging to tell the user what is wrong:
…When GitKraken’s integration permissions have been revoked externally (e.g. from the GitHub website).
…When a Jira administrator attempts to view the issues of a private project which they do not have permission to view.
Fixed an issue where Local Workspaces were not loading.
Fixed issues with adding or viewing Workspaces in the breadcrumbs for repos without a remote.
Fixed an issue where Jira issue types were not loaded after selecting a Jira project.
Fixed an issue where Cherry Picks / Revert completion messages falsely claimed that, "the current branch already has all changes from the commit."
Fixed an issue where button labels were missing when signing in with SSO and more than one provider is available.
Fixed an issue where many auto-fetches could queue up in the background.

New in GitKraken 9.5.1 (Jun 13, 2023)

New in GitKraken 9.5.0 (Jun 8, 2023)

On-Premise:
Git Executable has been enabled for all On-Premise users to allow Git to directly perform actions like fetch, commit, and much more instead of the Nodegit library.
Users may toggle the setting from Preferences > Experimental.
On-Premise and Serverless clients now also benefit from the new first time user experience.
New:
Workspaces got a power boost:
Invite individuals from your GitKraken Org to a Workspace.
Pull all repos in a Workspace using the Pull all button located in the Repositories page.
Preview feature: Added a Complexity column to the Workspace Focus View, Team View, and Pull Requests page:
Complexity is a scale of 1 to 4 that scores a pull request’s complexity based on:
Number of lines changed
Number of files change
Number of commits made
Improvements:
Git Executable has been enabled for all GitKraken Client users to allow Git to directly perform actions like fetch, commit, and much more instead of the Nodegit library.
Provides performance improvements for fetch, commit, and more.
Users may toggle the setting off or on from Preferences > Experimental.
Note: This update will be slowly rolled out within the first week of the 9.5 release.
New user experience improvements:
New users may now start with one of their Cloud Workspaces when launching the app for the first time.
When starting with a Cloud Workspace, the Workspace now opens on the Repositories view.
During onboarding, users can configure SSH keys for integrations.
Improved the URL clone user interface on the new user onboarding.
Workspace improvements:
Added single dropdown to change the time period for all GitKraken Insights metrics.
Added additional options to locate or clone a repository when checking out a branch or viewing a Pull Request from a Workspace.
Updated messaging when opening the Workspace and no integration is connected.
Improved syntax highlighting and additional language support in the GitHub Pull Request View.
Added icons in Pull Request View timeline for comments, requested changes, and reviews.
Added logging for Git commands with GitKraken Client log system.
Requires enabling both the “Git Executable” setting from Preferences > Experimental and the Use extended logging in activity log setting from Preferences.
Support viewing Git hook output using Git Executable feature.
Added option to close login modal using the Esc key.
Bug Fixes:
Fixed case where Git binary wouldn’t fetch from HTTPS remotes on older Linux distros (ex. CentOS-7).
Fixed case where Git binary wouldn’t fetch from HTTPS remotes in Snap installs.
Fixed issue where editing working directory files while multiple commits were selected caused diff display issues for selected commit range.
Fixed delay with loading spinner appearing.
Fixed UI display issue with long emails in the sample commit during the first time user onboarding.
Fixed various “unique key prop” errors in Workspaces.
Azure Issues status now reflects the status options on the main Azure app.
Fixed an issue where users were shown an upgrade button in the issue view panel when the issue’s repo is not cloned or located.
Fixed an issue where the Workspace search bar would disappear.
Fixed an issue where the Workspace repository page would not load a repo’s ahead/behind data.
Git binary no longer incorrectly uses bundled SSH instead of system’s OpenSSH when Use Local Agent”` setting is enabled.

New in GitKraken 9.4.0 (May 8, 2023)

New in GitKraken 9.3.0 (Apr 8, 2023)

New in GitKraken 9.2.1 (Mar 14, 2023)

New in GitKraken 9.2.0 (Mar 7, 2023)

New in GitKraken 9.1.1 (Feb 15, 2023)

New in GitKraken 9.1.0 (Feb 10, 2023)

NEW:
Improved WSL 2 support for the Linux version of GitKraken Client.
Users may now install GitKraken Client in a WSL 2 distribution with WSLg and work with their Linux repos.
For the best experience, we recommend users also install GitKraken Client on their Windows machine to work with repos hosted outside their WSLg distribution.
For installation or upgrade instructions, check out the WSL 2 Help Center documentation.
New encoding support
Configure from Preferences > Encoding or from the top right of any File Diff view.
Users may now bypass Git Hooks when committing after entering a commit message.
GitKraken Insights is now available for Cloud Workspaces connected to Azure DevOps.
IMPROVEMENTS:
Amend (rename) stashes:
Right-click a stash in the graph and then click Edit stash message.
Right-click on a stash in the Left Panel to access Edit stash message.
Click the stash message in the Commit Panel to edit the stash message.
Workspace improvements:
Workspace columns can now be sorted on Repositories, Issues, Pull Requests and WIP tables.
All GitKraken Insights metrics now have a dropdown for changing the time period between 7 days or 14 days for licensed users.
From the Interactive Rebase editor, the first commit can now be set Drop.
BUG FIXES:
Fix submodules update being triggered twice during a Pull (rebase), Rebase, cherry-pick, revert commit, reset, checkout, or undo/redo.
Local Workspaces may now be edited again while working offline.
Users will now get a more helpful message when an integration fails to connect due to a problem with SSL certificate verification.
When amending commit messages, the draggable resize handle will now correctly resize the text box.
When amending commit/stash messages, the summary-line text input will now be focused automatically.
Fixed an issue where Jira Server issues would not show up for a Workspace.
Fixed a timing issue where Shared Workspaces would not show up for Organization owners if the user was not a team member of that Workspace.
Fixed an issue where manually inputting the token to login with GitHub would not save the token for the Github Provider.
Fixed a timing issue that caused branches not to show when relaunching the app from a Workspace.
Improved WSL 2 Support:
We’ve heard that WSL is an essential part of many of our users’ development setup, and as WSL’s popularity continues to grow, we’re excited to start offering some improvements for users working in this environment. To give users an opportunity to have a more native-like experience as quickly as possible, we’ve improved the Linux version of GitKraken Client to fix common issues when operating within a WSL 2 environment.
With 9.1, users may now install GitKraken Client in a WSL 2 distribution with WSLg and better work with their Linux repos. For the best experience, we recommend users install GitKraken Client both on their Windows machine as well as their WSLg Linux distro. This allows users to quickly swap between GitKraken Client on each of their operating systems.
For more information about WSL 2 / WSLg, and the additional features we’ve introduced to better manage GitKraken Client in this environment, check out the Help Center documentation.
WORKSPACE IMPROVEMENTS:
Workspace columns can be sorted on Repositories, Issues, Pull Requests and WIP tables. This should help you better organize your Focus View or Team View.
GitKraken Insights is now available for Cloud Workspaces connected to Azure DevOps, which should help Azure DevOps users measure how fast pull requests get merged.
And all GitKraken Insights metrics now have a dropdown for changing the time period between a 7 day or 14 day time period for licensed users.
QUALITY OF LIFE BOOSTS:
Amend Stash Messages:
Users may now amend stash messages which should make renaming stashes a breeze. Just right-click a stash in the graph and then click “Edit stash message.”
You may also right click on a stash in the Left Panel to access the same option.
Bypass Git Hooks:
Another request from users — you may now bypass Git Hooks when committing. To bypass, first stage changes in a repo with Git Hooks enabled and then start typing your commit message.
You may then click this split button option to commit and bypass the Git Hook.
Encoding Support:
GitKraken Client 9.1 comes with new encoding support for ISO-8859-1, Windows-1252, and many more. To update the encoding for the app’s File Diff view, navigate to Preferences > Encoding and set your encoding selection for the repository.
Alternatively, from any file diff in GitKraken Client, click this dropdown menu in the top right to change your encoding preference.
Of the two options, we recommend users to change the default encoding in their Preferences. That way you’ll be able to read all diffs with the correct characters.
Interactive Rebase “Drop”
And finally, when setting up an Interactive Rebase, you may now set the first commit to Drop.

New in GitKraken 9.0.1 (Jan 5, 2023)

New in GitKraken 9.0.0 (Dec 14, 2022)

“Ready to tear into presents? Santa’s “Workspace” has been coding around-the-clock to release these gifts"
We know how tedious it can be to figure out what repos have recent WIPs and which repos to open next. That’s why we’re so excited to present GitKraken Client 9.0, and transform your development workflow.
This version helps you create a hub for all your repos and makes working with multiple repos a breeze. Plus, with features like Workspaces and GitKraken Insights, you’ll be able to improve your development productivity in no time.
NEW:
Workspaces :
There are now two types of GitKraken Workspaces: Local and Cloud.
Local Workspaces are a new type of Workspace that reference only repositories on your machine.
Select individual repositories, a directory of repositories, or a VS Code Workspace (.code-workspace) to create a Local Workspace.
Local Workspaces can also be created from existing Project Directories in the Repository Management view.
Quickly open repositories in a Repo Tab, or in a VS Code Workspace.
View the currently checked out branch, remote status, and work in progress across all repositories in the Workspace.
View repository details, including the README for each repository in the Workspace.
Fetch all repositories in a Workspace at once.
Cloud Workspaces (previously Personal and Shared) are enhanced with Pull Requests and Issues from hosting and issue tracking services.
Cloud Workspaces can be easily created from Local Workspaces from the Workspace menu.
The Overview is now out of Preview and has been renamed to the Focus View. It displays Pull Requests, Issues, and work in progress that are relevant to you.
The Team Overview is now out of Preview and has been renamed to the Team View. It displays Pull Requests and Issues for everyone on your team.
Tables inside the Focus View and Team View can now be customized to toggle specific columns on/off.
Repositories can now be marked as favorites within all Workspaces.
GitKraken Insights – Preview:
GitKraken Insights measures how fast pull requests are merged into your repositories and more! Get metrics like:
Average Cycle Time: Measures the average time it takes for a pull request to be merged for the selected timeframe.
Average Throughput: Measures the average number of pull requests merged for the selected timeframe.
Merge Rate: The percentage of merged pull requests compared to open pull requests for the selected timeframe.
Open: The total number of pull requests opened for the selected timeframe.
Merged:The total number of pull requests merged for the selected timeframe.
Note: GitKraken Insights will be gradually rolled out to all users. Look for it soon!
Ghost branches:
A “ghost” branch is now displayed when hovering over commits in the graph that shows the closest branch in the BRANCH / TAG column. This can be toggled on/off in Preferences > UI Customization.
Commit highlighting:
Now when you hover over a branch/tag, the associated commits will be highlighted on the graph after a brief delay. This can be toggled on/off in Preferences > UI Customization.
Solo from the graph:
You can now solo branches directly from the context menu of branches in the graph, which hides all other branches and commits.
IMPROVEMENTS:
Workspaces:
The Create Workspace form has been refined to include Local and Cloud Workspace types and to make sharing and adding repositories easier.
The Workspace loading spinner is less-boring 🍭
Improved speed at which Focus View and Team View start to load.
Left Panel:
Resizing sections in the Left Panel now behaves better in edge cases, like pushing several sections at once.
Sections in the Left Panel can now be maximized via context menu to collapse all other sections.
Icons and text in the Left Panel have been aligned and have consistent indents in all sections.
The resize handle for adjusting Left Panel width is now centered on the panel edge.
UI / Themes:
The UI has been refreshed in most views to reduce visual noise. This mostly involved reducing the dependency on background colors to separate sections of content and will be noticeable in custom themes.
Color values in default Light themes have been updated to be generally brighter.
Color values in the Dark (High Contrast) theme have been updated to better separate content after the UI refresh.
Menu bar and context menus will now match the GitKraken Client theme in Windows.
The Mac application icon has been updated to match current Apple guidelines.
Windows and Linux application icons have also been refreshed.
Improved LFS performance for cherry-picking or reverting a commit with a large amount of LFS files.
BUG FIXES:
Fixed an issue where submodules were left uninitialized (even with ‘Keep submodules up to date’ enabled in the preferences) after the following actions:
Undo or redo a checkout or reset hard
Cherry-pick, revert, rebase, interactive rebase, reset, pull
Fixed some theme-ability issues on the toolbar and the New Tab.
Fixed an issue with false positives in private repo detection.
Fixed an error that will occur when Ctrl/Shift clicking within the Left Panel.
WORKSPACES:
Local Workspaces:
GitKraken Client 9.0 brings a whole new way to organize your repos. Users may now create Local Workspaces to group repositories on your machine.
To create a Local Workspace, navigate to the Workspace tab in the upper left of GitKraken Client and click on New Workspace.
Select Local Workspace and then name your Workspace, and browse to select repos to add to your Local Workspace.
Once your Local Workspace is created, you’ll see all your repos grouped together and get the following benefits:
View currently checked out branch for each repo.
Click on any repo name to open it as a tab in GitKraken Client.
Multi-select repos to:
Perform a fetch for the selected repos
Open repos as tabs in GitKraken Client
Use your selection to create a Cloud Workspace (formerly called Personal or Team Workspace)
That’s right! You can also use your Local Workspace to create a Cloud Workspace, which will enable more visibility into your pull requests, issues, and share your Workspace with teams.
Cloud Workspaces:
Formerly known as Personal and Shared Workspaces, Cloud Workspaces are useful for sharing your Workspace with teams along with enabling GitKraken Insights.
Focus View & Team View:
The Focus View, which was previously called the Overview, is now out of Preview and provides a list of all Pull Requests, Issues, Works in Progress that matter to you.
With this release, you may now toggle columns on or off from this gear in the top left corner.
The Team Overview is also out of Preview and is now called Team View. It will show you all pull requests and issues associated with the repos in your Workspace.
And similar to the Focus View, you may now toggle columns on or off from this gear in the top left corner.
GITKRAKEN INSIGHTS:
Next, we’re excited to introduce GitKraken Insights – which measures how fast pull requests are merged into your repositories.
But why does it matter if you track metrics like pull request Cycle Time and Throughput?
“I think an underlying principle that exists is that the longer your code stays away from being merged, the more complicated your workflow is going to become.And so as those changes land and your PR and your change becomes more behind from the main trunk branch, the more likely it becomes you will have to do more work to get that code working again.”
Jeff Schinella, Director of Product
To enable GitKraken Insights, you’ll first need to open a Cloud Workspace and then navigate to the Pull Request section. From here, click to connect to your remote hosting service.
Once the connection is complete, return to the Pull Request section in your Cloud Workspace to view the following metrics for your Workspace pull requests:
Average Cycle Time: Measures the average time it takes for a pull request to be merged for the selected timeframe.
Average Throughput: Measures the average number of pull requests merged for the selected timeframe.
Merge Rate: The percentage of merged pull requests compared to open pull requests for the selected timeframe.
Open: The total number of pull requests opened for the selected timeframe.
Merged: The total number of pull requests merged for the selected timeframe.
GitKraken Insights is currently in Preview, and we’d love to hear your feedback.
UI/UX REFRESH:
Next, we recently released the Commit Graph for GitLens where we learned how to improve the graph even more. We’re delighted to bring those learnings to GitKraken Client 9.0.
Ghost Branches:
In GitKraken Client, you will now see a “Ghost” branch when you hover over a commit. This will show the closest branch that contains that commit. The “Ghost” branch will also show when a commit is selected, and double-clicking that ghost branch will checkout the head of the referenced branch.
Users may toggle this setting on or off from Preferences > UI Customization.
Commit highlighting:
When you hover over a branch, the app will highlight all commits referenced by that branch.
Users may toggle this setting on or off from Preferences > UI Customization.

New in GitKraken 8.10.3 (Nov 8, 2022)

New in GitKraken 8.10.2 (Nov 3, 2022)

New in GitKraken 8.10.1 (Oct 19, 2022)

New in GitKraken 8.10.0 (Oct 12, 2022)

New in GitKraken 8.9.1 (Sep 15, 2022)

New in GitKraken 8.9.0 (Sep 9, 2022)

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.

New in GitKraken 8.8.0 (Aug 11, 2022)

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.
GitKraken may now initiate an Oauth authentication flow with the following supported Identity Providers (IdPs):
Azure Active Directory
Okta
Google Identity Platform
Resources:
Requirements and configuration
Signing in with SSO
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.

New in GitKraken 8.7.0 (Jul 17, 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.
GitKraken Client now supports the ability to create and apply patches.
Create patch from commit(s)
Create patch from uncommitted file(s)
Create patch from Command Palette
Apply patch from Command Palette
Left panel improvements – Left Panel now has a context menu to toggle visibility of the different sections.
New Tab update – Updated UI and layout.
Terminal Tab – Repo aliases will now show in Terminal Tab titles.
More fuzzy search – Enabled fuzzy search in gk history and gk blame commands in GitKraken CLI.
Search tabs list – Users may now search tabs by repo alias in the tabs list.
Naming 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.
Git LFS performance improvements:
Users will see faster performance when cloning LFS repositories with submodules
Users will note much faster performance for general GitKraken Client actions, e.g. reset, merge
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 .
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.
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

New in GitKraken 8.6.0 (Jun 15, 2022)

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 Preferences → Terminal → Default 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 Preferences → General 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}.visualstudio.com) 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.

New in GitKraken 8.5.0 (May 18, 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 when GitKraken is already open will now work as expected.

New in GitKraken 8.4.0 (Apr 12, 2022)

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.

New in GitKraken 8.3.3 (Mar 17, 2022)

New in GitKraken 8.3.2 (Mar 8, 2022)

New in GitKraken 8.3.1 (Mar 1, 2022)

New in GitKraken 8.3.0 (Feb 15, 2022)

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 Preferences → Terminal.
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 Preferences → UI 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.

New in GitKraken 8.2.1 (Dec 21, 2021)

New in GitKraken 8.2.0 (Dec 14, 2021)

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 the 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 the 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 GitHub.com, GitLab.com, or Bitbucket.org.
Themes:
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/README.md.
Users will find two new themes when navigating to Preferences → UI 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 the 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 → Terminal → Cursor 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, the 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 the 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.

New in GitKraken 8.1.1 (Nov 10, 2021)

New in GitKraken 8.1.0 (Oct 15, 2021)

NEW:
The seasons continue to change and so does GitKraken...for the better!
The GitKraken Git 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 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 GitHub.com from the comments inside GitKraken'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.

New in GitKraken 8.0.1 (Sep 28, 2021)

New in GitKraken 8.0.0 (Sep 21, 2021)

NEW:
Introducing the GitKraken CLI Preview:
The GitKraken CLI adds a Git-enhanced, keyboard-driven, terminal experience to the GitKraken Git Client. Get the powerful Git visualizations GitKraken 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 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.
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 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. 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 to the linked repository. The links will focus GitKraken 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'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 now works with the Git Integration for Jira app to allow quick navigation between GitKraken and Jira when viewing commits and file diffs related to Jira issues.
In GitKraken, 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.
To leverage GitKraken’s Git Integration for Jira integration you will need to:
Connect Jira Cloud Integration in GitKraken.
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.

GitKraken Changelog

What's new in GitKraken 9.13.0

New in GitKraken 9.11.1 (Jan 11, 2024)

New in GitKraken 9.11.0 (Dec 15, 2023)

New in GitKraken 9.9.2 (Oct 16, 2023)

New in GitKraken 9.9.1 (Oct 7, 2023)

New in GitKraken 9.9.0 (Oct 5, 2023)

New in GitKraken 9.8.2 (Sep 17, 2023)

New in GitKraken 9.8.1 (Sep 8, 2023)

New in GitKraken 9.8.0 (Sep 8, 2023)

New in GitKraken 9.7.1 (Aug 16, 2023)

New in GitKraken 9.7.0 (Aug 10, 2023)

New in GitKraken 9.6.1 (Aug 7, 2023)

New in GitKraken 9.6.0 (Jul 13, 2023)

New in GitKraken 9.5.1 (Jun 13, 2023)

New in GitKraken 9.5.0 (Jun 8, 2023)

New in GitKraken 9.4.0 (May 8, 2023)

New in GitKraken 9.3.0 (Apr 8, 2023)

New in GitKraken 9.2.1 (Mar 14, 2023)

New in GitKraken 9.2.0 (Mar 7, 2023)

New in GitKraken 9.1.1 (Feb 15, 2023)

New in GitKraken 9.1.0 (Feb 10, 2023)

New in GitKraken 9.0.1 (Jan 5, 2023)

New in GitKraken 9.0.0 (Dec 14, 2022)

New in GitKraken 8.10.3 (Nov 8, 2022)

New in GitKraken 8.10.2 (Nov 3, 2022)

New in GitKraken 8.10.1 (Oct 19, 2022)

New in GitKraken 8.10.0 (Oct 12, 2022)

New in GitKraken 8.9.1 (Sep 15, 2022)

New in GitKraken 8.9.0 (Sep 9, 2022)

New in GitKraken 8.8.0 (Aug 11, 2022)

New in GitKraken 8.7.0 (Jul 17, 2022)

New in GitKraken 8.6.0 (Jun 15, 2022)

New in GitKraken 8.5.0 (May 18, 2022)

New in GitKraken 8.4.0 (Apr 12, 2022)

New in GitKraken 8.3.3 (Mar 17, 2022)

New in GitKraken 8.3.2 (Mar 8, 2022)

New in GitKraken 8.3.1 (Mar 1, 2022)

New in GitKraken 8.3.0 (Feb 15, 2022)

New in GitKraken 8.2.1 (Dec 21, 2021)

New in GitKraken 8.2.0 (Dec 14, 2021)

New in GitKraken 8.1.1 (Nov 10, 2021)

New in GitKraken 8.1.0 (Oct 15, 2021)

New in GitKraken 8.0.1 (Sep 28, 2021)

New in GitKraken 8.0.0 (Sep 21, 2021)

New in GitKraken 7.7.2 (Aug 16, 2021)