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.0 (Dec 14, 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.10.0 (Nov 8, 2023)

New:
Commit and push! Added an option to auto-push on commit.
Stage changes and type a commit message to access option for commit and push.
You can set the default behavior of the commit button for each repo under Preferences -> Commit
You can now snooze a Focus View item for a set duration.
Improvements:
Enabled Cloud Patches by default.
You can now easily share your changes with other developers by creating a Cloud Patch from your WIP or from the context menu of any commit. Copy the generated link to share the changes.
Added ability to delete Cloud Patches from Left Panel.
Toggle feature on or off in Preferences > Experimental.
Experimental Feature – Git Executable:
Provided more information about SSH supported versions on Windows in Experimental Settings.
Added support for Pull (fast-forward if possible) and Pull (fast-forward only).
Added cherry-pick support.
Focus View improvements:
Added a clear button to the Focus View search bar.
Added a refresh button to the Focus View.
Added a helpful warning when signing with an SSH key, and the configured key is a public key, but the corresponding private key has not been added to the SSH Agent.
Added the ability to turn off commit lazy loading on the Commit Graph in Preferences.
Added the ability to set how to display commit message descriptions in the Commit Graph.
Added emojis support for commits messages on the Commit Graph.
Bug Fixes 🐛
Experimental Feature – Git Executable:
Show info toast to remove user from remote url if integration is used.
Fixed a problem with SSH_ASKPASS in Windows 10.
Fixed GPG signing with passphrase not working when using installed git version (Windows).
Improved PuTTY detection.
SSH credentials prompt when not using the Git Executable will now show the SSH key file path, not the remote URL.
Improved performance in Commit Graph when opening a repository with thousands of grouped branches / tags.
Improved loading time of avatars in the Commit Graph when switching tabs.
Fixed an issue where the displayed number of items in the Focus View tabs was incorrect.
Fixed an issue where the Commit Graph may display lines incorrectly.
Fixed an issue where duplicate WIP items would appear in the Focus View repos with the same local path but different remotes.
Fixed an issue where users on older dpkg versions may not be able to install the debian package.
Fixed an issue in Commit Graph when hovering over annotated tag icon, the tag message was not appearing in the tooltip.
Fixed an issue that was preventing the drag and drop of soloed and hidden branches with the Commit Graph.
Fixed an issue where the prompt to refresh the GitLab token would appear more often than required.
Fixed an issue where Cloud Patch links would not work if the app was closed on macOS.
Fixed an issue where the scroll position resets after closing a diff view with the Commit Graph.
Fixed an issue with branch check out from the dropdown menu of a grouped branch.
Fixed an issue where the Focus View is in a infinite loading state when failing to load pull requests or issues.
Fixed an issue with deleting unsaved branch names when scrolling away from the branch name input.

New in GitKraken 9.9.2 (Oct 14, 2023)

New in GitKraken 9.9.1 (Oct 14, 2023)

New in GitKraken 9.8.2 (Sep 16, 2023)

New in GitKraken 9.8.1 (Sep 7, 2023)

New in GitKraken 9.8.0 (Sep 6, 2023)

New in GitKraken 9.7.1 (Aug 16, 2023)

New in GitKraken 9.6.1 (Aug 1, 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 13, 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 10, 2023)

New in GitKraken 9.3.0 (Apr 7, 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 16, 2023)

New in GitKraken 9.1.0 (Feb 8, 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.
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)

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.
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.
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.2 (Nov 3, 2022)

New in GitKraken 8.10.1 (Oct 19, 2022)

New in GitKraken 8.10.0 (Oct 11, 2022)

New in GitKraken 8.9.1 (Sep 16, 2022)

New in GitKraken 8.7.0 (Jul 14, 2022)

New in GitKraken 8.6.0 (Jun 15, 2022)

New:
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:
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:
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)

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.
NoteSignificant 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.

New in GitKraken 8.4.0 (Apr 12, 2022)

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 16, 2022)

New in GitKraken 8.3.2 (Mar 7, 2022)

New in GitKraken 8.3.1 (Mar 1, 2022)

New in GitKraken 8.3.0 (Feb 14, 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 22, 2021)

New in GitKraken 8.2.0 (Dec 13, 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:
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 14, 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
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
Deep Linking:
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.
Jira App Integration - Git Integration for Jira:
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.
Improvements:
The Fuzzy Finder is now the Command Palette!
Tab navigation has been significantly improved when many tabs are open at once.
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:
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.

New in GitKraken 7.7.2 (Aug 10, 2021)

New in GitKraken 7.7.1 (Jul 29, 2021)

New in GitKraken 7.7.0 (Jul 13, 2021)

New:
Talent wins games, but teamwork and intelligence win championships…
Introducing GitKraken Teams.
GitKraken users with Pro and Enterprise Cloud accounts can now create and manage teams within their organization.
Organizations are now visible in Preferences in each user's Profile. From this view:
All team members can view a list of other members in the organization, as well as the members in any team to which they belong
Administrators can create and manage teams.
Administrators can also invite, remove, or change the role of members in an organization.
Team collaboration features.
Team View.
View a list of members in your team in the left panel.
See which files and branches your fellow team members are currently working on.
To avoid merge conflicts, files you and a team member both have changes on are marked with a warning icon ⚠️.
Graph filtering. Filter the Author column of the commit graph by Team and/or collaborators to highlight work committed by your team.
New Pull Request section:
Pull request filtering.
The following filters are included by default to help focus PRs most important to users, with some options specific to certain hosting providers:
My Pull Requests.
All Pull Requests.
Assigned to me.
Awaiting my review.
Custom filters can also be created for all supported integrations.
All filtered pull requests can now be easily searched.
New status icons will now indicate CI/CD status as well as request status of pull requests, depending on the hosting provider.
Improvements:
It is literally true that you can succeed best and quickest by helping others to succeed…
Diff hunks are now copyable from the Pull Request view.
Updated and new GitHub Actions templates.
Any form submission will now be focused, making for more convenient submission with tab/enter.
Bug Fixes:
We think, mistakenly, that success is the result of the amount of time we put in at work, instead of the quality of time we put in…
Commits from interactive rebases will resume being signed.
Tab navigation issues resolved.
Notifications settings will no longer always be detected as offline.
The merge tool window will no longer extend off the right of the screen.
When in a detached head state the pull dropdown is now enabled to allow fetching.
Notes:
If I have seen further, it is by standing on the shoulders of giants...
GitHub is deprecating user/pass authentication, we have added an in app notification to prepare users of this upcoming change.

New in GitKraken 7.6.1 (May 19, 2021)

New in GitKraken 7.6.0 (May 12, 2021)

New in GitKraken 7.5.5 (Apr 12, 2021)

New in GitKraken 7.5.4 (Apr 6, 2021)

New in GitKraken 7.5.3 (Mar 26, 2021)

New in GitKraken 7.5.2 (Mar 3, 2021)

New in GitKraken 7.5.1 (Feb 9, 2021)

New in GitKraken 7.5.0 (Jan 21, 2021)

New in GitKraken 7.4.1 (Nov 30, 2020)

New in GitKraken 7.4.0 (Oct 28, 2020)

New in GitKraken 7.3.2 (Sep 11, 2020)

New in GitKraken 7.3.1 (Sep 9, 2020)

New in GitKraken 7.3.0 (Aug 26, 2020)

New in GitKraken 7.2.0 (Aug 4, 2020)

New in GitKraken 7.1.0 (Jul 13, 2020)

New in GitKraken 7.0.1 (Jun 8, 2020)

New in GitKraken 7.0.0 (May 20, 2020)

New in GitKraken 6.6.0 (Apr 21, 2020)

New in GitKraken 6.5.4 (Mar 9, 2020)

New in GitKraken 6.5.3 (Feb 21, 2020)

New in GitKraken 6.5.2 (Feb 20, 2020)

New in GitKraken 6.5.1 (Jan 28, 2020)

New in GitKraken 6.5.0 (Jan 23, 2020)

New in GitKraken 6.4.0 (Dec 12, 2019)

NEW:
A long time ago in a galaxy far, far away...was a Git GUI without activity logs.
Introducing Activity Log! Users can now view all Git actions made to repositories and all application actions made in GitKraken through activity logs. Access this feature through the new icon in the footer toolbar.
To access the activity log for a repository, navigate to the repo’s tab and click the icon. You will then see any Git actions made in the repo listed in chronological order on the tab titled Repository.
To access the activity log of local application changes made in GitKraken, click the icon. You will then see all application changes listed in chronological order on the tab titled Application.
The progress of Git hooks can also be tracked through activity logs. All Git hooks within the repository's log contain a clickable link where you can click to view the hook’s output in a separate tab.
IMPROVED:
We polished our lightsabers and dusted off our droids to make these improvements your new reality.
The appearance of the dropdown menu that displays when selecting a repository to clone has been improved for consistency.
We have added additional context to the error message that displays when opening a pull request with a remote ref that doesn’t exist.
Commit author names are now displayed on hover above commit nodes in the graph instead of below them.
BUG FIXES:
We built up a Resistance to these unwanted bugs.
When opening GitKraken, if the most recent tab is not a Glo Boards tab, and the user switches to or opens a new Glo tab, the Glo Board is now correctly in focus.
Commit search now closes upon opening the Fuzzy Finder.
Editing a file to a previous state no longer creates an empty WIP node.
Users cannot use keyboard shortcut Cmd/Ctrl + F to search commits when the graph is blocked by a prompt for input (as search results would not be visible behind the prompt’s display box).
The button on a new tab now works as expected.
Bitbucket remote origins now correctly display their name instead of displaying undefinied.
GitLab users can view and create pull requests from repositories in subgroups.
Users will be appropriately directed to Account Management in the application after clicking during the free trial period.
Users will no longer be prevented from interacting with collapsed left panel items.
Users with multiple profiles can now successfully delete the first profile created from that account.
Folders will be created when cloning a repository on Windows.
SECURITY:
This release includes fixes for the following vulnerabilities:
CVE-2019-1348
CVE-2019-1349
CVE-2019-1350
CVE-2019-1351
CVE-2019-1352
CVE-2019-1353
CVE-2019-1354
CVE-2019-1387

New in GitKraken 6.3.1 (Nov 5, 2019)

New in GitKraken 6.3.0 (Oct 15, 2019)

New in GitKraken 6.2.1 (Sep 25, 2019)

New in GitKraken 6.2.0 (Sep 12, 2019)

New:
The country might be small, but its fortunes large. Trust us, this new GitKraken feature calls for a top-shelf martini. Shaken...not stirred. 🍸
The GitKraken merge conflict tool and built-in code editor have been updated with performance improvements affecting scrolling, output editing, and conflict line selection. The GitKraken merge tool now utilizes Monaco Editor, the same editor found in VS Code, which gives users the ability to independently search within the three separate conflict windows using the keyboard shortcut Cmd/Ctrl + F. Extra gold for Paid users: the code editor’s output now has auto-complete capability.
Improvements:
These latest improvements to the GitKraken Git Client are shocking...positively shocking.
Significant UI improvements have been made to the commit panel, including more recognizable file status icons, easier view of file names, and more.
Escape guarding has been added to the Pull Request panel. Now, if you add text in any field on the PR template form, you will not be able to close the panel without clicking the X button at the top right of the panel.
Users can again push a tag after it has been moved locally.
GitKraken will now select the WIP node instead of the HEAD node when detecting a merge conflict.
Bug Fixes:
Because a world with these bugs is not enough… M’s orders
Date and time settings set by the user will now be respected.
When trying to pop a stash created from outside of GitKraken, users will no longer receive an error message.
If the commit message is empty, the create commit keyboard shortcut will no longer create a commit.
Unless the diff view has been focused, Esc will close the diff views.
Creating a workflow with the same file name as an existing workflow will no longer close the GitHub Actions panel.
The Ignore and stop tracking feature will now correctly remove the ignored file from the index.
When editing a file inside of GitKraken using our code editor, a user’s line ending preference will apply the correct line ending.
When merging two conflicting branches, the correct commit message will now be generated.
Users no longer need to hit the Save button twice when closing the merge conflict tool.

New in GitKraken 6.1.4 (Aug 21, 2019)

New in GitKraken 6.1.3 (Aug 21, 2019)

New in GitKraken 6.1.2 (Aug 21, 2019)

New in GitKraken 6.1.1 (Aug 21, 2019)

New in GitKraken 6.1.0 (Aug 8, 2019)

New:
Get out your magnifying glass and prepare to search like you never have before, Detective.
Users can now easily search inside the graph for commits by message, author, or SHA. Access this feature with the keyboard shortcut Ctrl/Cmd + F or click on the toolbar’s search icon. While searching, use Enter or ↓ to view the next result in the graph, or Shift + Enter or ↑ to view the previous result.
New GitHub Actions integration! Users can now add, edit, and delete GitHub Actions workflows inside of GitKraken. The GitHub Actions section will appear in the left panel for repositories with a GitHub upstream or any repository with the .github/workflows directory. Choose from several workflow templates to get started.
Improvements:
We might not have a thunderstone, but we’ve leveled-up GitKraken with these improvements.
The integration tabs under Preferences → Authentication have been changed to a vertical layout.
The merge conflict warning when opening a pull request will now display a list of conflicted files.
An un-bundled version of GitKraken’s strings file has been added. Users can edit/replace for use in non-officially supported languages. This file can be located at {appLocation}/Resources/app.asar.unpacked/src/strings.json.
More Keif avatars have been added to profiles.
An option has been added to the Fuzzy Finder to view GitKraken release notes.
Bug Fixes:
Our small yellow friend helped us thunder shock these bugs into oblivion.
Users will no longer encounter the error message caused by .gitignore negation rules, Checkout failed: error matching pattern due to .gitignore, when checking out a branch.
Users can now change the project group name casing when renaming a project group.
When initiating a push and pull request through the context menu, the Pull Request panel will now appear once the local branch has finished pushing to your remote.
The reset branch context menu will now perform as expected after dragging a branch onto another reference in the graph.
We (really) have fixed an issue with authentication for Bitbucket servers when the username is an email address.

New in GitKraken 6.0.1 (Jul 16, 2019)

New:
It might take some time to get used to these new powers features, but we’re confident you’ll be shooting webs from your hands in no time.
This one’s for you Aunt May. Users can now configure location notifications in GitKraken by going to Preferences -> UI Preferences -> Notification Location.
The message box for commits is now resizeable.
Users can now use the keyboard shortcut Shift + J (or Shift + ↓) to jump to the parent commit of a selected commit.
Similarly, users can also use the keyboard shortcut Shift + K (or Shift + ↑) to jump to the child commit of a selected commit. No webs required.
Improvements:
Like Spidey’s new suit, it’s as if Stark himself helped with these technical improvements (we miss you Tony!)
The Fuzzy Finder will now filter search results based on frequency of function use.
When you hover over an author/committer name, a tooltip of their email address will display in the commit panel.
A caps lock warning notification will now appear in all password input fields.
A tooltip has been added to Project Groups to display the directory path.
Bug Fixes:
We got some help from our friendly neighborhood Spider-Man to control the GitKraken bug population.
Now, if there is a corrupt reference in the repository, the graph and its branches will still display.
The Commit Changes context menu and button options for submodules will now work properly.
GitKraken will no longer take an extended time to timeout when switching to a tab with an inaccessible remote repository.
Users can now focus the Fuzzy Finder search box by selecting the search commit icon.
Extra new tabs will no longer generate when relaunching GitKraken if you have the Remember Tabs setting disabled.
The Mac keyboard shortcut Cmd + Q will quit GitKraken if Glo is open.
Bitbucket Server users who have email addresses for their usernames can now successfully integrate their repositories.
Merge commits will no longer have unknown authors if the global gitconfig has no email address.
The appropriate branch will now appear in the working directory when performing a branch checkout through the command line.

New in GitKraken 6.0.0 (Jun 18, 2019)

New:
No need to keep Tabs on this journey. Launch systems are a go. 3. 2. 1…...
TABS...sip, ah. The speed and performance improvements involved in v6.0 has finally made switching between multiple repos in the form of tabs possible! Users can also use Tabs to switch between repos and Glo Boards.
If a merge conflict exists between your source and the target branch, a Merge Conflict Detected! error message will now directly appear in the pull request template panel when attempting to initiate a pull request.
Improvements:
Like a Nascar pit crew, our team spruced up the physical performance of GitKraken to achieve peak racing form. Prepare for lightspeed…
The startup time of GitKraken is up to 2.3x as fast!
The application size has been reduced by approximately 100MB for MacOS users.
It will feel like taking a Buggati for a spin. Checkout in LFS is now 14x as fast!
Newly created pull requests will display much faster.
Toast notifications have been moved from the upper right corner to the lower left corner of the central UI to avoid blocking important information.
File History and Blame views load up to 20x as fast! Top that Usain!
Bug Fixes:
Flash! We’ve zapped these slow pokes out the way!
Users will no longer encounter the error message Cannot read property isGitHookError of undefined when finishing a release branch through GitFlow.
Commits will no longer appear detached from their respective branch if a child commit’s date is older than the parent’s commit date.
Self-hosted remote services with a domain containing a custom port or path will now be supported through GitKraken’s integration feature.
All folders in Tree View can now be expanded.
When using the Bitbucket.org integration, duplicate repositories will no longer appear in the clone menu.
When using the Azure DevOps integration, repositories will be listed alphabetically on the clone menu.
Users with their autoCRLF set to input will no longer have line endings converted to CRLF when resolving a conflict.
Submodules will no longer be not initialized after discarding submodule changes.
Commit message text now wraps correctly inside of the commit message box.
Several GPG-related bug fixes have been applied, including:
All merge conflicts will now be signed after selecting the Sign commits by default checkbox.
The error notification message will be more descriptive when attempting to generate a GPG key with a name not provided in a user’s profile.
If using older versions of GPG, users will no longer encounter a gpg: invalid option --pinentry-mode error notification.
Annotated tags on Windows will now be correctly signed.

New in GitKraken 5.0.4 (Mar 28, 2019)

New in GitKraken 5.0.3 (Mar 27, 2019)

New in GitKraken 5.0.2 (Mar 16, 2019)

New in GitKraken 5.0.1 (Mar 13, 2019)

New in GitKraken 4.2.2 (Feb 7, 2019)

New in GitKraken 4.2.1 (Jan 23, 2019)

New in GitKraken 4.2.0 (Jan 3, 2019)

New in GitKraken 4.0.6 (Oct 13, 2018)

New in GitKraken 4.0.5 (Sep 20, 2018)

New in GitKraken 4.0.4 (Sep 15, 2018)

New in GitKraken 4.0.3 (Sep 12, 2018)

Features:
Added editor settings to change the font size and family. This setting is located under Preferences → Editor Preferences.
Added a setting to remember the last opened repository on startup. This setting is located under Preferences → General.
Added an editor setting and Fuzzy Finder option to toggle syntax highlighting on and off. This setting is located under Preferences → Editor Preferences.
Added a context menu option to delete all branches within a branch folder (local branches only).
Added the ability to change theme from the Fuzzy Finder.
Improvements:
Using the stage all and unstage all keyboard shortcuts (Ctrl/Cmd + Shift + S & Ctrl/Cmd + Shift + U) will now select the WIP node.
Disabled several keyboard shortcuts when no repository is open.
In the repository management window under the recently opened tab, a browse button has been added if there are no recently opened repositories available.
When viewing a file, Ctrl/Cmd + W will close the file instead of closing the whole repository.
When performing a Fetch or Pull, the text under the loading icon will now reflect which action is being performed.
The prompt to notify a file has been modified externally has been reworked and improved.
The sliding panels for Git Flow, Remotes, Pull Requests, and Submodules have been expanded.
Bug Fixes:
For GitLab.com users, context menus will now be generated for the currently checked out commit.
Tooltips should no longer linger when clicking buttons in the top toolbar.
Unstaging the last hunk of a file would sometimes cause that file not to appear in the unstaged list. This has been fixed.
Esc will once again close the PR panel.
The graph will no longer disappear after creating or editing a file inside of GitKraken.
Resolved an issue that would cause the File View to blank out when staging new additions to a file.
When using Glo inside of GitKraken, Ctrl/Cmd + / will no longer open both GitKraken and Glo’s keyboard shortcut menus.
The discard button should no longer cause the commit panel to shift when multi-selecting files in the staging/unstaging panes.

New in GitKraken 4.0.2 (Aug 20, 2018)

New in GitKraken 4.0.1 (Aug 14, 2018)

New in GitKraken 3.6.6 (Jul 13, 2018)

New in GitKraken 3.6.5 (Jul 12, 2018)

New in GitKraken 3.6.4 (Jun 19, 2018)

New in GitKraken 3.6.3 (Jun 1, 2018)

New in GitKraken 3.6.2 (May 30, 2018)

New in GitKraken 3.6.1 (May 15, 2018)

New in GitKraken 3.6.0 (May 1, 2018)

Features:
Mission Control, we are a go for total pull request management! Users can now do the following when creating a pull request through GitKraken:
GitHub.com & GitHub Enterprise:
Add assignees
Add reviewers
Add labels
GitLab.com & GitLab Self-hosted:
Add an assignee
Add labels
Is your pull request go for launch? GitHub users: GitKraken will now display the status of pull requests in the left panel. Hovering over a pull request will provide a summary of information on a build’s status.
Typos can be costly, so we’ve added spell checking to the commit message box, pull request panel, and the commit template field.
Quickly propel yourself into your repo folder from the new file menu option that allows you to open your repository folder in your default file manager.
You can also use the keybind Alt + O.
Reduce the drag on your graph by using the new context menu option to Hide all tags
Improvements:
Looking for more pull request info on the fly? Tooltips for open pull requests have been redesigned and should be easier to read.
GitKraken will now display tag annotations. Let everyone know how amazing your code is
Selecting the button from the Clone window will now take users to the hosting service tab instead of the general authentication tab.
Switch repos at light speed! Ctrl/Cmd + Shift + O now opens the Fuzzy Finder with the open repo option preselected.
Bug Fixes:
You shouldn’t be faulted for writing a thorough commit message, so we resolved an issue that prevented users from accessing their submodules if the last commit message was very long.
Amending a commit message using the commit keyboard shortcut should properly amend the commit instead of creating a new one.
We managed to fit this one in: long branch names will no longer go off of the Git Flow panel.
[GitLab Self-Hosted] users: Initializing a public repository through GitKraken would actually make the repository private; this has now been fixed.
We’re all for resolving conflicts, especially ones that aren’t really there. For repositories on FAT32 or NTFS drives, GitKraken should now correctly checkout the branch instead of throwing conflict errors.

New in GitKraken 3.5.1 (Apr 5, 2018)

New in GitKraken 3.5.0 (Mar 27, 2018)

Features:
Presto! Commit message D-N-A! You can now create commit message templates for each of your repositories
For those times when you can’t network eight connection machines and debug two million lines of code all on your own, GitKraken will now display co-authored commits!
Improvements:
Looking for that perfect iteration? We’ve added a context menu option to copy a commit SHA.
Buried repos should stay buried; so GitKraken will no longer display archived GitLab repositories in the clone window.
Since you can’t discard and stage hunks when viewing the diff of an untracked, removed, or renamed file, we’ve eliminated the temptation by removing those buttons.
We consulted a mathematician and fixed the selection algorithm for unstaged/staged files, so it now respects Z-A sorting.
Must code faster, must code faster! GitKraken will now perform an LFS pull after a clone or submodule initialization, when necessary.
You don’t always have to force reboot the system, but you might need to force push some commits. For VSTS users, force pushing to a branch when you do not have the force push permission enabled will now provide a more detailed error message.
Bug Fixes:
That is one big pile of commits. The squash option should now appear after rebasing commits.
Life...finds a way... Just like Keif has found a way to fetch PRs from a repository that is in a nested group on GitLab.
T-Rex is much shorter, but we realize you can’t always abbreviate. Profiles with long email addresses and names should no longer be cut off in the dropdown menu.
Nuh-uh-uh, you didn’t say the magic word! The Repository Management window will no longer freeze up after removing an account from the initialize repository form.
WIP changes shouldn’t go extinct. Starting a new Gitflow branch would cause some WIP changes to vanish—that should no longer happen.
Commit selection shouldn’t have to be explained by chaos theory. So Shift + click between two commits should now select all commits in between the selection instead of randomly omitting a few.

New in GitKraken 3.4.1 (Mar 16, 2018)

New in GitKraken 3.4.0 (Mar 7, 2018)

New in GitKraken 3.3.4 (Jan 29, 2018)

New in GitKraken 3.3.3 (Jan 22, 2018)

New in GitKraken 3.3.2 (Dec 15, 2017)

New in GitKraken 3.3.1 (Dec 7, 2017)

New in GitKraken 3.3.0 (Nov 27, 2017)

New in GitKraken 3.2.2 (Nov 14, 2017)

New in GitKraken 3.2.1 (Oct 31, 2017)

New in GitKraken 3.2.0 (Oct 30, 2017)

New in GitKraken 3.1.2 (Oct 17, 2017)

New in GitKraken 3.1.1 (Oct 10, 2017)

New in GitKraken 3.1.0 (Oct 4, 2017)

Features:
We’ve given the commit panel a Cinderella-style makeover! It has a new header and can be pinned to the right or bottom of the window as you prefer.
The “Discard All” button has been replaced with a trash can icon on the left side of the new panel header. This should reduce the chance of accidentally clicking it when staging changes.
Wash the dishes, do the dusting,
Do the staging, make the commits!
When viewing a commit, the SHA for that commit is displayed in the new panel header (and copyable with a click).
When viewing the working directory, the new panel header will tell you how many files have been changed and display the name of the branch styled to match the label in the graph.
When in a conflicted state, messaging will now correctly reflect whether the state was the result of a rebase or a merge. The branches involved are now also styled to match their labels in the graph.
The list/tree view dropdown menu has been replaced with a new toggle button.
Quickly jump to your working directory when viewing older commits, with a new shortcut that appears at the top of the commit panel.
Now you can collapse the unstaged and staged files sections to make more room for viewing file changes in the commit panel.
A checkbox to view all files is now available when viewing a previous commit. This allows you to browse and view all files in a repository as they were at that commit.
External diff tools are now supported. Set the tool you prefer to use for viewing diffs in Preferences > General.
We added a context menu option to copy a branch’s name from the left panel or the graph.
There’s now a full-file contents view when viewing a diff of a commit. Users are able to toggle between viewing solely the diff hunks with changes, or the entire file with the changes applied.
Improvements:
This makeover came with new and improved easy-to-see scrollbars! 📜
But the thingamabob that does the job is bibbidi-bobbidi-boo.
Background colors and other styling has been improved for both light and dark themes wherever code is displayed (e.g., the new full file contents view, the diff view, file history view, and the conflict resolution tool). This should make code easier to read by improving text contrast and further differentiating code views from other panels in the application.
Bug fixes:
Linux users, this one’s for you! Update buttons are much easier to see now.
Links to the EULA will now correctly take you to our EULA page (previously, it would do nothing… whomp, whomp).
Once upon a time, in Windows, GitKraken would occasionally crash when viewing a diff. Issue addressed.

New in GitKraken 3.0.2 (Sep 28, 2017)

New in GitKraken 3.0.1 (Sep 19, 2017)

New in GitKraken 3.0.0 (Sep 7, 2017)

New in GitKraken 2.7.1 (Aug 16, 2017)

New in GitKraken 2.7.0 (Jul 18, 2017)

New in GitKraken 2.6.0 (May 24, 2017)

New in GitKraken 2.5.0 (May 3, 2017)

ike the Flash, GitKraken now has the power of superspeed. In addition to numerous improvements and fixes across the board, this release also drastically speeds things up for Windows users.
Oh, and checkout operations are as much as 3 times faster than SlowTree, err... I mean SourceTree (including their latest v2).
Speed/Performance Enhancements:
(Windows) File history rendering is now much faster.
(Windows) Rebasing a series of commits is now quicker.
(Windows) Checkouts are more than 60% faster than they were in v2.4.
(All OSs) Graph rendering is more efficient.
Improvements:
There’s nothing like a good, old-fashioned error. We’ve updated some of GitKraken’s error messages to be more descriptive.
We’ve also better named stashes.
Pushed tags are now identifiable.
When opening a file’s history, the first diff is now shown as a priority, before loading the rest of the history.
When adding a new SSH key, hitting the enter key will now add the key, rather than you having to click a button like some kind of caveman.
The commit button now includes a file count number.
Bug Fixes:
Deleted repos would delete just fine, but would persist as ghostly memories by stubbornly appearing in the fuzzy finder, even post-deletion. We’ve performed an app-wide exorcism and that seems to have worked.
Restarting Windows with GitKraken open would make GitKraken forget the currently open repo, but not anymore!
The command palette was not always showing every option it was supposed to show. It now shows everything it should.
Cherry-picking a commit when the changes are already present was creating a commit with no files. Sad! Fixed.
“Ignore whitespace” has sometimes worked, sometimes not, and fluctuated between the two states. It now super works.
Pushing or switching branches, then quickly creating a PR wasn’t then showing the branch. This was described by our QA guys–masters of understatement–as “pretty annoying,” and has been corrected.
In some cases, the merge tool was messing up line endings. No more!
The diff viewer was also overlapping lines of code at times, which made review tricky. Everything is orderly once more.
Generating a new SSH key in Ubuntu 16 could crash GitKraken. That’s a bug and we have fixed it, with apologies.
Fixed an issue where double-clicking a hidden remote would trigger an error. No more unhiding and rehiding!
When blaming, you need your facts in hand. Viewing the blame entry in the file history now includes the date and commit title.
Cloning a repo with submodules would throw an error if the user chose to initialize the submodules. This should now work as expected.
Undoing the deletion of a branch would restore the branch, but would fail to retain any upstream that had been set. GitKraken now remembers all.
Fixed some quirky styling to the toolbar breadcrumbs.
Repositories with the same name can now exist and appear in the same project group. Though this was allowed before, it resulted in only one of the repos being listed in the group. Now all repos display as they should.
Submodules will no longer appear in project groups by default.
Following a rename in the blame view meant you couldn’t get back to where you started, but now you can!
Navigating blames now retains your scroll position to help you better trace code changes.

New in GitKraken 2.4.0 (Apr 19, 2017)

Improvements and Fixes:
Dude, your WIP is showing. Submodules now update correctly when switching branches so a work-in-progress isn’t incorrectly created as if you changed something.
Inception-themed performance improvement: Submodules now initialize faster and recursively (if a submodule has submodules).
In Repo Management, project group names can now be edited with a simple double-click.
In Repo Management, found repos sorting has been upgraded from sort of kind of alphabetical and a little bit the order in which found to actually alphabetical, for real.
Resolving merge conflicts in GK no longer replaces CRLF line endings with LF line-endings. Believe it or not, this happened to some users.
If you check out a remote beyond the graph history (>2000 commits), GitKraken correctly creates a local ref and works now.
Deleting a file then creating a branch at the same commit would resurrect the deleted file from the grave. Yes, it’s Easter; no, this doesn't make it ok. It’s incorrect behavior, and we’ve fixed it.
Using GitKraken in fullscreen mode? Closing GitKraken in fullscreen mode? Opening it again? If this sounds like you, you’re going to love this one: The app will now remember if it was closed in fullscreen mode and, if it was, will launch in fullscreen mode.
GitKraken also now remembers where it was positioned after being closed while maximized or fullscreen in Windows.
In the fuzzy finder, “finder”, “explorer”, and “folder” have been included as additional keywords to open in file manager. Did you know we had a fuzzy finder? Oh you’ll just love it! Use the keyboard shortcut command + p / ctrl + p and start typing.
Keif got better at math and the commit sorting algorithm was improved as a result. You’ll notice an increase in application speed when refreshing.
Fixed issue where pushing a branch that doesn’t have an upstream ref would cause an error.
In the Keyboard Shortcuts modal, the shortcut for “filter left panel” is now correct. FYI that shortcut is command + option + F (Mac) / Ctrl + Alt + F (Windows/Linux).
If you delete a local branch that was not checked out and then try to undo that action, it actually undoes the action, rather than not.
UI fixes / improvements:
Lightened the shadows between the graph and the ref label / commit message columns in light theme.
Fixed "disabled" button styles in toolbar when certain actions are in progress.
Styles for new branch name input are now consistent with other inputs.
Fixed some margin and button styling issues in file view.
"Default" button styling is improved and more consistent throughout the application.

New in GitKraken 2.3.3 (Apr 7, 2017)

New in GitKraken 2.3.2 (Apr 6, 2017)

New in GitKraken 2.3.1 (Apr 4, 2017)

New in GitKraken 2.2.1 (Mar 23, 2017)

New in GitKraken 2.2.0 (Mar 9, 2017)

NEW FEATURES:
GitLab Integration: GitLab users rejoice! GitKraken now integrates with your accounts! Enjoy the following conveniences from within GitKraken: ?Adding and removing SSH keys: From Preferences ? Authentication, you can now quickly generate and manage your keys
Initializing a repo
Cloning a repo from a GitLab account
Viewing GitLab remote avatars in the graph
Users have requested that the repo management interface be tidier and more intuitive, so the new Repository Management View has been created as an entirely different way to organize and open repos. Happy now?
In the Repository Management view, users can now: ?Browse the file system for a repo to open
Open a repo from a list of recently opened repos
Create custom project folders that contain groups of repos: Folders that contain groups of repos can now be added to GitKraken as Project Folders which can be discretely named in the app
You can clone and init repos as usual, don’t panic. It’s all fine.
Avatars in the left panel for remotes: As with the graph, viewing copious remotes can get a little confusing. Remotes now display, where possible, avatars to make them more immediately identifiable.
HTTP and proxy credentials storage: When entering a username/password for a host, GitKraken will now ask if you’d like to remember those credentials. Stored credentials can be cleared in Preferences ? Authentication. Sincere apologies I couldn't make this sound more interesting. I tried in a blog post too, but didn't succeed there either. Sigh.
IMPROVEMENTS:
Hovering over a pull request in the left panel reveals a tooltip that wasn’t the easiest to read. We’ve improved the layout to be cleaner and more legible.
BUG FIXES:
Fixed an issue where GitKraken might botch permissions when generating SSH keys. This could lead to lax permissions, the key not being used, and no-one being able to have nice things. These permissions are fixed.
Closing GitKraken and then reopening it would lose the window’s previous size, like the app knew better than you did what window size you wanted. It now respects the previous size you set, and has learned never to be so presumptuous in the future.
Fixed an issue where the window in MacOS wouldn’t reopen if it was closed and then reopened from the dock.
In the left panel, hiding a remote would turn the branch icons for that remote into a bunch of misfits, like in some kind of John Hughes movie. Everything now stays put and is predictable as an episode of Columbo.
In this most ghostly of bugs, the stage/unstage buttons had the tendency to become transparent when diff view was open. Spooky fun for some, annoying for many, fixed for all!

New in GitKraken 2.1.0 (Feb 15, 2017)

New in GitKraken 2.0.1 (Feb 15, 2017)

New in GitKraken 2.0.0 (Feb 15, 2017)

PERFORMANCE IMPROVEMENTS:
Make a commit and watch GitKraken go! Committing is completed far quicker than in previous versions.
New year, new you: Open those repos at least 2 x faster than you could in 1.9.
Don’t forget to thank your grandma for the $5 in your Christmas card, and for drastically improving the scroll refresh in the graph. Did you see that? No more blank spots during scroll!
In fact, the graph scroll is also much, much faster. Do you scroll both ways? Great! Scrolling is noticeably faster on both axes.
Scrolling through a file’s changes is significantly faster, too.
Traversing the graph using keyboard shortcuts and the arrow keys was nice enough, but came with significant lag. Now it’s snappy and responsive.
NEW:
.gitignore: A big feature request from our users is finally here! You can now select a file or folder in the file staging area, and add to the .gitignore file on the fly. Right-click and select Ignore. From there, you can:
Add that specific file to .gitignore
Add all files with that file extension to .gitignore
Add all files in the same folder as the selected file to .gitignore
(If selecting a folder) add that folder to the .gitignore
Psst. GitKraken’s a bit CLI-curious! There’s a new option to open the current repo folder in terminal. Just go to File Open Terminal or use the keyboard shortcuts opt + T (Mac) / alt + T (Windows + Linux).
Your drunk uncle might have all the great Christmas dinner stories, but can he push a commit and create a pull request at the same time? Only if he’s using GitKraken. If you haven’t yet pushed a branch to a remote, you can choose to push and start a pull request in one command. Saves clicks and time! Hic!
Open GitKraken! Go on, try it! Look at Keif swim with delight! Watch that smile and know that, today, you made one kraken very happy.
We polished up the visual feedback during loading operations in-app, too. Remember that embarrassing wobble in the previous version’s loady-spin? But a distant memory.
IMPROVED:
When you're setting an upstream, you can select from available remotes instead of having to type out the fork and remote like it’s 2016. The really neat part is that GitKraken will get the gist of your most popular upstreams, and then prioritize those in the drop-down. Of course, if you want to type, you can still type.
PRO: Profiles can once again be assigned discrete GitHub / Bitbucket accounts.
UI IMPROVED:
New light and dark themes use a reduced color palette that is more consistent between themes. Notice that moodier, bluer tint to the dark theme? That was us.
A lot of love was given to the light theme to clean up the UI and improve contrast with a new color palette.
Input focus and mouseover styles have been added/modified to improve contrast and consistency.
Merge resolution tool UI has been cleaned up significantly, fixing alignment issues, etc.
Font style variations were reduced to improve legibility and generally look less wacky.
The font used to display code has been updated for legibility and is now consistent in all views.

New in GitKraken 1.9.0 (Nov 3, 2016)

NEW:
GitHub Enterprise support! If you’re using GitHub’s self-hosted platform, GitKraken will play nicely with it. It won’t snatch, won’t throw tantrums, and it will share. In fact, it will offer you all the features that make working with regular GitHub.com services in GitKraken so seamless, without having to leave the app: ◦Create pull requests
Create repositories including .gitignore and license files
Generate and verify SSH keys
Save authentication into profiles
Clone from GitHub Enterprise repo list
Add remote repos
Those of you on 64-bit Windows can now download a 64-bit version of GitKraken! Wrap your tentacles around it here. The app also displays which version (32- or 64-bit) you are running, for reference.
Tag folders: Just as with branch folders, you can now keep your tags in an organized and visually tidy order with tag folders. Ah, that’s better!
Remember the left panel search? Well, now, when you type, the search term you’re typing will be highlighted in the filtered items. This is for your eyeballs. We hope they find it useful.
FIXED/IMPROVED:◾Error log, supplemental: The crew has been alerted to a strange phenomenon resulting in cryptic messages about scopes being included in other scopes. We sent an away team to investigate these scopes, their customs and their weaponry, and it would appear that the crew is now returning to normal, thanks to GitKraken Engineering.
The Git Flow panel static path prefix is now correctly, vertically aligned with the rest of the text. Yes, these minor imperfections add a certain charm and gritty character to the app, but it’s better this way.
Left panel style tweaks to make you smile more or grimace less.
Attempting to add an external SSH key to a service would initiate a super secret and unintentional broken SSH mode that nobody wanted.
This release wouldn’t be the same without one of those good ol ‘generic javascript error’ messages you’ve grown to love. Eliminated in this release: Cannot read property ‘deletePassword’ of undefined. Absolute classic. You’ll miss that one, now that it’s gone.

New in GitKraken 1.8.0 (Oct 21, 2016)

NEW:
GitKraken’s left panel has been even more improved with some big new features:
Branch folders: Branch structures are now represented in beautiful, intuitive folder systems. Rejoice! At a glance, you can now see your folders and subfolders as actual folders and–yes–subfolders. The logical, clear, hierarchical structure will bring a nice, orderly tear to your eye.
Button tooltips: Left panel buttons (such as the > for Git Flow or the + for add remote) now have cute little tooltips to confirm their function. Adorable!
Left panel filter: If you have a lot going on in your repo, finding relevant items can be complicated, resulting in copious scrolling, looking around, and frowning. GitKraken is designed to make you click and scroll less, not more, so we’ve worked hard on a new filter feature for the left panel. You can filter the entire panel, including:
Branches
Remotes
Pull requests
Tags
Stashes
Submodules
Use keyboard shortcut ⌘ | Ctrl + Shift + F, and start typing. At the risk of stating the obvious, hitting Esc will clear the filter.
FIXED:
When making a pull request from within GitKraken, selecting a branch would make the text color go dark. Like, same color as the background dark. Weird. Fixed.
Some .git/config URL entries would cause some repos to fail to open. We’ve fixed that issue, because if you had to choose one thing you’d want GitKraken to do, it would probably be “open a repo.”
When cloning a new repo and using GitKraken to create an initial commit, that repo’s remote would not show up in the UI, but it does now.
Under some circumstances (involving team names and repo names in Bitbucket), GitKraken would fail to create Bitbucket pull requests. Where it once failed, GitKraken now succeeds!
Let’s say you were able to make a Bitbucket pull request. Well, you were still not out of the woods, because some Bitbucket PRs would not show in the left panel even if they were successfully created. The left panel now shows them all.
Relative commit dates in the graph were off by 1. If “off by 1” sounds like an unwelcome state of affairs, that’s because it is. And, as such, it has been fixed.
For some users, the file history would serve up this bland message: searched until invalid date (). Whatever that means, it’s not a message you’ll see anymore, thank goodness.

New in GitKraken 1.7.1 (Oct 7, 2016)

New in GitKraken 1.7.0 (Oct 7, 2016)

New:
Notice anything different about GitKraken? Heh, NBD, just that we went ahead and rebuilt the entire Left Panel from scratch! That’s right, as part of our ongoing refactoring we have migrated our architecture for the left panel (over to Redux, if you’re interested).
Rebuilding this panel has allowed us to give you a special gift: The gift of time. That left panel is snappier than in previous versions.
One of the major reasons for the speed boosts in the left panel is the refactoring of the scrolling module it uses. To do this, some of the GitKraken team built a custom module: meet Rickscroll! Rickscroll intelligently renders only what is visible at any time (say, in that left panel) and never more, making rendering much more efficient.
The Rickscroll module is open source and is an actively developed and maintained scroller for React, for all your overflow needs. Check out the package at http://github.com/implausible/rickscroll.
Here’s a breakdown of what’s different:
Section headers will now stick to the top of the left panel when scrolling.
The currently checked-out branch is now highlighted in green and has a checkmark icon, so it’s kind of hard to miss.
Labels no longer animate to reveal hide/show or solo icons—that keeps things simpler in that small space and makes it less likely you’ll inadvertently click the wrong thing.
WAIT, WHERE DID THE SOLO ICON GO? We removed the solo button from the label itself, but don’t panic, Yngwie Malmsteen, you can still solo. The “soloing” state is now initiated via the context menu. Once initiated, additional branches can be soloed by clicking the solo icon next to them.
The icon to hide branches and tags from the graph (that green eye) will still appear on hover, by the way.
Each type of item (branch, pull request, tag, stash) now has its own icon, so they’re easier to visually differentiate in large lists. Small lists too, but especially for large lists.
Buttons that open the sliding panels (for things like adding a remote or creating a PR) are now all aligned to the right of the row.
Drag and drop styling has been modified to be more clear and intuitive, with an icon appearing next to the currently-hovered drop target.
We went ahead and increased the overall level of sexiness in the left panel. The sexiness levels were pretty high originally, but we opted to make efforts to increase these levels to achieve optimal sexiness.
Fixed:
When creating a new Pull request, branch dropdown lists were not always populating. They now populate consistently.
Take a quick look at the following line of text: **/example*/**. This may seem harmless enough, but having a line like this in your .gitignore file would cause GitKraken to re-open that repo, forever, thanks to a bizarre ‘more than one double asterisk in a single line of your .gitignore file’ bug. Shout out to Rob King for reporting that bug and freeing us of this purgatory! We fixed it!
Improved:
We’ve changed the default Preferences-Authentication-Use local SSH agent checkbox state to be UNchecked on macOS and Windows. Before, that was checked by default, and caused confusion for some of you who were not actually using a local agent.

New in GitKraken 1.6.1 (Sep 20, 2016)

New in GitKraken 1.6.0 (Sep 13, 2016)

New in GitKraken 1.5.4 (Aug 30, 2016)

FIXED:
Sometimes, a truncated branch label would be obscured by another branch label to its right. This was probably something to do with z-indexes or something. Either way, your branch labels will no longer live in the shadows when in a hover state.
Imagine you’re taking a tour of a historic castle or monument, and the moment you acknowledge your tour guide, he or she bolts to the door and runs off into the distance, never to be seen again. Weird, right Well that’s basically what was happening with our new user tour. If you clicked on a tour bubble, the tour would end, just like that. This no longer happens.
Now imagine that you’re on that same tour, and the replacement tour guide recommends you take the lead and go through a door, but once you have gone through the door you find yourself outside, unable to get back in and resume your tour. Again, that’s basically what was happening in our tour. On the second step where the user is asked to click the preferences menu item, if the user clicks the tour bubble, the tour would break. Not any more!
In some cases, opening a repo with a graph less svelte than the current repo would fudge the rendering of the lines. We’ve fixed that.
Attempting to supply an SSH URL in an incorrect format would throw you a cryptic error that was heart-sinkingly useless to people who are not machines. We now have a more human-friendly message to help you correct the formatting and be on your way.
Sometimes, hidden branches would decide that being hidden was the best thing in the world, and never unhide. All hide/unhide behavior now functions as expected.
When cloning from the Bitbucket tab, the list of available repos will more closely match the repos on your Bitbucket.org home screen.
The account screen now opens in-app.
The esc key once again closes full-page views because it was annoying that it didn’t.
If GitKraken was asked to check out a hidden branch, it would have an existential crisis and throw an error, and this no longer happens.
IMPROVEMENT:
Commit autoselection has been improved!
“Command Palette” keyboard shortcut has been included in the keyboard shortcut modal.
Windows and Linux users: you finally have a preferences keyboard shortcut! Hit Ctrl + , to open preferences.
Fetching a single remote now updates pull requests.
Cherry pick prompt now gives you the option to cancel.
Expanding/collapsing the ref panel is snappier. So smooth!
GitKraken’s ability to open the most massivest of repos has been improved. To prove it, we managed to open the Linux repo without breaking GitKraken, our computer, Linux, GitHub or the Internet.
Toolbar labels can now be switched on or off as preferred by the user.

New in GitKraken 1.5.3 (Aug 17, 2016)

New in GitKraken 1.5.2 (Aug 5, 2016)

New in GitKraken 1.5.1 (Jul 30, 2016)

New in GitKraken 1.5.0 (Jul 29, 2016)

This latest release brings a brand new paid version of the app, as well as some substantial improvements to the free version. Both versions will continue to be developed side-by-side, and as always, release notes will appear here with each update.
For more info on GitKraken Pro, please check out the Pro page. To learn more about the story behind monetizing the app, check out our blog post.
NEW:
Tree view mode is now available for the staging panel, because sometimes you just need to see those file parents and their kiddies. You can also:
Toggle between the full file path view and the tree view
Sort folders and files alphabetically in ascending or descending order
Stage/unstage all files in a folder! This feature hopefully makes your staging management more convenient and much faster if you need to stage/unstage lots of files at once.
In-app merge tool updates:
Remember when GitKraken’s merge tool didn’t have syntax highlighting? That’s so version 1.4! As of this version, you.canEnjoy('a more sensical comparison of your code') with the new syntax.highLighting();
User interface refinements:
Removed a lot of unnecessary buttons that were just kind of hanging around and giving the neighborhood a bad name
Left and right panels now hide to allow more room to view your code in the merge tool.
Introducing GitKraken Pro:
GitKraken Pro is our new paid version, and it includes a couple of awesome new features (see below) as well as email-based support.
We’ve updated the GitKraken app to allow you to manage your GitKraken account and Pro subscription at any time, or you can visit account.gitkraken.com.
Profiles! Pro Feature:
Add and quickly switch between multiple profiles: This is ideal if you often need to switch between different projects (such as work & personal projects). Profiles store settings like:
The name and email address you use when signing commits, as well as optionally update your global .gitconfig when switching projects
Authentication info (GitHub/Bitbucket credentials)
Repos
Color themes
Profile avatars
In-app merge tool editor Pro Feature:
When handling a merge conflict, Pro users can edit the final output in-app before resolving.
FIXED:
The last repo in a list of less than 5 repos would style incorrectly. That’s an oddly specific visual bug that we’ve now fixed.
Staging and then unstaging the currently viewed file would start loading just fine. But here’s the kicker: it would never finish loading. Now it does.
After searching for and finding a commit, the diff for the commit would load forever. That’s too long, so we’ve reduced it to “a finite and reasonable amount of time.”
On the Set Upstream dialog, an incorrect default value would be populated in some cases.
The Linux update would sometimes display an available update as version [object Object]. Not technically a lie, but not the most informative output. We’ve fixed it to always show the version number.
.gitignore should be properly handled now and no longer ignore your ignore settings. It was meta like Being John Malkovich, only just annoying and inconvenient. Now it’s more like any Nicolas Cage movie: It’s exactly what you’d expect. It’s a Nicolas Cage movie. It’s fine. It does what it’s supposed to do. No surprises.
IMPROVED:
We’ve updated our end user license agreement for this release and added a privacy policy, just so you know.
Mac users: sorry if you enjoyed waiting for GitKraken to start up. It’s just that we went and made the app load time 200% faster! NBD.

New in GitKraken 1.4.1 (Jun 8, 2016)

New in GitKraken 1.4.0 (Jun 2, 2016)

NEW:
Squash commits: You can now select a bunch of adjacent commits (in the same branch only), right-click and select “squash” to consolidate them into one single commit.
Option to merge without fast-forwarding: Previously, GitKraken would fast-forward your merges where possible. But, since some people find the tree view that results from regular merging more useful than the view that results from fast-forwarding (even when fast-forwarding is available), GitKraken will now let you choose a regular merge instead of fast-forwarding. You may merge, humans.
Discard hunks/lines: Want less hunks on-stage? When previewing unstaged files, you now have the option to discard hunks from that commit. You can also get really detailed by selecting lines, right-clicking and discarding those lines specifically. Hunky.
New command palette: It’s a new, err, palette, dedicated to, umm, commands. It works like the fuzzy finder, but whereas the fuzzy finder is used to open/change anything relating to views and panels, the control palette is used to trigger actions that affect your repo:
Open the command palette with shortcut ⌘ | Ctrl + Shift + P
Type your command: Undo/Redo, Fetch All, Create Branch, Create/Apply/Pop Stash, Stage/Unstage/Discard All Files
Please note: We have moved the Checkout Branch command from the fuzzy finder to the command palette because it’s less findy and more commandy, and so it belongs there.
In-app license and .gitignore generation: When initializing a repo via GitHub or Bitbucket, you can now specify a license and a .gitignore template. These will be pushed to your repo upon initialization.
FIXED:
Multi-selected commits are now ordered by author date in the commit panel.
The option to “Add as a remote” enjoyed playing peekaboo in pull request context menus. In fact, it would play it so well that it wouldn’t even appear as an option. We’ve fixed that, sorry.
Submodules were not showing parent branches if that submodule was not in the root folder of the parent repository. That shouldn’t happen, and it no longer does.
The in-app merge no longer fails to load if neither version had any matching lines.
Some memory leak issues were persisting and we’ve been working hard to fix them. We know things like this can be a pain, and hope that these leaks spring no more.
IMPROVED:
Authentication pages for GitHub and Bitbucket have been overhauled and should be much improved.
Here are some of the notable improvements:
Connection status to hosting services is clearly visible and easy to change.
You can set whether GitKraken uses your local agent or a specific SSH key.
SSH keys can be labeled when generated in GitKraken.
SSH keys set or generated for each service are now clearly displayed so they can be easily connected/disconnected from those services.
We reduced the sizes of our download files by 30-50%, saving you disk space and Making the World a Better Place.

New in GitKraken 1.3.0 (May 20, 2016)

NEW:
You can now select multiple commits to view the differences between those commits. It mostly works like you’d expect from a file manager:
Click: Selects a single commit (you’ve probably done this before).
⌘ | Ctrl + click: Adds the clicked commit to currently-selected commits.
Shift + click: Adds all ancestor commits from the previous selection up to your current selection.
You can now change the zoom level in three ways:
Keyboard shortcuts (the quick way):
⌘ | Ctrl + +: Zoom in
⌘ | Ctrl + -: Zoom out
⌘ | Ctrl + 0: Reset zoom
Fuzzy finder (the typey way)
Status bar (the clicky way): Click on the zoom level down there.
New keyboard shortcuts have been added! Hit ⌘ | Ctrl + / to view a list of all available keyboard shortcuts, including those for undo/redo, toggling the left panel, staging/unstaging all files, zooming, and arrow-key aliases.
(Yes, it’s a shortcut to view shortcuts. And it gets even more existential when you see that this keyboard shortcut is itself featured in the list of keyboard shortcuts that you opened using this keyboard shortcut. Whoa.)
Here are some other context-specific shortcuts:
If commit message or WIP input is focused:
⌘ | Ctrl + enter: Create commit
⌘ | Ctrl + shift + enter: Stage all files and create commit
If a staging panel file is open:
S: Stage file
U: Unstage file
We sent some of our keys to school to make them smarter. We’re so proud of them! Here’s what they learned:
Esc key now closes most things that are open like a good Esc key should.
Arrow keys: When a file is open, arrow keys will switch between files in the same commit instead of moving you to a different commit.
More options added to the fuzzy finder: Open, clone, or init a repo, open settings page, toggle left panel, change zoom level, and view keyboard shortcuts.
Right-clicking on a remote now gives you the option to open that remote in your web browser.
FIXED:
Loading huge files (about 5k+ lines) in the in-app merge panel is much faster.
Most prompts and form inputs will now auto-focus when opened.
Fixed error that occurred when trying to open a repo with merge conflicts that had soloed branches.
The Pull Requests list no longer fails to load if any pull request was from a repo the user does not have access to.
If there were no pull requests pending, the list would straight up lie and say it was “Loading...” forever. Now it tells the truth: there are 0 pull requests.
Bitbucket clone repo would sometimes not list every repo, but now, it does.
Fixed an issue where you couldn’t initialize a repo in Bitbucket if you did something zany, like use uppercase letters or spaces in the repo name.
Fixed not being to change the root drive in Init Repo.
Fixed all files becoming unstaged when right-clicking a staged file and choosing “Discard Changes.”
Opening the in-app merge tool now scrolls you to the first conflict automatically.
Sometimes the in-app merge tool would get stubborn and not let you scroll far enough to see the end of a long line. Now it will let you scroll right to the end.
Special note and shout out: A large number of bug fixes were made in addition to the above, thanks to the awesome bunch of people who worked on a significant update to NodeGit. Thank you!

New in GitKraken 1.2.0 (Apr 27, 2016)

New in GitKraken 1.1.0 (Apr 13, 2016)

New in GitKraken 1.0.0 (Apr 4, 2016)

New in GitKraken 0.9.2 Beta (Mar 19, 2016)

New in GitKraken 0.9.0 Beta (Mar 17, 2016)

New in GitKraken 0.8.3 Beta (Mar 15, 2016)

New in GitKraken 0.8.2 Beta (Mar 15, 2016)

New in GitKraken 0.8.1 Beta (Mar 5, 2016)

New in GitKraken 0.8.0 Beta (Mar 5, 2016)

New:
File History is now available through the context menu of a file in the diff panel. This will bring up an evolved Diff View showing the timeline of commits. Use keyboard shortcuts to navigate or click the short commit SHA to quickly jump and show diffs.
cmd+↑ on mac / ctrl+home on windows/linux to switch to the first commit entry
cmd+↓ on mac / ctrl+end on windows/linux to switch to the last commit entry
Blame revisions in the new File View tab also present in the history section to see how and when the file changed, and by whom. Select a commit entry by author to display changes at that point in time and toggle 'Show blame details' to see more or less annotation for the change.
Looking to get your contributions reviewed and merged in asap without leaving GK? There's no more wait as Pull Requests are now accessible in the left ref panel on repositories. Fetch from the open list and quickly create PRs for GitHub or Bitbucket!
Fixed:
Many crash issues eradicated. So many. The elusive fatal error in white screen of death when opening a repo has been addressed. 🙅 ◽ 💻 💀
If you happened to commit in the future like us or had a different method of birthing a child commit before its parent, it was possible for a commit appearing unusually orphaned in a merge on the graph. This is not a problem anymore as we've adjusted the sort for it to display correctly.
Updated references for the possibility of removing a remote during an active fetch, preventing a repo from being reopened
Autofetch interval will work for remotes when switching from one repo to another
We'll gracefully recover on the chance a commit search index becomes corrupt and loads forever. Seek and ye shall find 🔍
Improved:
Ridin' spinners! For Remotes on the left panel, there is now a spinning icon for indicating when there is an active fetch in progress. 🌀 They'll stop when the operation completes.
In Add Remote the Select list has evolved to allow pulling the list or typing to find a desired repository from both GitHub and Bitbucket
Add Remote is also case insensitive now, disallowing adding remotes at the same name
Updated ability cross-platform to locate merge tools in Preferences
Accurate messaging for when Bitbucket authentication fails or has expired