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.12.0 (Feb 14, 2024)

  • New:
  • The new Focus View has improved to display all of your PRs, Issues, and WIPs.
  • You can access the new Focus View from the new Focus View tab. Note, the Focus View will no longer show within a Cloud Workspace.
  • You can still filter items by Workspace using the Workspace filter dropdown.
  • You can now host Cloud Patches on your own dedicated storage for the highest level of security (Requires an Enterprise plan).
  • Your organization’s admin can configure a self-managed environment for your Cloud Patches at https://gitkraken.dev/settings/security.
  • When creating a Cloud Patch, GitKraken Client will display a message to confirm it will be securely stored on your organization’s storage.
  • Improvements:
  • Experimental Feature – Git Executable:
  • Added clone support.
  • Improved stability and performance when authenticating with Git remotes.
  • Updated to Monaco 0.45.0:
  • This brings improvements to the file/diff/merge editors.
  • Bug Fixes:
  • Experimental Feature – Git Executable.
  • Fixed an issue where relative paths for core.hooksPath failed to execute hooks.
  • Fixed an issue where SSH and Git version information was parsed incorrectly.
  • Fixed an issue on Windows where updating the file known_hosts was not working for rare cases.
  • Fixed an issue where checking out a branch for a pull request in the Focus View would not fetch the remote before checking the branch out.
  • Fixed an issue on macOS where opening a file in Finder from GitKraken Client could cause Finder to freeze.
  • Fixed an issue where the diff view could disappear after quickly selecting a commit in the Commit Graph using the right arrow key or the mouse.
  • Fixed an issue where repos may not load for GitLab Self-Managed instances with self-signed certificates.

New in GitKraken 9.11.1 (Jan 11, 2024)

  • New:
  • You can now edit link permissions for Cloud Patches after creation.
  • Improvements:
  • Added the ability to customize more date/time formats in Preferences > UI Customization > Date/Time.
  • Upgraded to Electron 27.
  • Experimental Feature – Git Executable:
  • Friendlier GPG errors
  • Experimental Feature – AI Commit Message Generation:
  • You can now select an OpenAI model to use with gpt-4 support added.
  • You can test whether an OpenAI API key is valid with a button in Preferences > Experimental.
  • Bug Fixes:
  • Fixed an issue where the compact Graph column in the Commit Graph may not display correctly when moving the horizontal scroll bar using the trackpad.
  • Fixed an issue where selecting multiple branches in the left panel was not working on Windows or Linux.
  • Fixed an issue where the Date/Time column of the Commit Graph was not taking into account the time portion set in Preferences > UI Customization > Date/Time Format.
  • Fixed several issues where resolving a gitkraken:// link wouldn’t cancel properly when the user interrupted locating the relevant repository.
  • Fixed an issue where navigating between files in the commit panel with the keyboard didn’t work as expected.
  • Cloud Patches will no longer fail to create on repositories without a remote.
  • Experimental Feature – Git Executable:
  • Fixed an issue where invalid credentials with HTTPS remotes showed an info toast instead of prompting for valid credentials.
  • Fixed a problem on MacOS and Linux where SSH commit signing could only be used with ssh-keygen.

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 9, 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 16, 2023)

  • Improvements:
  • Upgraded to Electron 22.3.25.
  • Bug Fixes:
  • Experimental Feature – Git Executable:
  • Fixed "Cannot read properties of null (reading ‘startsWith’)" due to error reading gpg key from settings.

New in GitKraken 9.9.1 (Oct 9, 2023)

  • Bug Fixes:
  • Fixed an issue where the improved commit graph could not display Bitbucket Server repositories

New in GitKraken 9.9.0 (Oct 6, 2023)

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

New in GitKraken 9.8.2 (Sep 18, 2023)

  • Bug Fixes:
  • Upgraded to Electron 22.3.24.

New in GitKraken 9.8.1 (Sep 6, 2023)

  • Bug Fixes:
  • Fixed a bug where double-clicking a branch in the Left Panel was not checking out the branch.
  • Fixed a bug where graph columns could not be resized.
  • Fixed a bug where filtering by author was not working in the graph.

New in GitKraken 9.8.0 (Sep 6, 2023)

  • New:
  • The Focus View has been improved!
  • Pull Requests, Issues and Works in Progress have been combined into a single view.
  • We also added buckets for PRs, ISSUES, and WIPS only.
  • Filter PRs by Mine, Created by Me, Assigned to Me, or Needs my review.
  • Filter ISSUES by Mine, Created by Me, Assigned to Me, or Mentioned.
  • Note: If you’re new to Focus View, you may access the Focus View tab from any Cloud Workspace.
  • Improvements:
  • Enhanced ‘Invite Users’ Modal: Added X button for email removal and improved email display as individual components.
  • Bug Fixes:
  • Experimental Feature – Git Executable.
  • Improved handling of ssh_config options, specifically StrictHostKeyChecking and UserKnownHostsFile and their interaction with remote actions.
  • Fixed Workspace repo list having duplicate entries when an Azure repo is deleted.
  • Fixed a bug where Jira Server issues could not be opened in the browser due to a malformed URL.
  • Fixed cursor jumping to end of input when updating the Date/Time Short Format preference.
  • Fixed the Workspaces tab re-loading data when closing other tabs.

New in GitKraken 9.7.1 (Aug 16, 2023)

  • Bug Fixes:
  • Improved performance when selecting the working directory.

New in GitKraken 9.7.0 (Aug 10, 2023)

  • New:
  • Your working directory can now be compared against any commit or branch! This can be accomplished in two ways:
  • Right-click a commit or branch, and choose Compare commit against working directory
  • Use Ctrl click (or Cmd click on MacOS) to select your Work-in-Progress ("WIP") node, along with the commit of your choice.
  • GitKraken Client will now attempt to pull Date/Time settings from OS preferences, along with an override in Preferences > UI Customization.
  • Windows: Region & Short date format preferences
  • macOS: Region & Date format preferences
  • All: LC_ALL & LC_TIME environment variables
  • Improvements:
  • Added an indicator for repositories in the Workspace REPOSITORIES list when multiple paths are detected. Clicking this will allow the user to specify which repository to use.
  • Experimental Feature – Git Executable:
  • Added tag support.
  • Added GPG Preferences setting for SSH commit signing.
  • Bug Fixes:
  • Fixed an issue where Pull Requests were not loading for Bitbucket Workspaces.
  • Improved home directory detection on Windows.
  • App will now create ~/.ssh directory if it doesn’t exist when updating ~/.ssh/known_hosts.

New in GitKraken 9.6.1 (Aug 2, 2023)

  • New:
  • Added a share button in the Workspaces tab for inviting organization members and/or teams to join a Workspace.
  • Improvements:
  • Upgraded to Electron 22.
  • Experimental Feature – Git Executable:
  • Added push support.
  • Force push will now default to --force-with-lease, and prompt to fetch or push --force (without lease) when the remote ref and remote-tracking branch are different.
  • Added support for streaming Git Hooks output.
  • Renamed the GitKraken Terminal command gk to gkc.
  • Bug Fixes:
  • Fixed an issue loading Workspace pull requests when repos have too many pull requests.
  • Fixed an issue where GitKraken Client couldn’t start if the last opened repository was no longer openable.
  • Fixed instances where the Git info in the Workspace repository list would not display.
  • Fixed error toast that appears when a rebase fails due to conflicts.
  • Fixed an issue where GitKraken Client wouldn’t show that a merge was active after resolving a conflict.
  • Fixed an issue where Workspace pull requests would not display if a team, bot, or mannequin was a requested reviewer.
  • Fixed an issue where the GPG program could be set to an invalid value, causing issues with GPG actions.
  • Fixed cases of improper UI for the Workspace pull request list when using the search bar.
  • Fixed cases where a blank screen could appear while viewing a repo’s README from a Workspace.
  • Fixed tilde resolution of core.hooksPath in some cases.

New in GitKraken 9.6.0 (Jul 12, 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 18, 2023)

  • Bug Fixes:
  • Fixed an issue where a merge is aborted when there are conflicts and the merging branch is checked out.
  • Fixed an issue that would occur when squashing certain commits.

New in GitKraken 9.5.0 (Jun 7, 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 9, 2023)

  • New:
  • Experimental section now available from Preferences, and users may now opt-in for:
  • Experiment 1: AI Generated Commit Messages
  • Generate commit messages from any staged changes by connecting with an OpenAI API key.
  • Experiment 2: Bundled Git Executable
  • GitKraken Client will use Git instead of the Nodegit library for actions like fetch and commits, plus deliver some performance improvements.
  • Refreshed the new-user onboarding, for a smoother experience into the app.
  • Improvements:
  • When adding repos to a Workspace connected to Azure DevOps, you may now select specific Azure DevOps repos instead of syncing an entire project.
  • Improved position of “traffic light” window controls on MacOS.
  • Improved the left panel resize handle UI.
  • Bug Fixes:
  • Deleting the default branch name setting no longer sets the default branch name to empty string in .gitconfig.
  • Changing this setting also no longer edits the .gitconfig file at all if the sync .gitconfig with profile setting is not checked.
  • Basic text-editing context menu has been added to Left Panel filter input.
  • Added error toast if the app detects different capitalization in remote URLs.
  • Fixed issue retaining selected Jira project or Trello board when changing Workspaces.
  • Fix duplicate repos in the Local Workspace repo list when the repo was deleted from the users machine.
  • Fix error ‘Checkout Failed: stdout maxbuffer length exceeded’ when checking out in some big LFS repos.
  • Improved the app’s handling of commits with an empty message.
  • Fixed a case where opening a file in an external editor would not complete the action.

New in GitKraken 9.3.0 (Apr 9, 2023)

  • New:
  • Azure DevOps Integration Boosts:
  • View and edit Azure Work Items in Workspaces from Focus View or Team View.
  • Create a branch from an Azure Work Item.
  • One-click integration connection from Preferences > Integrations > Azure DevOps (but you can still use personal access tokens too).
  • Sign into the app with Azure.
  • Bug Fixes:
  • Fixed an issue where the Workspace issue branch column would not update if a branch for the issue was deleted.
  • Fixed an issue where the Work In Progress table was not working for Azure DevOps Cloud Workspaces.

New in GitKraken 9.2.1 (Mar 14, 2023)

  • Bug Fixes:
  • Fixed a crash on MacOS that could occur based on the user’s installed fonts.
  • Resolved .build-id Electron conflict in the RPM package.

New in GitKraken 9.2.0 (Mar 8, 2023)

  • New:
  • GitKraken Insights:
  • Sparkline graphs will now show the shape and trends of GitKraken Insights for each metric.
  • Focus View Updates:
  • View, checkout, and start a branch from an issue in the My Issues section of the Focus View.
  • You may now hide entire sections for Focus View in Workspaces. Customize away!
  • Issue View for Workspaces:
  • Added ability to open the issue panel for Workspace issues.
  • Improvements:
  • Updated Azure Devops integration page with “Work Items” scope.
  • Added a new UI setting for hiding the workspace tab when the tab is closed.
  • Upgraded to Electron 21.
  • Improved stability for font loading.
  • Updated font selection settings to present monospace fonts accurately.
  • Bug Fixes:
  • Disconnecting GitLab Insights integration will no longer affect the connection status for other Insights integrations.
  • Fixed several bugs with keyboard shortcuts in the Interactive Rebase view.
  • GitKraken Insights will now successfully connect for Cloud Workspaces connected to Azure DevOps.

New in GitKraken 9.1.1 (Feb 15, 2023)

  • Bug Fixes:
  • Updated OpenSSL to 1.1.1t, which includes important security updates.
  • Fixed file contents not loading when opening diffs/merges in external tools.

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

  • Improvements:
  • The Open repo command in the Command Palette will now show repos from deep linking and Local Workspaces.
  • Bug Fixes:
  • Fixed a bug on MacOS where having the UI theme set to Sync with system caused high CPU usage.
  • Fixed performance hit when undoing Discard all changes with LFS files.
  • Fixed lag when resizing the commit message.
  • Fixed issue saving token when a user manually enters the token to login with GitHub.
  • Workspaces:
  • Issues will now load in Workspace when using GitHub Issues or GitLab Issues.
  • GitKraken Insights metrics section will still show even if there are no open PRs.
  • Fixed blank Workspace tab that would show after upgrading to 9.0.
  • Submodules:
  • Fixed error when discarding all changes after adding a submodule.
  • Fixed submodule not initializing after renaming a submodule.
  • Fixed submodule not initializing when discarding all changes with submodule changes.

New in GitKraken 9.0.0 (Dec 13, 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.
  • Once your Local Workspace is created, you’ll see all your repos grouped together and get the following benefits.
  • View currently checked out branch for each repo.
  • Click on any repo name to open it as a tab in GitKraken Client.
  • Multi-select repos to:
  • Perform a fetch for the selected repos
  • Open repos as tabs in GitKraken Client
  • Use your selection to create a Cloud Workspace (formerly called Personal or Team Workspace)
  • That’s right! You can also use your Local Workspace to create a Cloud Workspace, which will enable more visibility into your pull requests, issues, and share your Workspace with teams.
  • Cloud Workspaces:
  • Formerly known as Personal and Shared Workspaces, Cloud Workspaces are useful for sharing your Workspace with teams along with enabling GitKraken Insights.
  • Focus View & Team View:
  • The Focus View, which was previously called the Overview, is now out of Preview and provides a list of all Pull Requests, Issues, Works in Progress that matter to you.
  • With this release, you may now toggle columns on or off from this gear in the top left corner.
  • The Team Overview is also out of Preview and is now called Team View. It will show you all pull requests and issues associated with the repos in your Workspace.
  • And similar to the Focus View, you may now toggle columns on or off from this gear in the top left corner.
  • GitKraken Insights:
  • Next, we’re excited to introduce GitKraken Insights – which measures how fast pull requests are merged into your repositories.
  • But why does it matter if you track metrics like pull request Cycle Time and Throughput?
  • “I think an underlying principle that exists is that the longer your code stays away from being merged, the more complicated your workflow is going to become.And so as those changes land and your PR and your change becomes more behind from the main trunk branch, the more likely it becomes you will have to do more work to get that code working again.” Jeff Schinella, Director of Product
  • To enable GitKraken Insights, you’ll first need to open a Cloud Workspace and then navigate to the Pull Request section. From here, click to connect to your remote hosting service.
  • Once the connection is complete, return to the Pull Request section in your Cloud Workspace to view the following metrics for your Workspace pull requests:
  • Average Cycle Time: Measures the average time it takes for a pull request to be merged for the selected timeframe.
  • Average Throughput: Measures the average number of pull requests merged for the selected timeframe.
  • Merge Rate: The percentage of merged pull requests compared to open pull requests for the selected timeframe.
  • Open: The total number of pull requests opened for the selected timeframe.
  • Merged: The total number of pull requests merged for the selected timeframe.
  • GitKraken Insights is currently in Preview, and we’d love to hear your feedback.
  • UI/UX Refresh:
  • Next, we recently released the Commit Graph for GitLens where we learned how to improve the graph even more. We’re delighted to bring those learnings to GitKraken Client 9.0.
  • Ghost Branches:
  • In GitKraken Client, you will now see a “Ghost” branch when you hover over a commit. This will show the closest branch that contains that commit. The “Ghost” branch will also show when a commit is selected, and double-clicking that ghost branch will checkout the head of the referenced branch.
  • Users may toggle this setting on or off from Preferences > UI Customization.
  • Commit highlighting:
  • When you hover over a branch, the app will highlight all commits referenced by that branch.
  • Users may toggle this setting on or off from Preferences > UI Customization.

New in GitKraken 8.10.3 (Nov 8, 2022)

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

New in GitKraken 8.10.2 (Nov 2, 2022)

  • New:
  • Workspace Overview section will now show Pull Requests for Bitbucket repos for the current user.
  • Improvements:
  • When a GitLab token expires, GitKraken Client will now show a prompt to re-login. This should address previous issues working with GitLab repos.
  • Workspaces can now be viewed across machines and profiles. Be sure to sign into the same GitKraken account to access Workspaces on a different machine.
  • Improved Commit Graph responsiveness when bringing the app into focus.
  • Bug Fixes:
  • Jira issues will no longer break if there is no vote field on an issue.
  • Removing your remote from the Left Panel no longer causes rows to overlap.
  • Links in blame commit messages will now open in an external browser.

New in GitKraken 8.10.1 (Oct 19, 2022)

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

New in GitKraken 8.10.0 (Oct 19, 2022)

  • Improvements:
  • GitKraken Client has been updated to Electron 17.
  • New Tab layout has been rearranged to make it easier to access Repositories, Workspaces, and the Terminal Tab.
  • You can now double click a section header in the left panel to maximize that section. This option is also available in a context menu.
  • Bug Fixes:
  • Fixed an issue where the breadcrumb in Azure repo tabs would direct users to add the repo to a Workspace when this is not supported.
  • Fixed an issue where the SSH key options were not being displayed for Azure and self hosted integrations.
  • Fixed an issue where the Workspace Overview page would say there are no PR’s/issues during initial loading.

New in GitKraken 8.9.1 (Sep 15, 2022)

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

New in GitKraken 8.9.0 (Sep 15, 2022)

  • New:
  • “Alpha, Rita’s escaped! Recruit a team of developers with attitude.”
  • Team Overview – Added the Team Overview section for Workspaces:
  • Team Pull Requests – Shows all Pull Requests for repos in Team Workspace and provided quick actions.
  • Team Issues – Displays list of all Issues for repos in Team Workspace.
  • This view is in Preview with many more improvements coming. A link to submit feedback can be found at the top of the view
  • Improvements:
  • Thanks to Alpha, the command center got some mighty upgrades.
  • Workspace UI improvements
  • GitHub users may open the in-app Pull Request Panel from Workspace sections.
  • Added the ability to switch issue tracker in the Workspace Overview page.
  • Added a gray draft PR indicator in the Workspace Overview page.
  • Repository and Pull Request sections in Workspaces have been updated to reflect the new styles in Overview.
  • Added colors to the last updated date displayed in the pull request and issue tables in Workspaces.
  • At Risk PRs are now highlighted with a ⚠️ icon in the PR Status column.
  • Team Overview for Workspaces associated with GitHub repos can be filtered by Author or Assignee.
  • Left panel improvements – Left panel filtering experience improved:
  • Issues and Pull Requests, which have separate, integration-specific filtering unaffected by the global filter, will automatically collapse while performing a global filter.
  • Sections can be collapsed and expanded while filtering.
  • We continue to listen to feedback and plan even more left panel improvements.
  • Added the keyboard shortcut Ctrl + Shift + E which opens checked repositories from the Workspace Repository section in your preferred external editor.
  • Jira Server connections now support authentication with personal access tokens (PAT).
  • In-app support forms have been removed in favor of linking to the support form on our website.
  • Bug Fixes:
  • Rita made her monsters grow, but our megazord saved Angel Grove from their clutches.
  • Fixed an issue where GitLab Self-Managed remotes would not display a user’s avatar as the icon.
  • Fixed an issue where inputting an invalid token when signing in closes the token input box.
  • Fixed issues with checking out pull request branches from the Workspace Overview section.
  • Fixed an issue where searching in the Workspace Overview with upper case would not show any results.
  • Fixed an issue where having a pre-push hook fail when deleting a tag would cause a looping Oauth prompt to show up.
  • Fixed an issue where users could not delete tags from remotes.
  • Fixed an issue where editing profiles from Preferences -> Profiles could make it appear that the user had switched profiles.
  • Fixed an issue where the log-in screen had poor contrast on light themes.
  • Fixed an issue where commits would not immediately be inserted into the graph after using Show All Tags to unhide one or more tags.
  • Team Overview:
  • Your teams have a new hub with the Team Overview in Workspaces.
  • This new broad view shows all Pull Requests and all Issues for the repos in your Workspace – giving you a high level view of your team’s coding efforts.
  • Team Pull Requests:
  • If your Workspace repos are hosted on GitHub, you may filter the Team Pull Requests by assignee or author.
  • The Team Pull Requests sections has the following columns:
  • Last Updated
  • PR title with link to open the Pull Request in the hosting provider
  • PR Author
  • Repo name with link to open the repo in GitKraken Client
  • Review status
  • PR status – Shows status for “Draft” or “At Risk” Pull Requests
  • Checks – Shows CI/CD results
  • Lines added/removed
  • PR branch – Double click to check out directly in GitKraken Client
  • Shortcut to open the Pull Request Panel – GitHub Repos only
  • Team Issues:
  • Team Issues will show all GitHub Issues, GitLab Issues, Jira Cloud Issues, Jira Server, or Trello cards associated with the repo.
  • With Team Issues, it’s easy to switch between Jira or Trello and back to either GitHub Issues or GitLab Issues. If you select Jira or Trello, you can also filter by project so that you only see issues that matter to you.
  • The Team Overview is in Preview, and feedback is welcome. A link to submit feedback can be found at the top of the view.
  • Workspace UI updates:
  • GitKraken Client v8.9 also updates the UI for the Repositories and Pull Request sections in Workspaces – providing clearer information at a glance through updated color coding and iconography.
  • Overview > My Issues > Set Issue Tracker:
  • You may now switch the Issue Tracker provider from the My Issues section in the Overview tab.
  • Left panel improvement:
  • In the left panel, you may now expand or collapse sections when filtering the left panel.
  • We plan to continue pushing more left panel improvements in future releases. Thanks for your feedback so far!

New in GitKraken 8.8.0 (Aug 11, 2022)

  • New + Improved:
  • No yield signs here – we’ve made it easier to get connected to your favorite Git client with Single Sign On for multiple providers.
  • Single Sign On:
  • GitKraken may now initiate an Oauth authentication flow with the following supported Identity Providers (IdPs):
  • Azure Active Directory
  • Okta
  • Google Identity Platform
  • Resources:
  • Requirements and configuration
  • Signing in with SSO
  • Overview in Workspaces:
  • A new Overview section has been added to Workspaces that focuses on the work most important to you across all the repos in a Workspace.
  • Partial stash:
  • Right-click on a single file or a selection of files in the commit detail panel to see options for stashing and applying changes.
  • Left panel improvements:
  • Sections in the left panel are now always visible and don’t scroll out of view.
  • Individual sections in the left panel can now be resized.
  • Aliases for submodules will now be displayed in the left panel.
  • New Tab view updates:
  • The Recent and Favorite Repos lists have been moved to the top of the Repositories section for easier access.
  • More autosuggest in GitKraken CLI:
  • Autocomplete for git remote prune and git remote update will now suggest remotes.
  • Fixed crashes and improved performance by approximately 2X to 3X when opening very large conflicts.
  • Improved the app performance when loading commit details.
  • Bug Fixes:
  • Users who installed GitKraken on Linux via Snap will no longer crash when opening file selection dialogs.
  • Resolving large conflicts with the context menu options will no longer crash GitKraken.
  • Fixed accounts not being listed when initializing a repo in a hosting provider.
  • GitKraken will now close open workspaces if the workspace was deleted from the organization.
  • Workspaces with no repositories will no longer load unexpected pull requests in the pull request section.
  • Fixed an issue where opening selected repositories within a workspace would open all repositories.
  • Fixed an issue where creating a new profile does not set a default organization even if the user belongs to an organization.
  • Fixed display issue for Google icon from the Google login/signup form.
  • Fixed a timing issue where the branch column would not show up for a workspace when you first create a workspace.
  • Fixed an issue where users could not create a workspace if the icon size was too big.
  • Removed unnecessary comment count column from Azure Workspaces.

New in GitKraken 8.7.0 (Jul 13, 2022)

  • New + Improved:
  • We hemmed in some new threads.
  • Watch v8.7 feature demo 🎥
  • GitKraken Client now supports the ability to create and apply patches.
  • Create patch from commit(s)
  • Create patch from uncommitted file(s)
  • Create patch from Command Palette
  • Apply patch from Command Palette
  • Left panel improvements – Left Panel now has a context menu to toggle visibility of the different sections.
  • New Tab update – Updated UI and layout.
  • Terminal Tab – Repo aliases will now show in Terminal Tab titles.
  • More fuzzy search – Enabled fuzzy search in gk history and gk blame commands in GitKraken CLI.
  • Search tabs list – Users may now search tabs by repo alias in the tabs list.
  • Naming branch from issue – When viewing an issue from inside GitKraken Client, there is now a short text field for naming the branch when creating a branch from the issue.
  • Git LFS performance improvements:
  • Users will see faster performance when cloning LFS repositories with submodules
  • Users will note much faster performance for general GitKraken Client actions, e.g. reset, merge
  • Bug Fixes:
  • We’ve stitched up a few loose ends.
  • Fixed issue related to GitKraken CLI’s autocomplete in Git Bash.
  • In Workspaces, users will be notified if attempting to open a deleted or unreachable repo from the repo details section.
  • Fixed task lists for GitLab issues showing  .
  • Commit graph will immediately update when the app performs a fetch or force push from the terminal.
  • Fixed issue where if two profiles both have the same repo tab open, switching profiles would cause issues to disappear from the left panel.
  • Changing accounts will now properly reset the selected Workspace.
  • In the Workspace Pull Request section, removing a filter and quickly selecting a PR will no longer generate a blank screen.

New in GitKraken 8.6.0 (Jun 16, 2022)

  • New:
  • You've got a friend in GitKraken.
  • Users can now create Workspaces using Bitbucket Server repos.
  • Users can now select Git Bash as their default shell in Windows for GitKraken CLI.
  • Users can set Git Bash as their default terminal by navigating to Preferences → Terminal → Default Terminal and selecting "Git Bash" from the dropdown menu.
  • Repo and Terminal Tab aliases:
  • Users can now set an alias for a repository.
  • To set an alias, users can right-click on a Repo Tab and select the Alias repository option.
  • Setting an alias through a Repo Tab will cause GitKraken Client to store that name for the repo and reference it as an “Alias Repository”.
  • Users can set an alias for individual Terminal Tabs.
  • To rename any Terminal Tab, users can right-click on the tab and select the Rename tab option.
  • Setting an alias to a Terminal Tab results in only renaming that specific tab.
  • Users can now set GitKraken Client to skip submodule updates while performing Git actions, either globally or per repo.
  • Improvements:
  • Faster for LFS, big repos, and beyond.
  • Git LFS performance improvements:
  • Users will see faster performance when cloning LFS repositories.
  • Users will note much faster checkout times in LFS repositories.
  • Sections in the left panel will now be collapsed by default.
  • Users can now set the maximum number of commits shown in the Commit Graph as low as 500 commits.
  • To set the shown commit limit, navigate to Preferences → General and look for Max Commits in Graph towards the bottom of that menu.
  • Users will note improved performance when the open repo has a large number of stashes.
  • When creating a pull request from a branch that starts with an issue ID (e.g, GK-123-feature-branch), a link to the associated issue will now be added to the pull request description automatically.
  • Bug Fixes:
  • You are a sad, strange little bug, and you don't have my pity.
  • When creating a new branch from an issue, users will see the input box as expected.
  • When working with remote branches in the left panel, the context menu will remain available.
  • GitLab avatars will now more consistently display correctly.
  • Branches will immediately refresh when a checkout is performed in a Terminal Tab.
  • Users connected to an Azure DevOps integration using Azure's older hostname style (eg. {organization}.visualstudio.com) will now be able to use Workspaces and the Pull Requests section in the left panel.
  • Users leveraging Azure DevOps Workspaces will no longer see a misleading ‘Add a Repository’ button in their Workspace. Users will need to visit Azure DevOps directly to add repositories to their Workspaces.

New in GitKraken 8.5.0 (May 18, 2022)

  • New:
  • Git is what gives a dev their power...It binds the galaxy together.
  • GitKraken WorkSpaces now support Azure DevOps repositories.
  • Any Workspace created for Azure DevOps will automatically include repos for a selected Azure Project.
  • Workspaces can currently support up to 100 repositories for an Azure Project.
  • Visual interactive rebase can now be initiated from the GitKraken CLI, which you can access from a Terminal Tab or a Repo Tab by clicking the Terminal icon in the top toolbar.
  • Users can type either gk rebase -i or gk rebase --interactive along with two refs to open the interactive rebase view. If only one ref is passed it will perform the rebase of the branch currently checked out onto the specified ref.
  • Improvements:
  • An elegant Git client for a more civilized age.
  • Git LFS Improvements:
  • Users will experience a reduced delay in updating the graph and commit detail panel when selecting commits in LFS enabled repos.
  • Note: Significant work towards reducing checkout times for LFS repos is underway and we plan to include these improvements in the GitKraken Client v8.6.0 release, scheduled for June.
  • When creating a new Team, members can now be added as part of the creation process.
  • Team members are now sorted by username in the Teams section, found in the left panel of GitKraken Client.
  • Improvements to GitKraken Workspaces:
  • Workspaces can now be shared as Team Workspaces, allowing users to share the Workspace with specific teams within their Organization.
  • In the Workspaces Repository view, clicking on the name of a repository will open it in a Repo Tab.
  • Users can view repository information by clicking on the Open Repository Details option, found on the right side of the Repositories view.
  • Organization admins and owners will see a new "Show All Workspaces" checkbox, allowing a simplified way to see all available Workspaces.
  • Users can now leverage GitHub’s search syntax when using the Workspaces Pull Requests view search.
  • Users will find more options for filtering in the Workspaces Pull Requests view. The new options include:
  • "Opened by Me", to show pull requests that were opened by the user. This filter is available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
  • "At Risk", to show any pull requests that are not drafts and have been open for longer than 7 days. This filter is currently only available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
  • "By repository", to limit the view to a single repo within the Workspace. This filter is currently available for Azure DevOps, GitHub, GitHub Enterprise, Gitlab, and Gitlab Self-Managed repositories.
  • For Windows users, GitKraken Client will now respect the core.longpaths setting in .gitconfig. Previously, GitKraken Client had its own longpaths setting independent of the user’s .gitconfig setting.
  • On Windows, core.longpaths now only applies to the files in the working directory, not in the .git directory, to maintain compatibility with Git for Windows.
  • GitKraken CLI autocomplete will now be able to suggest more than one argument in these commands:
  • git add
  • npm install
  • npm remove
  • yarn add
  • yarn remove
  • Notifications with a Call to Action will now be marked as read when the CTA is clicked.
  • Users encountering merge conflicts can now right-click on the conflicts shown in the Commit Panel to reveal new options for easier and faster conflict resolution. The new options available are:
  • "Take current", which applies the changes from the branch currently checked out to resolve the conflict.
  • "Take incoming", which applies the changes from the incoming branch to resolve the conflict.
  • Bug Fixes:
  • Bugs…You will never find a more wretched hive of scum and villainy.
  • GitKraken Client will now open as expected for users on OpenSSL 3 Linux distributions such as Ubuntu 22.04 and Fedora 36.
  • Users will see increased performance when opening a commit diff for very large images. Large images will now display as a binary file Instead of producing an error.
  • For large files, such as images and other media, we recommend using Git LFS.
  • Dotted graph lines will no longer take precedence when overlapping with solid lines in graph views.
  • Users can now type in the GitKraken Terminal as expected on a wider range of OS versions.
  • When un-hiding a remote, users can continue hiding or un-hiding remotes without waiting for the triggered automatic fetch to resolve.
  • Azure DevOps integrations and all self hosted integrations will now work properly on our new Teams license tier.
  • Users with hundreds or thousands of Azure DevOps Projects will see improved performance when integrating Azure DevOps.
  • Users can now use quotation marks when naming Workspaces.
  • All Organization and Team actions will remain available after using the login screen.
  • The scrollbar in the GitKraken Terminal will now remain clickable in all situations.
  • When a user pushes many files up at once to GitHub, they will no longer experience an OAuth infinite loop.
  • Opening repositories via gitkraken --path when GitKraken is already open will now work as expected.

New in GitKraken 8.4.0 (Apr 13, 2022)

  • New:
  • I pity the tool that does not have Workspaces or the GitKraken CLI.
  • GitKraken Workspaces:
  • Workspaces now include a Pull Requests view!
  • Users can filter PRs to see items "Assigned to me".
  • At-risk pull requests are highlighted through a label and filterable.
  • Selecting any GitHub pull request now shows the user a new Pull Request view that presents users options to quickly manage PRs across a whole Workspace.
  • Clicking on any repo in a Workspace now shows see more info and options. Users will see the repository's README, as well as quick access buttons to open the repository in a Repo Tab, Terminal Tab, or on the remote repository's hosting provider.
  • GitKraken CLI:
  • The Terminal button in a Repo Tab’s toolbar will now open the GitKraken CLI inside a Terminal Panel, instead of opening a new Terminal Tab. Users can still open new Terminal Tabs through a New Tab, the Command Palette, or through any Terminal’s context menu.
  • Users can toggle the Terminal Panel on and off by pressing the Terminal button in Repo Tab toolbar, through keyboard shortcut Ctrl+`, the Command Palette, the Terminal Panel’s context menu, or options in the GitKraken Client's View menu. Toggling the Terminal Panel will turn it on or off across all Repo Tabs.
  • A Terminal Panel session can also be terminated by executing the exit command. This will only close the Terminal Panel and not the Repo Tab. Toggling the Terminal Panel back on will initialize a new terminal session.
  • Unlike with the Terminal Tabs, navigating to a different working directory in a Terminal Panel will not change the repository opened in the Repo Tab.
  • The following gk commands are available in the Terminal Panel:
  • gk blame
  • gk diff
  • gk history
  • gk help
  • Improvements:
  • Making GitKraken Client a mean, clean Git managing machine.
  • Users will now see helpful icons when shown GitKraken CLI Autocomplete suggestions, helping clarify to which command the suggestion is related.
  • Git LFS users will see improved performance checkouts.
  • Bug Fixes:
  • Shut up, bugs!
  • Filtering Autocomplete suggestions by name will work as expected.
  • After selecting between multiple Autocomplete suggestions that have the same prefix, further suggestions will disappear as expected.
  • Users will no longer be allowed to create Workspaces for repositories on unsupported versions of GitLab Self-Managed services.
  • Bitbucket Server users will now see the branches correctly populated when creating Pull Requests.

New in GitKraken 8.3.3 (Mar 17, 2022)

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

New in GitKraken 8.3.2 (Mar 8, 2022)

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

New in GitKraken 8.3.1 (Feb 28, 2022)

  • Improvements:
  • Though short, February is filled with lots of love and sweet improvements.
  • GitKraken CLI:
  • Users who want to use the GitKraken Terminal when opening repositories in external terminals, alt/⌥ + T, can now set this as the default by navigating to Preferences → General → Default External Terminal and selecting "GitKraken Terminal" from the dropdown menu.
  • When hiding the visualization panel orientated to the top of the window, the toolbar will remain in place at the top.
  • Themes:
  • Users can customize the terminal colors together with the rest of their custom themes. This update removes the Terminal Theme setting from the Preferences → Terminal menu.
  • Bug Fixes:
  • The early birds of spring get the bugs.
  • GitKraken Client will remain responsive when adding an issue tracker integration supporting a large number of assignable users.

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.
  • 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.
  • 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.
  • 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)

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

New in GitKraken 8.2.0 (Dec 14, 2021)

  • New:
  • We have helped users progress and seen them accomplish wonders.
  • Introducing GitKraken Workspaces:
  • GitKraken Workspaces save teams time by providing an easy way to group repositories, take actions against multiple repositories at once, and quickly onboard new team members.
  • GitKraken Workspaces allow you to gather and access all the required repos for your project in a single tab in the GitKraken Client. The new GitKraken Workspaces tab shows you the status for the last branch that you checked out, how far ahead and/or behind in commits you are, and if there is an active WIP for each included repository.
  • GitKraken Workspaces can be created as Personal, only visible to you, or Shared, visible to all members of your Organization.
  • Users can access GitKraken Workspaces from the new “Workspaces” tab in the tabs bar, from the New Tab view, from the command palette, which can be opened with the keyboard shortcut cmd/ctrl + p, or from the newly added repository breadcrumb in any Repo Tab.
  • Users can view details and trigger the following actions on any or all of the repositories in a workspace at once:
  • Clone multiple repositories at once. This will help teams quickly onboard a new team member or get a new computer up and running.
  • View the last checked out branch for all repositories and see if a branch is ahead/behind a remote.
  • View work in progress for all repositories, including the number of files modified, added, renamed, or deleted.
  • Perform a fetch for all or a selection of repositories.
  • Open multiple repos in the GitKraken Client, or in an external editor, such as VS Code, IntelliJ, Atom, or Sublime Text.
  • Open any repository in the associated hosting service website.
  • GitKraken Workspaces can currently contain repositories hosted on GitHub.com, GitLab.com, or Bitbucket.org.
  • Themes:
  • Users may now create their own custom GitKraken Client themes.
  • For more information about creating a new custom theme, checkout our Themes documentation or navigate to gitkraken/themes/README.md.
  • Users will find two new themes when navigating to Preferences → UI Customization menu.
  • Users can now sync their GitKraken theme with their system theme, if their OS supports it.
  • Activity status:
  • An activity status will now display on the avatars of members in your GitKraken Organization or Team, indicating if they are actively using the GitKraken Client. This activity status icon is visible in the Team View section in the Left Panel, or in the Organization view in Preferences.
  • Users can manually set their status to “Active” or “Away” by selecting the circle icon in the top right corner, or by opening the Profile/Account dropdown menu.
  • GitKraken Workspaces and Activity status are currently unavailable for Self-Hosted and Stand-Alone customers.
  • Improvements:
  • When you love something, you improve it.
  • GitKraken CLI:
  • Users can now customize the behavior of the ↹ Tab key when using auto-complete in a Terminal Tab. This setting can be found under Preferences → Terminal → Tab Behavior.
  • Users can customize the cursor used in a Terminal Tab. This can be configured in Preferences → Terminal → Cursor Style. Users can select either Block, Underline or Bar for their cursor.
  • Auto-complete suggestions will now show branches and tags as options when running git diff or git reset commands.
  • The gk diff command now supports tags and branches as options.
  • Auto-complete suggestions have been added for npm and yarn.
  • When users open the pull request panel and click on a pull request while the left panel is minimized, the GitKraken Client will now open the pull request view.
  • Bug Fixes:
  • We came here years ago to protect users from these bugs.
  • When using the GitKraken CLI, suggestions will disappear as expected after auto-completing a command with escaped characters in the path.
  • After using the GitKraken Client to execute a cherry-pick and resolving any arising conflicts, the Git CLI will no longer report that a cherry-pick is currently active.
  • When creating a pull request in a repository with a large number of forks, users will no longer have to wait as all forks are being fetched before opening the dropdown menu.

New in GitKraken 8.1.1 (Nov 14, 2021)

  • Improvements:
  • Sudon't want to miss out on these new improvements.
  • GitKraken CLI Preview:
  • GitKraken CLI users can now use git help to display help information about using Git.
  • Windows users will now see an auto-suggest option for the cd command.
  • Users changing directories in the GitKraken Terminal will see auto-suggest options showing the end of the folder path rather than just the beginning. This is useful when long directory names are present.
  • Users can choose from more Keif options for their avatars when creating or editing their Profiles.
  • Bug Fixes:
  • There are only 10 kinds of bugs: the ones we have fixed and the ones that we have not identified yet.
  • GitKraken CLI Preview:
  • Improved GitKraken Terminal support for custom fonts, such as Nerd Fonts and Powerline fonts.
  • Users leveraging oh-my-posh in Powershell using custom themes will now see and be able to select auto-suggest options.
  • Users can now resize the commit panel in a GitKraken Terminal tab.
  • All Mac users are now able to use the gk commands.
  • Windows users leveraging “Constrained” language mode in Powershell can now execute gk commands.
  • Users can now resize the merge editor tool as expected when the visualization panel is positioned to the left or right in a GitKraken Terminal tab.
  • When working with GitHub and GitLab wiki repos, GitKraken will no longer throw an error message about being unable to fetch pull requests.
  • If a user checks out a commit while in Solo mode, they will now see the HEAD tag displayed.
  • Users fetching GitHub pull requests will no longer see timeouts.
  • Stand-Alone & Self-Hosted:
  • There is no place like:
  • The GitKraken CLI Preview is now available for Self-Hosted and Stand-Alone customers.

New in GitKraken 8.1.0 (Oct 15, 2021)

  • New:
  • The seasons continue to change and so does GitKraken...for the better!
  • The GitKraken Git client can now identify weak SSH keys and provide an easy way to remove and replace them. Read more on the GitKraken blog.
  • Improvements:
  • It's the time of year to reap the harvest of new improvements to the GitKraken Git client.
  • GitKraken CLI:
  • GitKraken CLI users can now use reverse search as expected by typing Ctrl+R in the terminal.
  • Mac users will now see the LANG environment variable pass automatically to the shell process.
  • When selecting an auto-suggest option with the mouse, GitKraken will now refocus on the terminal prompt.
  • The GitKraken CLI now supports 256 colors.
  • Mac and Linux users will now see auto-complete suggestions for the cd command.
  • When running gk blame or gk history, users will now see suggestions when navigating from inside a repository's subdirectory after typing ../.
  • Users will now see auto-suggest options for the git gc command.
  • In addition to showing or hiding the visualization panel, users can now orient it to the top, bottom, left, or right, as well as toggle the right-side commit panel using the visualization panel toolbar.
  • The user interface for user profile settings under the [Preferences] menu has been improved.
  • Users can now open specific comments on GitHub.com from the comments inside GitKraken's pull request or issue views.
  • Users who are not using GitKraken Integrations will no longer be repeatedly prompted for credentials for each remote when connected to repositories with multiple remotes sharing the same hostname.
  • Bug Fixes:
  • As the leaves fall, so do these bugs.
  • The overall reliability of notification delivery has been improved.
  • Auto-complete for Windows users leveraging the GitKraken CLI has been improved.
  • Windows users will no longer see a Named Pipes error when running gk commands in a terminal tab.
  • Using gk diff in the GitKraken CLI will produce properly parsed numerical SHAs.
  • When discarding a large number of files in a repository, the repo will fully load as expected.

New in GitKraken 8.0.1 (Sep 29, 2021)

  • Improvements:
  • GitKraken users can now search for a particular tab and navigate the menu using the keyboard when using the tab dropdown menu.
  • Bug Fixes:
  • Gitflow branch folders and tag folders collapse and expand as expected when selected in the left panel in GitKraken.
  • Layout and options have been optimized in the Organization panel in GitKraken's Preference view.

New in GitKraken 8.0.0 (Sep 23, 2021)

  • New:
  • “One tool to rule them all,
  • One tool to find them,
  • One tool to bring them all
  • and in the Git log bind them.”
  • Introducing the GitKraken CLI Preview:
  • The GitKraken CLI adds a Git-enhanced, keyboard-driven, terminal experience to the GitKraken Git Client. Get the powerful Git visualizations GitKraken is known for—like the commit graph—in the context of a Terminal Tab. Plus auto-suggest and auto-complete for Git commands to help you drive (and learn) Git faster, with fewer mistakes.
  • Dive deeper into file changes with the gk commands. Use the command gk history to see File History and gk blame to see what has changed in a file or commit and who made those changes.
  • During the GitKraken CLI Preview we are looking for feedback to help improve this feature. Please use the Feedback form linked in the bottom right corner of your GitKraken app, or email us at [email protected].
  • Users can open Terminal Tabs in a number of ways.
  • Clicking the "New Terminal Tab" button after opening a New tab in GitKraken.
  • From the "Terminal" button in the toolbar of a Repo tab (opens the current repo in a Terminal Tab).
  • From the Command Palette (Ctrl/Cmd + P).
  • When working in a Terminal Tab, you can open a new Terminal Tab with the key combination Ctrl/Cmd + T. The new Terminal Tab will open in the same working directory.
  • Auto-complete and auto-suggest make building Git commands easier than ever before in the GitKraken CLI. This feature works for users of PowerShell for Windows, ZSH and Bash for Mac/Linux.
  • Auto-complete and auto-suggest are configured for the most common Git commands, but we are continuing to build out this feature and would love feedback on which commands and parameters you want added.
  • Please be aware that other auto-complete programs could potentially cause the GitKraken CLI auto-complete to stop working. You may need to uninstall or disable those other programs to use this feature.
  • Note: If you switch shells, you'll need to set the new shell as default in your operating system settings and restart your computer for auto-complete to continue working as expected.
  • Some of the legendary Git visualizations that GitKraken is known for are also accessible within Terminal Tabs. To quickly view the commit graph, file diff, history, and blame view, simply type these commands:
  • gk panel: toggles the visualization panel on or off. You can also reposition the panel to the top, bottom, left, or right by adding those parameters to the command. For example gk panel right moves the panel to the right of the screen.
  • gk graph: shows the graph view. While this command has similar behavior to gk panel, even allowing repositioning of the graph with the same top, bottom, left, or right parameters, this command also returns to the graph if you're in a different view and has subcommands for toggling the graph columns with the keyboard.
  • gk history and gk blame: open the history or blame panel for a specified file.
  • gk diff: shows changes between commits. If no commit SHAs are provided, it will use your WIP and HEAD. If only one commit SHA is provided, it will be compared with HEAD.
  • gk --help: shows the list of available gk commands. You can also use --help on a specific gk command to see its arguments.
  • A toolbar above the panel will display the current repository name, branch, tag, and the number of changes pending to be pulled and/or pushed. Clicking this toolbar will toggle the panel on or off.
  • For Free accounts, this visualization panel will only be accessible within publicly-hosted repositories.
  • A Terminal section has been added to the Preferences menu that allows Terminal Tab customization:
  • Font choice. Changes to this setting will only apply to new Terminal Tabs.
  • Font size.
  • Enable auto-complete & auto-suggest.
  • Default the visualization panel position when opening a new panel: top, right, bottom, or left.
  • Show the visualization panel by default. This will apply only when opening new tabs.
  • Terminal theme.
  • Deep Linking:
  • "Oh, it’s quite simple. If you are a friend, you speak the password, click the link, and the doors will open."
  • We've added the ability to share deep links to specific remote repositories, commits, branches, and tags in GitKraken. This allows users to more easily collaborate and save time when working in issue queues or Git pull requests.
  • When shared, these links will both open and focus GitKraken to the linked repository. The links will focus GitKraken on the commit, branch, or tag specified. When specifying a branch, the latest commit of that branch will be focused.
  • The links can be found in GitKraken's context menus under Copy link to remote/commit/branch/tag.
  • Jira App Integration - Git Integration for Jira:
  • "It’s the Jira ticket that’s never started that takes the longest to finish."
  • GitKraken now works with the Git Integration for Jira app to allow quick navigation between GitKraken and Jira when viewing commits and file diffs related to Jira issues.
  • In GitKraken, you’ll find buttons and links to open the following in Git Integration for Jira:
  • File diffs - within the file diff view and in file context menus.
  • Commits - context menu when right-clicking commits in the graph.
  • In the Git Integration for Jira, anywhere you view commits and diffs will automatically have links to open them in GitKraken.
  • To leverage GitKraken’s Git Integration for Jira integration you will need to:
  • Connect Jira Cloud Integration in GitKraken.
  • Select Jira Cloud as the Issue Tracker for a repository.
  • Select a Jira Project.
  • Install Git Integration for Jira on the same Jira Cloud instance as the Jira Project.
  • Improvements:
  • "Even the smallest update can change the course of history."
  • The Fuzzy Finder is now the Command Palette!
  • We've renamed the Fuzzy Finder to the Command Palette. You can still open the command palette through the keyboard shortcut Ctrl/Cmd + P, or through the new magic wand icon in the toolbar.
  • Tab navigation has been significantly improved when many tabs are open at once.
  • We have improved the tooltips to provide both tab title and repo information.
  • Tooltips will now instantly appear when hovering the entire tab, not just the title.
  • A new dropdown list has been added to the tabs bar to help with tab navigation.
  • Reopening tabs after a “close all tabs to the right”, a “reopen closed tab” will now reopen only one tab at a time, instead of all that were closed at once.
  • An option to “Quote Reply” has been added for comments in the PR view.
  • The profile menu now shows the Organization associated with the current profile.
  • A “Cancel Rebase” button has been added at the top right of the Interactive Rebase panel for easier access.
  • We have improved form, prompt, and modal keyboard navigation and submission.
  • Improved user experience for the login form.
  • Bug Fixes:
  • "You (bugs) shall not pass!"
  • Styling of long branch names in the right panel has been improved.
  • Users will no longer see issues for remotes without access to a repo, as happens when users leave an organization or when forks are deleted.
  • When using the delete key to erase spaces in a URL, the cursor will behave as expected.
  • The Pull Request icon has been added back to branch labels in the graph.
  • The bottom of Diff views are no longer cut off when the file mode changes.
  • Relative paths are now allowed in hooksPath.
  • All users are now able to select a project for GitLab and GitLab-Self-Managed issues on the left panel.
  • If Sublime Text 4 is installed, it will now be detected and appear in the external editor dropdown.
  • Debouncing has been added in the left panel search. Searches will be executed when you stop typing, instead of on each letter, making it easier to find what you’re looking for.

New in GitKraken 7.7.2 (Aug 11, 2021)

  • New:
  • Users who are leveraging Git hooks in their workflows will be happy to learn that GitKraken now supports the Git configuration core.hooksPath variable. Users can also change the directory for where a repository’s hooks are stored from inside GitKraken by navigating to Preferences → Git Hooks.
  • Improvements:
  • We’ve improved performance for the new GitKraken Teams features. Users will notice that repository actions respond faster, especially for larger repositories.
  • Untracked files will no longer appear in the GitKraken Teams Panel if those files have not been modified.
  • Bug Fixes:
  • GitKraken Merge Conflict Editor users can now scroll horizontally, even if the scrollbar is over a conflicted line.
  • When switching tabs, GitKraken will now remember what panes users had collapsed, as well as which branches & tags had been hidden.

New in GitKraken 7.7.1 (Jul 28, 2021)

  • Improvements:
  • All users will notice improved performance when switching between tabs in GitKraken.
  • The Author and Team filter lists are now sorted alphabetically by default, making it easier to find what you are looking for.
  • Bug Fixes:
  • When opening repositories in GitKraken, users will no longer get stuck on the loading screen.
  • GitKraken users will no longer encounter a loop repeatedly asking for their SSH passphrase.

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)

  • Bug Fixes:
  • Resolved an issue that was preventing some repositories from rendering when connected to GitLab Self-Managed.

New in GitKraken 7.6.0 (May 13, 2021)

  • New:
  • Because moving at impulse power on GitHub was too slow...
  • Github.com users may now utilize the Pull Request view! Selecting a pull request in the left panel will bring up the pull request view which will allow users to:
  • Edit the pull request title, description, reviewers, assignees, milestones, and labels.
  • Comment on a pull request.
  • Merge a pull request from GitKraken.
  • Submit reviews by leaving a comment, approving the PR, or requesting changes.
  • GitKraken users at all plan levels can now create and edit issues on GitHub and GitLab public repositories.
  • Improvements:
  • We’re giving it all we got...
  • The cherry pick option has been removed from the context menu that appears after selecting multiple commits in the graph. GitKraken does not support the ability to cherry pick multiple commits...yet.
  • Markdown and styling have been improved throughout the application, most notably in issue detail view and the in-app release notes.
  • The scrollbar in the hunk diff view has been improved so it is selectable in all cases.
  • Bug Fixes:
  • Fixing the trouble with tribbles bugs...
  • Scrolling through a list of tracked LFS file types will feel smoother and render correctly.
  • The left panel will no longer disappear if a GitHub workflow file contains only content that has been commented out.
  • Pull request information will no longer render multiple times, and text artifacts will no longer clutter the left panel.
  • The diff and issue detail views can no longer be opened simultaneously when the commit panel is pinned to the bottom of the screen.
  • The .gitignore file generated when initializing a repository form GitKraken will no longer be set as read-only.
  • Notes:
  • Shields up...
  • We have improved security by no longer accepting untrusted SSL certificates used with self-hosted integrations, like GitHub Enterprise, GitLab Self-managed, and Bitbucket servers. If you notice issues with connecting or using one of these integrations, please visit our support site for more information about configuring your system.

New in GitKraken 7.5.5 (Apr 13, 2021)

  • Bug Fixes:
  • Resolved an issue that was causing GitKraken to sporadically crash on Mac and Linux when performing certain actions.
  • Fixed another crash that could occur when performing checkout operations.
  • Notes:
  • In an upcoming release of GitKraken, the minimum supported version of GitHub Enterprise will be 2.20.24 in order to use the integration. We anticipate this change to go live at the beginning of May.

New in GitKraken 7.5.4 (Apr 6, 2021)

  • Bug Fixes:
  • Resolved an issue that was causing GitKraken to crash for some users when trying to push.

New in GitKraken 7.5.3 (Mar 26, 2021)

  • Bug Fixes:
  • Using HTTPS over a proxy will no longer incorrectly throw the error message: Failed to get server certificate: The handle is in the wrong state for the requested operation
  • Hitting the Delete button in the commit message box when a commit template is present will no longer generate new lines.
  • The cursor will no longer jump to the end of the line when typing in a feedback or support form.
  • Repositories containing empty annotated tags will no longer cause GitKraken to crash on Mac and Linux.
  • Squashing in interactive rebase will no longer cause GitKraken to deadlock.
  • The error message: Failed to initialize [object Object] will no longer appear for GitLab users.
  • Error logs can again be opened using the File menu.

New in GitKraken 7.5.2 (Mar 2, 2021)

  • Improvements:
  • The tooltip display has improved when dragging-and-dropping branches in the left panel.
  • If a WIP node is present when a user selects Reset Local to Here to checkout a remote branch, GitKraken will now create a stash.
  • The profile dropdown menu will now close after switching profiles.
  • Bug Fixes:
  • Relative timestamps will display correctly in the graph.
  • Desktop notifications will render as intended.
  • A newline can now be prepended to the commit description field.
  • The option to delete a remote tag will again appear when deleting subsequent tags after deleting a tag from a remote repository.

New in GitKraken 7.5.1 (Feb 9, 2021)

  • Nobody:
  • GitKraken:
  • Ayy here's a hotfix for a big ol oopsie whoopsie we made (aka critical stability improvements for syncing GitKraken notifications).

New in GitKraken 7.5.0 (Jan 22, 2021)

  • New:
  • After all, Git can also be beautiful...
  • A notifications system has been added to GitKraken to alert users of important messages such as version updates, bug fixes, and more helpful information. These notifications can be accessed via the bell icon 🔔 in the upper right corner, and notification settings can be configured via Preferences Notifications
  • Improvements:
  • Well, that’s mate in 3.
  • The hamburger menu in the upper right corner has been removed. Preferences can now be more easily accessed through a new gear icon ⚙️.
  • The profile dropdown menu has been redesigned to better distinguish a user's Git authoring details from their GitKraken account details.
  • Users will now see the options to Show/Hide when multi-selecting local branches and stashes from the left panel.
  • Bug Fixes:
  • Bugs….it’s time to resign.
  • Actions accomplished by tab-related keyboard shortcuts will no longer be duplicated.
  • Users can again toggle the left and commit panels from the View menu options.
  • The left panel will no longer disappear if users have an empty yaml file in their repository’s github/workflows/ folder.

New in GitKraken 7.4.1 (Dec 2, 2020)

  • Improvements:
  • After a commit action has been made in GitKraken, a timestamp showing the duration of the action will be added to the activity log.
  • Bug Fixes:
  • The GitLab Self-Managed issue tracking integration will work for instances that have a URL path or protocol.
  • Fetching and auto-fetching while a file is open in GitKraken will no longer reset the scroll position on the Monaco text editor.
  • Stashing while the WIP node is selected will select the parent commit.
  • Post-checkout hooks will run correctly when starting a Gitflow Feature, Release, or Hotfix branch.

New in GitKraken 7.4.0 (Oct 29, 2020)

  • New:
  • These are the key points of GitKraken v7.4.0:
  • Users may now authenticate their GitKraken account using Google OAuth.
  • We have added a header to the commit graph, making resizing columns easier.
  • We have added the option to display additional columns of information in the commit graph:
  • Commit author
  • Commit date/time
  • Commit SHA
  • GitHub users now have the ability to create draft pull requests in GitKraken.
  • Improvements:
  • These improvements fit with GitKraken like a lock and key.
  • Now, when assigning an assignee or reviewer to a pull request, the dropdown menu will display the user’s name and username.
  • Autocomplete suggestions will now appear when creating or editing GitHub filters.
  • Search results will be more accurate when opening a repo via the Fuzzy Finder.
  • Keyboard shortcut Ctrl/Cmd + K can now be used to toggle the visibility of the commit panel on and off, while keyboard shortcut Ctrl/Cmd + J can be used to collapse and expand the left panel. The visibility of these panels can also be toggled from the View menu.
  • Bug Fixes:
  • Thanks for putting up with these door-key release notes we’re almost finished.
  • Users will again receive a notification when GitKraken automatically resolves a merge conflict.
  • Branches will load in the Pull Request panel in repositories that have a space or hyphen in the repo name.
  • Users will now be prevented from setting editor tab size to 0 as that was causing performance issues when viewing diffs.
  • Finishing a release branch with Gitflow when the commit on the local master and develop branches are the same will no longer cause GitKraken to display a blank screen.
  • The Add a remote and checkout context menu option will only appear once.
  • Issue tracking for GitHub Enterprise will work for instances that have a URL path or protocol

New in GitKraken 7.3.2 (Sep 13, 2020)

  • Bug Fixes:
  • We have resolved an issue preventing remote icons from appearing in the graph for some users.

New in GitKraken 7.3.1 (Sep 10, 2020)

  • Bug Fixes:
  • We have resolved an issue causing the Ubuntu snap version of GitKraken to crash for some users.
  • Users will no longer encounter an error message when switching between profiles.
  • The icon noting when a branch is associated with a card will display properly for the GitKraken Boards issue tracking integration.

New in GitKraken 7.3.0 (Aug 26, 2020)

  • New:
  • Mona and Keif have been friends for a long time, and now, they have even more to celebrate in their friendship.
  • The GitKraken Git GUI now supports issue tracking integrations for GitHub and GitHub Enterprise! GitHub Issues users now have the ability to perform the following actions from GitKraken:
  • View and filter a list of issues from the left panel.
  • Create a branch tied to an issue.
  • View issue details.
  • Edit assignee of an issue.*
  • Edit state of an issue.*
  • Add/remove labels.*
  • Comment on an issue.*
  • Create new issues.*
  • *Paid features.
  • Improvements:
  • Users may now set a custom default branch name when initializing a new repository. Set a default branch by navigating to Preferences General Default Branch Name.
  • GitHub users now have the ability to fork a remote repository and add it to the left panel via a new context menu. This option will only appear if you do not have any existing forks of the repository.
  • GitHub users now have the ability to add an existing fork of a cloned repository. A pop-up message will appear in the left panel.
  • Bug Fixes:
  • Clicking on a remote reference in the left panel will select that remote reference in the graph.
  • An issue has been resolved that was preventing some Jira users from viewing issue details.

New in GitKraken 7.2.0 (Aug 5, 2020)

  • New:
  • GitLab users will feel even more cunning 🦊 while managing issues directly from the GitKraken Git GUI.
  • The GitKraken Git GUI now supports issue tracking integration for GitLab & GitLab Self-Managed! GitLab Issues users now have the ability to perform the following from GitKraken:
  • View and filter a list of issues from the left panel.
  • Create a branch tied to an issue.
  • View issue details.
  • Edit assignee of an issue.*
  • Edit the state of an issue.*
  • Add/remove labels.*
  • Comment and reply on an issue.*
  • Create new issues.*
  • Adding and removing labels is now supported for all issue trackers.*
  • *Paid features.
  • Improvements:
  • Time to clean up that foxhole.:
  • Users can now multi-select branches in the left panel. This can be extremely helpful for quick clean up, like deleting all local branches.
  • The Preferences menu has been updated. The Authentication section has been renamed to SSH, and we have added a new Integrations section for accessing both Git and issue tracking integrations.
  • After pushing changes to a remote branch, the Push Successful notification will include a link to view the PR on the related hosting service.
  • Users can now use Esc to close the Create Issue and Create Filter panels.
  • When creating a new issue, users will see required fields noted with an asterisk.
  • When creating a new branch tied to an issue, users can now select the base of the branch.
  • Bug Fixes:
  • What does the fox say? “NO” to these bugs.
  • For GitLab users: when creating a merge request, clicking on Continue editing in GitLab will no longer take users to a 404 error page.
  • Users can now successfully delete remote tags.
  • GitKraken will no longer disconnect users who utilize multiple services that reside on the same base domain.
  • For Trello users: “Closed” boards will no longer appear in the Board dropdown menu in the left panel.
  • After deleting a local tag, the following prompt to delete that tag from all remotes works as intended.

New in GitKraken 7.1.0 (Jul 15, 2020)

  • New:
  • Hello? Can you hear us? It’s the GitKraken Git GUI here to announce Trello integration.
  • The GitKraken Git GUI now integrates with Trello as an issue tracker! Once the connection has been authorized, Trello users will be able to accomplish the following from GitKraken:
  • View and filter a list of cards from Trello boards in the left panel.
  • Create branches tied to a card.
  • Create new Trello cards from within the GitKraken Git GUI.*
  • Select cards from the left panel to view card details. From the card details pane, users can perform the following actions:
  • Edit the list of a card.*
  • Edit member(s) of a card.*
  • Add comments to a card.*
  • *Paid features.
  • Improvements:
  • At least we can say that we’ve tried…
  • We have added the ability to re-open closed tabs.
  • Users can now reorder filters in the left panel using drag-and-drop.
  • For users who have integrated an issue tracker: we have added an option to the context menu for branches tied to an issue or card allowing users to view the issue or card both inside the GitKraken Git GUI and the respective issue tracker.
  • Users will now be asked for confirmation before removing a filter.
  • Bug Fixes:
  • These bugs must have called a thousand times to tell us they’re sorry...
  • The left panel will no longer vanish due to an issue with the Jira integration.
  • The GitKraken Git GUI is now able to detect all versions of IntelliJ.
  • After selecting a Clone or Initialize path, the path will be auto-filled next time.

New in GitKraken 7.0.1 (Jun 8, 2020)

  • Improvements:
  • We have added a right-click context menu to Tabs. Right click on an opened tab to access the following options:
  • Close selected tab.
  • Close all other opened tabs.
  • Close all tabs to the right of the selected tab.
  • When starting a pull request from a branch associated with a Jira or GitKraken Boards issue, the GitKraken Git GUI will now populate pull request titles.
  • When viewing issue details, users can now navigate to an associated branch by clicking the branch name, or double-clicking the branch to checkout.
  • The status color and text for Jira issues is more legible in Light Theme.
  • We have removed the unassigned Jira default filter.
  • Bug Fixes:
  • Default Jira filters that are created inside the GitKraken Git GUI will no longer throw an error if the project prefix was a JQL reserved word.
  • The My Cards default filter will now populate with cards assigned to a user on a GitHub-synced board.
  • Search results will no longer display NaN when filtering in the left panel.

New in GitKraken 7.0.0 (May 22, 2020)

  • New:
  • Got issues? Keep them in Jira! Now you’ll have no issues tracking your issues because you can stay in the GitKraken Git GUI. New integrations for Jira Issue Boards and GitKraken Boards make it possible to resolve and manage issues directly from the GitKraken Git GUI.
  • GitKraken Git GUI now integrates with the following issue trackers:
  • Jira (Cloud & Self-Hosted)
  • GitKraken Boards
  • After setting up the integration, users will be able to do the following from the GitKraken Git GUI:
  • View and filter a list of project issues
  • View issue details
  • Create branches that are tied to an issue
  • Add comments*
  • Edit the status/column of an issue*
  • Edit the assignee of an issue*
  • Create new issues*
  • Features denotated with * are paid features for Jira integration and free for GitKraken Boards integration.
  • Users can now open repositories inside of the following text editors via the Fuzzy Finder, menu, or keyboard shortcuts (Ctrl/Cmd + Shift + E):
  • VS Code
  • Atom
  • Sublime
  • IntelliJ
  • Local repositories without a remote setup now include an option to create a remote and push local changes.
  • Improvements:
  • You’ve still got issues, but at least your favorite Git GUI is still improving...
  • When creating a GitHub pull request in the GitKraken Git GUI, users can now search for reviewers and assignees by name or username.
  • The text color in a commit description will change when the placeholder text has been replaced.
  • Users now have the ability to rename remotes.
  • ed25519 and ecdsa SSH key pairs are now supported.
  • For Windows users: the Open with GitKraken menu option will now open a new tab inside of the GitKraken Git GUI instead of a new window.
  • Pull request links can now be copied through the context menu.
  • Bug Fixes:
  • We take issue with bugs...
  • The From Repo drop-down menu will populate results when opening a pull request.
  • Users can successfully initialize a repository on a Bitbucket server from the GitKraken Git GUI.
  • For Windows users: the Open in File Manager menu option, keyboard shortcut, and Fuzzy Finder action now work as intended.
  • Snapcraft:
  • For Snap users: the snap for the GitKraken Git GUI has been moved to the classic confinement! Before updating to v7.0.0 of GitKraken, please install the snap with the --classic flag.

New in GitKraken 6.6.0 (Apr 22, 2020)

  • Improvements:
  • GitKraken now supports Bitbucket Workspaces.

New in GitKraken 6.5.4 (Mar 10, 2020)

  • Improvements 🙌:
  • Who needs luck when you have improvements as golden as these? 🍀
  • When users select a parent SHA in the commit panel, you will now be navigated to the parent commit.
  • The Cmd/Ctrl + F keyboard shortcut will now open the file search option if used when opening a file diff.
  • Bug Fixes 🐛:
  • Blarney! These bugs were making us green. 🤢
  • The list of commits in Blame and History views will no longer duplicate.
  • Signed annotated tags will no longer display the related GPG signature in the tooltip.
  • The commit panel will now show names of both the committer and the commit author if the names are different but the email addresses are the same.

New in GitKraken 6.5.3 (Feb 23, 2020)

  • Improvements 🙌:
  • For Windows users: We've addressed a false positive report from Windows Defender that GitKraken contained a Trojan virus. We have thoroughly investigated the issue and have verified the report was a false warning and GitKraken never contained a virus.

New in GitKraken 6.5.2 (Feb 23, 2020)

  • Improvements 🙌:
  • Don’t even try to tell us these improvements don’t tentacle your fancy…
  • Now, when users hover over the Push button in the toolbar, the upstream of the branch you’re pushing changes to will be displayed.
  • GitKraken will now remember the last directory to which you cloned a repository.
  • Bug Fixes 🐛:
  • We just had to break up with these bugs...it’s not us, it’s them. 💔
  • Now, when users rebase in GitKraken, the application will correctly remember your profile’s name and email address.
  • If you cancel a rebase from GitKraken’s merge conflict tool, the tool will now reset properly.
  • GitKraken will successfully perform a fetch, even if a pull request author has deleted their account on the related hosting service.

New in GitKraken 6.5.1 (Jan 29, 2020)

  • Bug Fixes:
  • The main process for MacOS users will now correctly display as “GitKraken” rather than “Electron.”
  • If the GitKraken application crashes, it will now automatically relaunch.

New in GitKraken 6.5.0 (Jan 24, 2020)

  • New:
  • All we can say about these new features is….Fork Yeah!
  • GitHub Users now have the ability to fork repositories from inside the GitKraken application. Now, when adding a remote, GitKraken will check to see if a fork exists for your current repository. If a fork does exist, GitKraken will offer to add your fork as a remote repository; if a fork does not already exist, GitKraken will provide an option to fork the repository and add a newly created fork as a remote in GitKraken.
  • GitKraken now supports core.longpaths, making it possible for Windows users to work with long paths exceeding 259 characters in length.
  • Improvements:
  • Some said it was too spoon to go for another performance improvement...but for fork’s sake, we just had to do it. And with reduced memory consumption and application size, you have more room on your plate for the good stuff.
  • Application startup time for GitKraken has improved, making it up to 10% faster.
  • Memory consumption for GitKraken has been reduced by up to 20%.
  • The application size for GitKraken has been reduced by up to 30%.
  • We have added a loading icon to the left panel when adding a remote.
  • Bug Fixes:
  • Please forkive us for these bugs...they were preventing us from providing our knifest experience possible.
  • If the left panel is collapsed, users can open all menu options.
  • All rows will be styled correctly in Interactive Rebase view.
  • Enterprise:
  • Enterprise users running on Linux now have an option to Check for latest update in the File menu.

New in GitKraken 6.4.1 (Dec 23, 2019)

  • Bug Fixes:
  • If stashes are created externally, users can now view the content of those stashes inside of GitKraken.
  • Creating branches titled constructor or toString will no longer cause repositories to become invisible.
  • GPG users using Git for Windows with non-empty passphrases will be prompted for their GPG passphrase instead of seeing the message: Error: GPG passphrase not found.
  • Git Hook activity log tabs will no longer display the word Repository.

New in GitKraken 6.4.0 (Dec 13, 2019)

  • New:
  • A long time ago in a galaxy far, far away...was a Git GUI without activity logs.
  • Introducing Activity Logs! 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 Get Support 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 Upgrade Now 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 6, 2019)

  • Improvements:
  • Users now have the ability to force push tags. The action will trigger a warning message.
  • Pushing a tag to all remotes is faster.
  • Bug Fixes:
  • MacOS Catalina users can access the terminal option.
  • Initializing a repository inside of GitKraken no longer causes an empty screen to display.
  • Interacting with a remote host or proxy that is self-signed will no longer cause the error message: Failed to get server certificate: The handle is in the wrong state for the requested operation.
  • Users can successfully checkout a submodule change where the URL has been modified.

New in GitKraken 6.3.0 (Oct 15, 2019)

  • New:
  • No need to hold a séance, this new search feature will help you conjure those spirits. Uncle Fester...is that you?
  • Users can now associate Glo cards with pull requests created from within the GitKraken Git Client. When creating a new pull request, simply search for the Glo card you wish to associate. The pull request description will then be updated to include a link to said card. Better yet, if you’ve set up the GitHub pull request integration, you can trigger an automatic change to progress your card to a new column the moment your PR status changes.
  • Users can now control the max number of commits that display in your graph. Navigate to Preferences → General and set a value for Max Commits in Graph. You will also see an option to Show All Commits in Graph.
  • Improvements:
  • We brought in Gomez and Morticia to class this place up with some supernatural improvements.
  • Users can now resize the text field to amend commit messages, and the Update Message and Cancel Amend buttons are now closer to the text field.
  • SSH keys using the OpenSSH format are now supported.
  • Bug Fixes:
  • With Lurch’s help, we’ve banished these bugs back to the cemetery.
  • Users can successfully drag-and-drop remote references to generate the menu option to start a pull request.
  • Users can switch tabs without the operation feeling sluggish.
  • Initials will correctly display inside of Blame View instead of Gravatar images when the Display author initials instead of avatars option is selected.
  • Keyboard shortcuts for Glo will now work after switching to a Glo tab.
  • If Glo is unreachable from the GitKraken Client, the application will correctly timeout and show an error message instead of hanging indefinitely.

New in GitKraken 6.2.1 (Sep 25, 2019)

  • The GitKraken team has released the ghouls of Sleepy Hollow to add some spooky new features, improvements, and bug fixes to version 6.2.1 of our Git client.
  • New:
  • The headless horseman is on the move...and all that’s left of Ichabod Crane is a shattered pumpkin.
  • Users can now enter a detached HEAD state by clicking the commit you wish to checkout and selecting Checkout this commit.
  • Improvements:
  • The editor line endings preference will only apply to new files created in GitKraken.
  • Bug Fixes:
  • Users can successfully clone a repository with a space in the name over HTTPS when using the Azure DevOps integration.
  • The initialize submodule prompt will work properly after cloning a repository with submodules.
  • Unstaged diffs for submodules will display accurately.
  • Loading a diff will no longer cause the application to crash.

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 22, 2019)

  • Improvements:
  • We’re going for the Dean’s List with this improvement.
  • Stashing time has been improved for stashing staged files.
  • Bug Fixes:
  • These bugs have been expelled from campus!
  • Users can again create a remote repository and clone it using an integration.
  • The Commit Search will return expected results when a stem word is queried.
  • Enterprise:
  • A+ grades across the board for these updates to our Enterprise Git Client.
  • The option to Sign in with GitHub has been removed.
  • The Linux Enterprise Client will now update properly.

New in GitKraken 6.1.3 (Aug 16, 2019)

  • The Electron cache now clears automatically with each update to ensure Glo tabs load correctly.

New in GitKraken 6.1.2 (Aug 16, 2019)

  • Improvements:
  • The baboons are going ape over this improvement.
  • The performance of GitKraken’s stashing functionality has been improved.
  • Bug Fixes:
  • We respect all living creatures, from the crawling ant to the leaping antelope, but this bug got to go -- sorry Pumba!
  • The libgit2 version has been updated to address a recent security patch.

New in GitKraken 6.1.1 (Aug 12, 2019)

  • Bug Fixes:
  • Users behind an authenticated proxy will now see a prompt for their credentials inside of the Release Notes & Glo tabs.
  • Renamed the duplicate GitLab.com option under Preferences → Authentication back to GitLab (Self-Managed).

New in GitKraken 6.1.0 (Aug 9, 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 17, 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 the location of 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)

  • Bug Fixes:
  • Resolved an issue that prevent GitKraken from opening on RHEL & CentOS.

New in GitKraken 5.0.3 (Mar 27, 2019)

  • Features:
  • Y’all ready for this? Users may now resize the reference column inside the graph.
  • Whoop there it is: Favorite repositories are just a keyboard shortcut away. By typing CTRL/CMD + 1/2/3/etc, you will open your favorite repos in the corresponding order.
  • We know you have that favorite TuneSquid player... Users are now able to reorder favorite repositories.
  • C'mon, check it out, y'all ready to jam? We added a search filter to the repository management modal.
  • Improvements:
  • No more flagrant fouls! Spell-checking has been added to the support and feedback forms.
  • By typing the keyboard shortcut Ctrl/Cmd + Shift + M, users now have the ability to focus the commit message box. Nothin’. But. Net.
  • Bug Fixes:
  • Bitbucket Server users will no longer experience an indefinite hang when opening a pull request or initializing a new repository. Sorry, hang time isn’t allowed on the GitKraken floor.
  • What’s up doc? The hide/show all tags context menu will now correctly hide and show annotated tags.
  • NOT. TODAY. Mr. Swackhammer… Commits made with an email address that doesn’t match your GPG key email address will no longer display as trusted.
  • Keif with the assist! GitKraken now supports different locales of GPG when signing a commit.
  • Initializing an LFS submodule will no longer cause GitKraken to crash. No more busted brackets workflows around here.
  • Alley-oop! Performing a pull on a repository with submodules configured with SSH should now correctly update the submodule.
  • Stand-Alone Clients:
  • The license.dat file may now be added to GitKraken’s parent directory. SHAZAM!

New in GitKraken 5.0.2 (Mar 18, 2019)

  • Bug Fixes:
  • The error toast Cannot read property 'hostname' of undefined should no longer appear when doing git operations with a SSH key that has a passphrase.

New in GitKraken 5.0.1 (Mar 13, 2019)

  • Bug Fixes:
  • Rebasing a branch while a WIP node is present will no longer cause GitKraken to get stuck on a loading screen.

New in GitKraken 5.0.0 (Mar 13, 2019)

  • Features:
  • Raise your chalice! GitKraken now supports GPG commit signing. This helps verify the identity of users making commits within GitKraken, and prevents other users from fraudulently using your alias to make commits. After all, there’s only one true King of the North.
  • GitKraken now has Interactive Rebase functionality—with a process so smooth and efficient you’ll feel like Brienne of Tarth with a sword. When you drag-and-drop a branch to rebase, you will now see an option for interactive rebase. After opening the interactive rebase view, you can choose from a menu of actions for each commit:
  • On the left, pick, reword, squash, or drop commits.
  • Use up and down keys to navigate commits.
  • Double-click a commit to reword.
  • Drag-and-drop to move commits up and down.
  • Use keyboard shortcuts to perform all of these actions!
  • You can also right-click on a commit in the graph to access the interactive rebase option for child commits:
  • Squash without HEAD
  • Move commit
  • Edit commit message
  • Drop commit
  • Improvements:
  • Fetching on a repository with multiple remotes is now faster. It will feel like flying on a dragon!
  • Braavos! An option to clone a repository has been added to the GitKraken welcome screen.
  • The commit panel will now display the committer in addition to the author if the two are different. No more taking credit for the accomplishments of others, Littlefinger...
  • Bug Fixes:
  • Our team resolved a memory leak that would occur with the Fetch operation. Varys and his birds will have to find their secrets elsewhere.
  • GitKraken will no longer throw a “Fetching pull requests failed” error when fetching from an Azure DevOps repository without using the integration. Daenerys doesn’t put up with liars.
  • For MacOS users, selecting the X icon in the toolbar will no longer keep the client hidden until a force quit.

New in GitKraken 4.2.2 (Feb 13, 2019)

  • Bug Fixes:
  • For those of you that didn’t appreciate Inception, we resolved an issue with duplicate repository names appearing in the breadcrumb list when a submodule had the same name as a recently opened repository.
  • What good is a Blame button when there’s nobody to blame? The History and Blame buttons will now only appear for appropriate files.
  • We all want to feel welcome, but Keif was getting a little carried away… Now, when opening a repository from the CLI using the -p argument, GitKraken will open the repository instead of the welcome screen.
  • The History and Blame buttons will no longer throw the error: “File path to get history is required.”
  • The error message “GitUrlParse.default.stringify is not a function” will no longer appear when cloning or pushing from a TFS instance.

New in GitKraken 4.2.1 (Feb 13, 2019)

  • Improvements:
  • For the 1 percenters, GitKraken now ships with a .rpm option for easy installation on CentOS, RHEL, or Fedora.
  • We nixed the 2 helpers who were sapping memory and system resources. You could call it, a clean bill of help.
  • Yes, we got up on the wrong hide of the bed. The keyboard shortcut to open history view has now been changed to Ctrl/Cmd + Shift + H to not interfere with the “Hide” option on MacOS.
  • Bug Fixes:
  • Now you don't have to be Sherlock Holmes; the error message for creating a branch that conflicts with a branch directory is now clearly s-p-e-l-l-e-d-o-u-t-f-o-r-y-o-u.
  • Windows users take a glass: the Edit on Bitbucket Server button should no longer take you to a 404 page.
  • For users who prefer to compile their OS, Linux users should now be able to open their terminal from GitKraken.
  • When you truly need to ESCape a situation, the Fuzzy Finder and Repository Management modals will now correctly close with the ESC key if no repository is open.
  • Nobody likes a blank image. Repositories under a private group on GitLab.com will have their avatars render as the GitLab logo instead of a blank image.
  • We get it. You don't like Tetris. Fine. Diffs for rebased commits will no longer display out of order.
  • It turns out, you do use this feature. Good to know: The Open with GitKraken context menu option on Windows should now open GitKraken instead of throwing an error message.
  • The blame & history buttons will no longer appear for untracked files. We don't know why you're not tracking these files in a tool designed for tracking, but who are we to judge?

New in GitKraken 4.2.0 (Feb 13, 2019)

  • Features:
  • Life’s a beach! GitKraken Pro users can now integrate their clients with Bitbucket Server to see a list of repositories that can be cloned and added. There are sunny days ahead for Bitbucket Server users because this integration enables you to open pull requests or initialize repositories from within GitKraken.
  • Error logging has been added into GitKraken. Users can access the error log from the Help Menu or the Fuzzy Finder. This error log will display the ten most recent error toasts that occured within the application. Let’s toast to that!
  • Improvements:
  • The VSTS integration has been renamed to Azure DevOps and now supports the new URL format (in addition to the older VSTS format).
  • You can now access File History and the Blame view from a file’s diff view.
  • A filter bar has been added to the right panel when View all files is selected.
  • Hovering over a merge commit will now display a tooltip with the commit author’s name.
  • Hovering over a stash will now display a tooltip with the full name.
  • Hovering over a repository, branch, or file name will display a tooltip with the full path and name.
  • When discarding changes to an individual file, the prompt will now display the file name.
  • The branch “ahead” and “behind” icons have been changed to improve visibility.
  • The pull request description field can now be expanded.
  • A filter has been added to the keyboard shortcuts window. This window can be accessed using Ctrl/Cmd + /.
  • Several keyboard shortcuts have been added:
  • Fetch (Ctrl/Cmd + L)
  • Create a Branch (Ctrl/Cmd + B)
  • Open File History in the Fuzzy Finder (Ctrl/Cmd + H)
  • Bug Fixes:
  • Initializing GitFlow on a repository with an existing local develop branch will no longer throw an error, Failed initializing Git Flow commit.id is not a function.
  • Lines that would connect reference labels to a commit should no longer appear in the graph if the reference label is hidden.
  • Launching a terminal from GitKraken will no longer set the NODE_ENV variable to production.

New in GitKraken 4.1.0 (Feb 13, 2019)

  • Features:
  • LumberKeif swiped right on GitHub, GitLab and VSTS (including Azure DevOps with legacy VSTS URLs) pull request templates.
  • Users can axe commit author gravatars and replace them with author initials. This setting is located under Preferences → UI Preferences.
  • Improvements:
  • Tree-mendous memory improvements!
  • Graph scrolling is smoother than a lumberjack on Timber.
  • The Preferences window takes less time to initially load.
  • Spruced up the Fuzzy Finder and added these options: Open File & View File. Both have the same behavior as the Fuzzy Finder option Edit File.
  • When cloning a repository via URL, GitKraken will now strip off any additional spaces at the beginning and end of the URL.
  • Bug Fixes:
  • For Linux users: Got to the root of the problem, and resolved an issue on some distributions that caused v4.0.6 to throw a libcrypto error.
  • Tooltips will no longer linger on the LFS dropdown. That was a real pine.
  • Removed the context menu option to favorite a repository in the branch breadcrumb menu.
  • Resolved an issue that caused duplicate pull requests to appear in the left panel due to having the same remote added with different casings.
  • Initializing a repository in GitKraken wood fail if you select a .gitignore template. It will no longer do that.
  • The Edit Submodule panel will now correctly update the remote URL when switching between submodules.

New in GitKraken 4.0.6 (Oct 16, 2018)

  • Bug Fixes:
  • GitKraken will no longer crash on Fedora 28 if a repository that has a SSH remote is opened or cloned.
  • Resolved an issue that caused the submodule sliding panel to be much more narrow than intended.
  • Users should now be able to correctly clear out the clone and initialize input fields.

New in GitKraken 4.0.5 (Sep 20, 2018)

  • Improvements:
  • Readded editor setting to change the font family. Changing this setting will alter the font in the Diff, File, History, & Blame Views.

New in GitKraken 4.0.4 (Sep 17, 2018)

  • Bug Fixes:
  • Temporarily removed editor setting to change the font family to prevent GitKraken from crashing for some users.

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 18, 2018)

  • Improvements:
  • When viewing a diff, users may now highlight lines to be staged, unstaged and discarded.
  • We changed the appearance of the Push and Pull icons. The new icons should no longer cause users' eyes to bleed.
  • Removed the Blame option for binary files.
  • Staging files quickly will no longer display a File contents are unchanged message.
  • Removed several actions from the Fuzzy Finder when no repository is open.
  • Bug Fixes:
  • The Stage all changes button should correctly appear after hitting the Mark all resolved button during a conflict.
  • An error toast will no longer appear after navigating to a commit from File History.
  • An error toast will no longer appear after switching to File View when viewing the diff of a submodule.
  • When creating a Feature, Hotfix, or Release branch in Git Flow, the text will now appear correctly in the input field.
  • After saving a file in the editor, the top toolbar will no longer flash like a strobe light.
  • The tooltip for hosting service icons, on the new landing page, will now correctly display the service's name instead of GitHub.

New in GitKraken 4.0.1 (Aug 14, 2018)

  • Bug Fixes:
  • "...a glitch in the Matrix. It happens when they change something." The edit profile modal has been cleaned up.
  • "Choice. The problem is choice." There will now be a default diff view mode selected.

New in GitKraken 4.0.0 (Aug 13, 2018)

  • Features:
  • Keif swallowed the red pill and woke up in the construct with some new abilities. Files can now be edited directly in GitKraken! The following features have also been added to file and diff views: Syntax highlighting, Word diffing, Ability to search within a file (Ctrl/Cmd + F when focused)
  • Déjà vu or did something change? File diffs can now be viewed inline or in Split view, in addition to Hunk view.
  • Do not try and bend the file. Realize the truth: there is no file. You can now create and delete files from within GitKraken. These options can be accessed through the context menu or from the Fuzzy Finder.
  • Improvements:
  • There might not be an operator watching your back, so GitKraken’s support documentation is now accessible through the Help menu.
  • Mastering the Fuzzy Finder can feel like becoming “The One”. The Fuzzy Finder can now be opened through the Help menu.
  • Free your mind from the graph clutter. Stashes now have the ability to be hidden from the graph view.
  • “Are you sure, Mr. Anderson?” A confirmation prompt has been added when deleting a stash.
  • What if I told you there was an all new way to manage your repos? Repositories can now be closed (Ctrl/Cmd + W), revealing a new view with quick links to open or start new projects.
  • It doesn’t take a visit to the Oracle to know that you’re ready to commit. Now, after staging all files through the keyboard shortcut (Ctrl/Cmd + Shift + S), the commit message box will be focused automatically.
  • Icons throughout GitKraken have been updated.
  • Bug Fixes:
  • A glitch in the Matrix, perhaps. Private groups on GitLab CE and EE will now have their remote avatars display correctly.
  • Like conquering a jump between buildings, GitLab projects with spaces in the name should not throw a 404 error after performing a pull or fetch in GitKraken.
  • “You’re empty.” “So are you.” After merging a branch, GitKraken will now correctly set the commit message box to be empty.
  • The commit panel is now able to dodge the long name or path of a file and will no longer get pushed off of the screen.
  • Commit Templates will now render correctly after staging and committing a file hunk.
  • Resolved an issue that caused GitKraken to throw an error when trying to view a deleted file with a missing parent folder.
  • Sometimes history needs to repeat itself, so we resolved an issue that prevented users from copying more than 67 lines of a file.
  • Enterprise:
  • Fixed an issue with Start TLS for LDAP authentication.
  • Resolved an issue that prevented users from registering through the Enterprise account site, when using built-in authentication.

New in GitKraken 3.6.6 (Jul 12, 2018)

  • Improvements:
  • Addresses the git vulnerabilities identified in CVE-2018-10887 and CVE-2018-10888.
  • Bug Fixes 🐛:
  • Windows users experiencing an Assertion Failed! error for git_revwalk_hide should no longer receive this error.

New in GitKraken 3.6.4 (Jun 19, 2018)

  • Improvements:
  • There are never too many places to add help instructions, so keyboard shortcuts are now accessible from the help menu.
  • Like a veteran camera man tracking a through ball, checking out a branch through the Fuzzy Finder will now scroll the branch into view. ⚽
  • GitLab.com users with private remote repositories will now display a placeholder icon instead of a blank box...a keeper, if you will.
  • Bug Fixes 🐛:
  • Hopefully we've fixed this one for good! Resolving merge conflicts on Windows should no longer result in the file getting CRLF line endings.
  • On Windows, selecting View all Files when viewing a commit diff should correctly display in Tree View. Or, if you're watching Mexico play, El Tri view. 🇲🇽
  • Two World Cups games at the same time: Awesome; Two scroll bars at the same time: terrible. Long commit messages will no longer have double scroll bars when viewing the diff of a file.
  • Can you imagine if two goals by the same player canceled each other out? A Pull Request with the same name as an existing Pull Request will now display, instead of appearing blank.
  • Accurate passing is key to any match. When opening a Pull Request in GitKraken, using Tab will now jump to the next field instead of selecting users or labels from the dropdown menu.
  • Pushing is grounds for a yellow card, so repositories with long names will no longer overflow in the repository bread-crumb menu.
  • Enterprise:
  • Like a super sub fresh off the bench, Enterprise clients that are launched in an offline environment should load significantly faster.🏃

New in GitKraken 3.6.3 (Jun 1, 2018)

  • This release addresses the git vulnerability that was recently identified in CVE-2018-11235.

New in GitKraken 3.6.2 (May 30, 2018)

  • Bug Fixes 🐛:
  • Hashtags are not just a commenting device: lesson learned. Commit messages with a # will now only be commented out if the new comment option is enabled in your Preferences > Commit Template settings.
  • Discarding or resetting an untracked or renamed file will no longer throw an error, especially since the action completes successfully.

New in GitKraken 3.6.1 (May 16, 2018)

  • Improvements:
  • You may now disable spell check from Preferences > UI Preferences, and of course tell everyone about your spelling bee championship at Lincoln Elementary.
  • Bug Fixes 🐛:
  • If you installed the Linux .deb package recently, you may have noticed that GitKraken was not installed into your system path. We fixed that by pointing Keif back to the proper location.
  • Enterprise:
  • We popped the hood and made a change that allow more memory allocatation when syncing with large LDAP environments.

New in GitKraken 3.6.0 (May 1, 2018)

  • 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.
  • FEATURES:
  • 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.
  • Mission Control, we are a go for total pull request management.

New in GitKraken 3.5.1 (Apr 7, 2018)

  • Bug Fixes 🐛:
  • GitKraken should now be able to connect to GitLab self-hosted servers with self-signed certificates, again.

New in GitKraken 3.5.0 (Mar 28, 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)

  • Bug Fixes:
  • GitKraken should no longer throw the following error when fetching pull requests from VSTS: Fetching pull requests failed. A project name is required in order to reference a git repository by name.

New in GitKraken 3.4.0 (Mar 8, 2018)

  • Features:
  • From the depths, a magical window has opened! GitKraken now integrates with Visual Studio Team Services (VSTS)! 🎉 GitKraken Pro feature - Upgrade now to access!
  • Improvements:
  • We like to Add/Remove Programs, too, so GitKraken now supports Araxis and P4Merge as external diff/merge tools.
  • For the hover explorers out there, a tooltip has been added to the green check mark in the left panel.
  • Bug Fixes 🐛:
  • Integration help links will now send you to the correct support page instead of a 404 page...and it wasn’t even the fun 404 page; our apologies!
  • Resolved an issue that prevented GitKraken from opening repositories that had a tag named X. You probably figured it was the ‘X’ tag in your repo, huh?
  • Toss those unwanted hunks out the window with confidence! Discarding hunks on Windows will no longer add LF line endings to a file with CRLF endings.
  • Enterprise:
  • Beta Feature: GitKraken Enterprise can now be configured to use LDAP as an alternative authentication method. 👏

New in GitKraken 3.3.4 (Jan 30, 2018)

  • Improvements:
  • When discarding a single file through the context menu, you’ll now see a confirmation prompt: also known as the ohnoididntmeantoclickthat prompt.

New in GitKraken 3.3.3 (Jan 23, 2018)

  • Features:
  • Keif’s New Year’s resolution was to be less secretive. So, hovering over a repository in the breadcrumb menu will now display a tooltip with the repository’s full path. 📁
  • Improvements:
  • After some year-end reflection, Keif decided that when staging or unstaging from a list of files, GitKraken will now select the next item in the list instead of selecting the first file in the list. 🎉
  • Bug Fixes 🐛:
  • The feedback and support forms should no longer feel laggy when writing in the subject field… We do want your feedback, we promise!
  • Scrolling through the Fuzzy Finder with your mouse wheel should now work as intended and not—you know—erase the results and act all weird.
  • Making changes requires commit-ment, so we resolved an issue that prevented some users from entering a commit message after popping a stash.
  • After staging, unstaging, or discarding all hunks and lines for a given file, GitKraken will no longer get stuck on a loading icon when trying to display the next diff. New year, new kraken! Keif will move on. 👏
  • To make a change, you need to start from the beginning. So when editing a submodule’s URL, the cursor will no longer jump to the end of the URL.
  • Wiki repos on GitLab are special. We know this now, and GitKraken will no longer display a “Fetching pull requests failed” toast when performing a fetch on a GitLab self-hosted Wiki repository.

New in GitKraken 3.3.2 (Dec 15, 2017)

  • Bug Fixes:
  • Users running Git hooks on OSX High Sierra may now commit. We've figured out our commitment issues

New in GitKraken 3.3.1 (Dec 7, 2017)

  • Features:
  • Lost in a holidaze of commits? There's now a Fuzzy Finder shortcut to view working directory changes.🔍
  • Improvements:
  • For our ambitious GitLab integration users with more than 100 repositories, you should now be able to see all repositories.💯
  • Feature/cantremember? When creating a branch or tag, GitKraken will now leave the input field open if you navigate to a different window.
  • We removed some of the...grey areas (sigh) by replacing the greyed-out placeholder text with actual placeholder text in the Clone and Init repository windows.
  • We know everyone loves a cryptic error message, but they are now more descriptive when trying to initialize a repository on GitLab Enterprise. Sorry not sorry.
  • Bug Fixes:
  • We realized you need more than one character for a commit message, so GitKraken now allows users to write a full commit message after undoing a commit.
  • When fetching from a GitLab repository, with merge requests disabled, an error message would appear saying it could not load your merge requests… GitKraken now understands this is the same as informing someone that something divided by 1 is itself.
  • GitKraken will now properly cache group information for GitLab instead of constantly pestering the server about the same groups.
  • Notes:
  • Remotes on GitLab self-hosted accounts will now display the GitLab icon instead of the associated remote avatar. Trust us, it's better this way.

New in GitKraken 3.3.0 (Nov 28, 2017)

  • Features:
  • GitKraken now integrates with GitLab Community Edition and Enterprise Edition (Pro users only). 🎉
  • Improvements:
  • When renaming a branch, the current branch name will now pre-populate the input field.
  • We’ve added a context menu option to copy a file’s full path from the commit panel.
  • Hovering over a user’s gravatar in the graph will now display a tooltip with that user’s name (or email if no name is provided).
  • A loading icon has been added to the clone repository window; it displays while GitKraken is retrieving your remote repositories.
  • Bug Fixes:
  • New connections to GitHub Enterprise no longer require GitKraken to restart.
  • Pull requests on GitHub.com with multiple assignees will now show all assignees in the tooltip and consistently display in bold when you are one of the assignees. (Previously, it would only bold if you were the first assignee.)
  • Users will no longer be prevented from discarding changes for a removed file.
  • In tree view, the commit panel should now properly display which files have been added/modified/removed/renamed while navigating through the graph.
  • Enterprise:
  • v3.3.0 does not include any changes to GitKraken Enterprise other than those listed above.

New in GitKraken 3.2.2 (Nov 21, 2017)

  • Features:
  • Got GitLab.com? Now you may create a pull request and add a remote from GitKraken.
  • Improvements:
  • The currently opened repository is part of the repository management window.
  • Esc will close the Gitflow and pull request panels.
  • Attempting to delete a primary remote branch now creates a specific error message.
  • Bug Fixes:
  • Cloning and working with a LFS repository on Linux via SSH works now.

New in GitKraken 3.2.1 (Oct 31, 2017)

  • Fixed a bug in analytics that caused certain clients to over-report analytics data.

New in GitKraken 3.2.0 (Oct 28, 2017)

  • Features:
  • If you have children, it’s usually a bad idea to have a favorite child. With GitKraken, it is totally fine to have a favorite repository, and thus we introduce you to the new Favorites list!
  • Multi-select for discarding changes: like multi-select for Staging and Unstaging, but with Discard. 🗑️ We’ve added a context menu, too, so now you may discard all changes within a folder if you are in tree view. Brought to you by popular demand- we know how much you love multi-select!
  • Improvements:
  • We’ve added a context menu option for updating submodules.
  • Now use Ctrl+D(Windows/Linux)/Cmd+D(Mac) or the Fuzzy Finder to open your configured external diff/merge tool.
  • Bug Fixes:
  • GitKraken no longer displays a Pushed Successfully message if a push fails due to a server hook. In other words, force-pushing to a protected branch will now display an error message instead of a false “success” message.
  • We resolved an issue that would cause GitKraken to launch outside of your window region. Sorry about that, it won’t happen again. 💐
  • Hitting the cancel button when trying to finish a Gitflow action (Hotfix, Release, or Feature) now properly closes the Gitflow window (instead of doing nothing).
  • Discard all now discards submodule changes, too.
  • GitKraken now correctly applies the operating system’s newline character when modifying a repository’s .gitignore file.
  • Enterprise:
  • v3.2 does not include any changes to GitKraken Enterprise other than those listed above.

New in GitKraken 3.1.2 (Oct 17, 2017)

  • Features:
  • Context menu option added: copy your selection when in File View. For those of you who cleverly tried to use Ctrl+C(Windows + Linux)/Cmd+C(Mac), you will no longer get line numbers when pasting the file contents. 👏
  • Improvements:
  • You can now initialize a repo with LFS and access the LFS configuration menu through the Fuzzy Finder.
  • We’ve added small loading icons when Staging/Unstaging a file.
  • Bug Fixes 🐛:
  • Esc will once again close the preference menu. 🎉
  • Drag and drop actions, as well as selecting text in the output panel of the merge conflict editor, are now more accurate when zooming above or below 100%.
  • So long useless error messages: staging a file directory change, an additional change to an untracked file, or a renamed file no longer throws a meaningless error message. 👋🏼
  • Fixed an issue which prevented filemode changes from being discarded if the change was still unstaged.
  • Resolved an issue that prevented changes from being committed to a submodule that had post-commit hooks.
  • The Git Config Default setting for external merge and diff tools now works with tools whose absolute paths contain spaces. Welcome, space! 🌌
  • Enterprise:
  • From this release forward, any changes to GitKraken Enterprise will be noted here. v3.1.2 does not include any changes to GK Enterprise other than those listed above… but stay tuned! 🎆

New in GitKraken 3.1.1 (Oct 10, 2017)

  • Fixed:
  • GitKraken would consume CPU like a ravenous sea monster 🌊 . This should be improved with this fix.
  • Addressed hanging or locking up with actions such as checkout and viewing a diff.
  • Discard hunk will no longer unintentionally delete the entire file (instead of just the hunk).

New in GitKraken 3.1.0 (Oct 4, 2017)

  • FEATURES:
  • 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.
  • 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.
  • 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.
  • IMPROVEMENTS:
  • This makeover came with new and improved easy-to-see scrollbars!
  • 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:
  • 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)

  • Fixed:
  • GitKraken will correctly generate 2048-bit SSH keys (issue caused GitKraken to generate 1024-bit keys).
  • Git hooks will no longer fail if the path they are on contains spaces.

New in GitKraken 3.0.1 (Sep 19, 2017)

  • Fixed:
  • GitKraken previously only supported Git LFS up to a file size limit of 250 MB/file. The issue has been addressed and you may now use larger files (up to Git LFS's limit of 2 GB).

New in GitKraken 3.0.0 (Sep 7, 2017)

  • FEATURES:
  • Super size those files: Git LFS support has arrived! 🎉
  • You can now select multiple files faster than going through the drive-thru! Simply use Shift or Control/CMD to multi-select files to perform any of the following actions:
  • Context menus
  • Stage
  • Unstage
  • Ignore
  • IMPROVEMENTS:
  • The right panel was looking a little beefy under the hood, so we slimmed it down a quarter pound and optimized the following:
  • File Tree view navigation with arrow keys
  • Scrolling through the file list
  • BUG FIXES:
  • Repository deletion should provide an error message if there is a file lock(s) preventing deletion.

New in GitKraken 2.7.0 (Jul 18, 2017)

  • IMPROVEMENTS:
  • Some prefer tabs, some prefer spaces, but at least now you can configure how many spaces should render for tabs in diff view.
  • A quick right-click will now give you the option to delete repos from the repository management panel.
  • Local branches can now be renamed—because we all make tpyos.
  • We heard your requests for more feedback with blank diffs:
  • A filemode change will now let you know that the contents have not changed.
  • A whitespace change when "Ignore Whitespace” is checked, will give you a heads up that you need to uncheck it.
  • A binary file change will tell you that GitKraken can’t display those.
  • Go-go gadget Fuzzy Finder is even more efficient. If you haven’t started using the Fuzzy Finder yet, now is the time:
  • Start a pull request or create a tag.
  • Access the Git flow panel.
  • “Search Commits” will take you back to the graph to view your selection, if the graph wasn’t visible prior to your search.
  • Wowsers! Git hooks are better too:
  • The pre-commit Git hook can now modify the files of the same commit it’s running.
  • Git hooks that have control characters (like ANSI escape codes) are rendered correctly when their logs are displayed on failure.
  • On Windows, you can now browse for your sh.exe file for Git hooks. GitKraken will verify the path too!
  • BUG FIXES:
  • GitKraken used to crash when trying to parse empty reflog messages; sorry about that chief, it’s fixed.
  • We trust that you read the EULA, so you can close that modal now without having to refresh GitKraken.
  • Merge conflict resolution on Windows no longer adds extra empty lines. Resolve conflicts with confidence again!
  • When the Clone Repo form is submitted, its input is cleared.
  • Command/Ctrl+P now clears the Fuzzy Finder, ah efficiency.
  • You’ll no longer get an error when you "Unstage All” from the Fuzzy Finder when there is no WIP node.

New in GitKraken 2.6.0 (Jul 18, 2017)

  • IMPROVEMENTS:
  • GitKraken will now inform you with a scarlet message when an external rebase is running. Once the rebase finishes, it will literally release the kraken.
  • Did you know Watson prefers Mac? He was adamant about changing the title bar colour, and fellow Mac users will hopefully be delighted in his tastes.
  • The new and improved Fuzzy Finder combines the Command Palette and the Fuzzy Finder all into one keyboard shortcut ⌘ | CtrlP which allows you to:
  • Push, pull, or manage account
  • Open, clone, or initialize a repo
  • Search through blame, history, commits, and more
  • BUG FIXES:
  • The loading spinners next to the remote names during a fetch had mysteriously vanished, but some well placed clues allowed us to track them down and return them to their rightful homes.
  • Longer submodule names now correctly align in the left panel. 🎉
  • The sight of a submodule caused the breadcrumb to lose its styling, a quick lesson in mindfulness has rectified the issue.
  • A user’s identity is no longer masked when logging in via OAuth and switching between a Free account and a Pro account.
  • Sir Arthur Conan Doyle can rest easy, Commit Changes to 1 Files message is now correctly pluralized (i.e. Commit Changes to 1 File).
  • If a Gitflow feature with conflicts is finished, there is no longer an extraneous No such file MERGE_MSG toast.
  • When merging with Gitflow, messages would look like Merge branch 'undefined' into undefined. After some words of encouragement, it works correctly.
  • The HEAD commit no longer has cherrypick as an option in the context menu.
  • If no HTTPS credentials were being stored, GitKraken still allowed users to Forget All credentials in Preferences. The constables did not like that, so we threw them a bone.
  • If a PR fetch failed, the error toast said repostory when it should have said repository. Cheers to our users for sniffing that out.
  • Commit messages passed to Git Hooks during a non-conflicted merge were missing newlines. They have been found, thankfully.

New in GitKraken 2.5.0 (Jul 18, 2017)

  • Speed/Performance Enhancements:
  • (All OSs) Checkout speeds improved across the board.
  • (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.
  • 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:
  • The command palette was not always showing every option it was supposed to show. It now shows everything it should.
  • Right-clicking a checked out commit no longer shows the cherry-pick option.
  • “Ignore whitespace” has sometimes worked, sometimes not, and fluctuated between the two states. It now super works.
  • 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 could crash GitKraken. That’s a bug and we have fixed it, with apologies.
  • Fixed an issue where double-clicking a ref inside 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.
  • When performing a checkout, sometimes the breadcrumb in the tool bar has a spinner next to the branch that never goes away, it does now!
  • If a submodule exists on branch B but not on branch A, switching from branch A to branch B now checks out the submodule.

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 19, 2017)

  • Fixed:
  • Fixes a frequent refresh issue when the system is completely idle.
  • If prepare-commit-msg failed during a conflicted merge, cherrypick, or revert, the pending commit message displayed in GitKraken would be cleared instead of persisting like it oughta. It behaves properly now.
  • Improved:
  • Created a fun new game called "How Soon Can We Release 2.3.4?" (Price is Right rules).

New in GitKraken 2.3.2 (Apr 6, 2017)

  • Fixed:
  • When creating a commit, the prepare-commit-msg hook looks at .git/COMMIT_EDITMSG. Nothing wrong with that, right? Correct, but there was a problem: that file wasn't being populated with data before the hook was fired, and whatever prepare-commit-msg did to .git/COMMIT_EDITMSG was being ignored. That is now fixed. Sorry!
  • Improved:
  • THREE releases in one week! Lucky you!

New in GitKraken 2.3.1 (Apr 6, 2017)

  • Fixed:
  • If you managed to download 2.3.0, you almost certainly experienced sign-in issues. This release fixes the issue. Sorry about that.
  • Improved:
  • The amount of time between a major release and the need for a hotfix release has been reduced significantly.

New in GitKraken 2.3.0 (Apr 6, 2017)

  • New Features:
  • Git hooks! One thing that has prevented some users and teams from being able to adopt GitKraken is the lack of Git hooks support. Until today! You can now create custom scripts that fire off at certain points during Git processes. GitKraken does not require that you install Git on your system, so until now, that independence had meant no Git hooks support. But, with a lot of blood, sweat and tears, v2.3 allows you to hook your way to a bounty of control over your Git actions! For more information and a complete list of the hooks supported by GitKraken, check out the Git hooks page on GitKraken's support site.
  • Localized dates on commits:
  • Morrissey once wrote:
  • When you say it's gonna happen "now"
  • Well when exactly do you mean?
  • See I've already waited too long
  • And all my hope is gone
  • I don’t think it’s too dramatic to say that this is how many of you felt, trapped inside an USA date format. It was unacceptable that users might not know how soon “now” is, was, or could be.. GitKraken now updates the date format based on your system locale, so you can view your dates in a sensical manner, because you are human and you need to be loved, just like everybody else does.
  • User onboarding: When we drop you into a new utopian land of wonder and beauty, you should probably still know where the restrooms are. With v2.3, we have implemented a rather pleasant onboarding experience for those who need a little help getting to know their way around. This onboarding process includes links to our support site intro video and Slack community.
  • Look at you with all your branches pointing to the same commit! Good news: The ref labels that describe branches and tags on the left side of the graph have been redesigned to more clearly display multiple branches pointing to the same commit, and generally improve readability. Those collapsed groups of labels now expand into a vertical list when hovered instead of the difficult-to-read horizontal row. You can also drag-and-drop labels between expanded lists to merge, rebase, reset, etc. with ease.
  • Improved:
  • Having trouble seeing which branch is checked out? We added a check icon to the label of the branch you’ve got ‘checked’ out. Checked. Get it? Punny!
  • If you're hiding a remote, we're collapsing the remote. That's our promise to you. Don't worry, you can still expand it back out after you unhide it.
  • If you collapse a folder that contains the currently-checked-out branch, that'll be highlighted to show you it contains that checked-out branch.
  • Pull requests can now be checked out from the left panel.
  • In the repo management view, you can now right-click on a project group and there’s an option to open that folder in your OS's file manager.
  • In the repo management view, the Recently Opened list no longer shows the currently open repo. Yes, it is the most recently-opened repo. But it's still open, see? It just doesn't help having it in the list. Don't you agree?
  • If you have project groups, you might notice that GitKraken finds your repos faster. That’s because GitKraken is finding them faster!
  • Fixed:
  • When viewing a commit in the right panel, reversing the sort order would initiate 'Opposite Day' for your keyboard where up is down, and down is up. Fun for the keyboard, less so for the user. Order is now restored!
  • For some users, adding submodules wouldn't work. For those same users, adding submodules should now work. Classic bugfix scenario.
  • There is a GitLab issue that was affecting GitKraken when trying to push via HTTPS with an OAuth token. We've made a workaround for this until the GitLab issue is resolved.
  • Viewing diffs in Kaleidoscope for MacOS stopped working–not ideal for a file-comparison app. It works again now, sorry.
  • GitKraken now respects the CRLF/LF line endings already being used in a file, rather than enforcing one.
  • With autofetch turned off, the pull request section message in the left panel doesn’t get cut off anymore.

New in GitKraken 2.2.1 (Mar 23, 2017)

  • Fixed:
  • In 2.2.0, we added support for authenticated proxies, but in doing so, we actually broke proxy support for some users. In what might be today's most obvious statement: this is the one thing we didn't want to happen. We have now unbroken this support, and also implemented wider proxy support than was available in 2.2.0. So, if you could use proxies before 2.2.0, but couldn't use proxies after 2.2.0, you should now be able to use proxies again like you could before 2.2.0. If you could never use proxies, there's a chance you can now. Simple? Simple.
  • Sorry, we're not done with proxy support. If you couldn't use proxies, and still can't use proxies, we've made it easier for some straightforward configuration tweaks to get you up and running. Due to the complex nature and diversity of Git setups, we can't get exhaustive with this, but for an overview, check out our FAQ on possible workarounds.
  • If you used the left panel to perform an action on a stash, this action would be applied to the newest stash. Like, every time, no matter what stash you were actually trying to modify. Sorry for that unpredictable behavior–it's been fixed.

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 14, 2017)

  • New Features:
  • Remote avatars: When multiple remotes were displayed on the same ref label, it would get hard to differentiate between them. In short, they were looking California and feeling Minnesota. Now each remote has its owner's avatar attached to it so you can clearly see the difference at a glance, even if you're searching with your good eye closed.
  • New remotes compatibility! Remotes on TFS 2015, TFS 2017, and VSTS that use HTTPS are now working.
  • You can now use GitKraken on computers behind non-authenticated proxies!
  • We've made significant performance improvements to the left panel. Especially with larger repos, you should notice snappier performance.
  • Bug Fixes:
  • Repos with a large number of tags should be faster now.
  • The graph and the left panel were exhausting themselves by refreshing every time you blurred and then refocused the app, causing lag. Both the graph and the left panel have decided to chill and only refresh when absolutely necessary, meaning no more lag.
  • Scrolling to commits that are more than 2 rows outside the current view now puts them in the middle of the screen. Deleting a reference would sometimes seize up the process. You're busy, you don't have time for that. Tomfoolery begone!
  • Emojis are displayed on the graph again 🍆
  • Selecting multiple commits once again shows the author information for those commits.
  • We swapped the candy cane progress bars for the eye candy known as "Spinny Keif."
  • Showing a diff between 2 branches would sometimes do the precise opposite by showing nothing, because the app would crash. This is contrary to intentions and has been fixed.
  • You didn’t want two commits with identical timestamps to break the app. We get it. We fixed that. But maybe you're just too demanding, maybe you're just like my mother (she's never satisfied), why did we let this bug happen? This is what it sounds like, when devs cry.

New in GitKraken 2.0.1 (Jan 26, 2017)

  • Fixed:
  • We understand that you need to open submodules, and now we are sure that you can, sorry!
  • Editing a submodule: This is a weird, weird thing that happened. So, here's the thing. If your submodule is in an OK state, editing that submodule would break the app. Now, it doesn't, which means we fixed it, and we are sorry it didn't work.
  • Setting upstream on a ref with a . in the name wouldn't work. . hardly seems like a far out there character to include in an upstream so we fixed that right up for you.

New in GitKraken 2.0.0 (Jan 26, 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:
  • 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.
  • .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
  • 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 improvements:
  • 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.3 (Dec 28, 2016)

  • Fixed:
  • The 1.9.2 update broke fetching, pushing and pulling when connecting to hosts without GitKraken integration (GitLab, etc). This should now be working as expected.

New in GitKraken 1.9.2 (Dec 28, 2016)

  • Fixed:
  • The context menu for stashes took an unexpected sabbatical in 1.9.1, but now it’s back and better than ever!
  • Some users have been harassed by a persistent message, telling them that their Bitbucket tokens “need more permissions.” It’ll no longer pester you, promise.
  • The GitKraken Store was stubbornly caching data. We’ve cleaned that up, because if we add a comma somewhere, you deserve to see that comma right away!

New in GitKraken 1.9.1 (Dec 28, 2016)

  • Fixed:
  • Uh oh. GitKraken would spring a memory leak for some users when the commit list was updated, negatively affecting performance, hogging system memory and raining on the performance parade in general. We prioritized fixing that issue, sorry.
  • Avast me hearties! If ye be sailing these SSH high seas, in some cases, the port number would disappear from your URI (U R AYE!). Arr, we’d be a bunch of scallywags if we didn’t fix that, so we’ve made that bug walk the plank into shark infested waters! Arrrr. It be smooth sailing through your ports now, scoundrels.
  • Did we mention the memory thing already? Something about a leak. Can’t remember.

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.1 (Oct 25, 2016)

  • Fixed:
  • There was some lag when typing in the commit message input field, but it now keeps up with the fracking pace, thank the Gods.
  • The graph no longer renders while a repo is being opened, which makes the process a bit faster and less distracting.
  • Pushes would sometimes fail with a Cannot read property ‘cancelled’ of undefined message. That was obstructive, unhelpfully ambiguous and a bit of a negative nelly kind of message. So depressing! So fixed!
  • If you tried to focus the left panel filter when the left panel was hidden, it would unleash a whole world of nope where you’d not be able to refocus it. It now behaves as expected, sorry.

New in GitKraken 1.8.0 (Oct 18, 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)

  • BUGFIX RELEASE:
  • Fixed:
  • We stopped the WIP text field from repopulating itself after a commit was made. That was pretty, pretty annoying, wasn’t it.

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. There’s also a little more info available here.
  • Given that this overhaul does so much under the hood, we would be inclined to say “it’s fast, now move on, nothing to see here.” But there is actually plenty to see, because while we were in there with our construction vehicles and hard hats, we also dusted off our pencils, pens and paintbrushes and made a bunch of UI and UX improvements.
  • 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:
  • Mac only: Looks like the Undo/Redo/Cut commands were missing from the Edit menu. Fine, whatevs, you can have those back.
  • 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)

  • Fixed:
  • Some users were getting errors trying to open all repositories. That was not a feature; it was a bug we’ve now squashed.
  • Remember all the way back in v1.5.2 when we fixed that issue with repeated logins? We’ve improved our fix for that, ensuring that you will super-never-be-asked-repeatedly to log in.
  • That’s all! Not too exciting, but we’re always trying to improve stability as we go. If you’d like to read more, in the spirit of generic bugfix release notes, here’s some filler:
  • We update the app regularly so we can make it better for you. Get the latest version for all of the available features and improvements. Thanks for using GitKraken!
  • Minor text fixes.

New in GitKraken 1.6.0 (Sep 13, 2016)

  • New:
  • Login with your GitHub account! This is a huge improvement for the activation process of GitKraken, meaning you no longer have to set up a separate account to use the app. Instead, it's just a two-step process to get yourself up and running using your GitHub account.
  • OAuth I love you
  • You and your quicker process
  • To use GitKraken
  • New fuzzy command: In the fuzzy finder, you can now "open repo in explorer" to go directly to your repo in your OS file system.
  • Fixed:
  • We fixed some pretty gnarly file behavior. When you delete files and then create a branch, those files would just come right back and sit there smugly. In addition, renaming files and then creating a branch would not only keep the previously-named files, but add new files with the new names. Precisely what you didn't want. It's fixed, promise.
  • When browsing for SSH keys on a Mac, GitKraken now sees all, showing hidden files regardless of your Finder settings.
  • If you tried to add a new remote or clone a repo from GitHub/BitBucket, GitKraken would default to using SSH even if that wasn’t set up. We weren't trying to convince you one way or the other, and recognize that you are your own person, with your own ideas, feelings and preferences. We have fixed this issue to reflect that.
  • Improved:
  • In-app support form Pro Feature
  • We added a "get support" form for Pro users to request support. You'll find it through the feedback button at the bottom of GitKraken, or through the application menu under Help.

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.
  • Improved:
  • 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)

  • Fixed an issue where, if a stash was applied that resulted in a merge conflict, the graph wouldn’t update.
  • Sometimes, popping a stash wouldn’t put work directory updates into the graph, and that would make it look like the stash had been deleted. Which was, frankly, terrifying. And unacceptable. We’ve fixed it.
  • Auto-selection of WIP node works where it was not working before.
  • Fixed a graph issue where creating a branch would make it look like the previously checked out branch is still checked out. Ooh, that naughty graph. Do behave.
  • In some cases, switching to a different repo while viewing a new merge conflict would cause GitKraken to get freaky and create its own bizarro reality. This was not destructive behavior, but we imagine it was really, really confusing and annoying to affected users. We’re sorry for the inconvenience and we have fixed the issue.

New in GitKraken 1.5.2 (Aug 5, 2016)

  • Fixed:
  • Commit Summary input field is no longer broken in Japanese input mode. ごめんなさい!
  • Speaking of the Commit Summary field: it no longer jiggles and jives like your drunk uncle at a wedding. We’re sorry that ever happened, but at least it never talked politics.
  • The tutorial would sometimes cut off during upgrade, but it doesn’t anymore.
  • We’ve addressed an issue where users might be prompted unnecessarily for login.
  • Linux now shows the correct package version.
  • Some users were finding that focusing the GitKraken window would take them on a long, tedious journey where the currently open repo would continually re-open, fail, and then try to re-open, ad infinitum. This should no longer happen.
  • Fixed an issue where dragging a branch on the graph would not show a hover image.
  • Fixed an issue where Bitbucket SSH key management could get stuck in a bad state.
  • Fixed at least some of the whitescreening that certain users were experiencing.

New in GitKraken 1.5.1 (Jul 29, 2016)

  • Fixed:
  • For some OS X users, our update button got stagefright and would disappear. This update reveals a new, confident update button that always appears when it’s needed.

New in GitKraken 1.5.0 (Jul 28, 2016)

  • INTRODUCING GITKRAKEN PRO: YOUR PROFESSIONAL FANCYKRAKEN:
  • 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 (https://www.gitkraken.com/pro). To learn more about the story behind monetizing the app, check out our blog post (https://blog.axosoft.com/2016/07/28/introducing-gitkraken-pro/).
  • 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!

New in GitKraken 1.4.1 (Jun 3, 2016)

  • Bug fix release:
  • GitKraken in OS X has learned a valuable lesson, and we are sorry for its recent behavior: “I will not open multiple windows when you focus my window”.

New in GitKraken 1.4.0 (Jun 1, 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.
  • 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.
  • 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.
  • 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:
  • We reduced the sizes of our download files by 30-50%, saving you disk space and Making the World a Better Place.
  • 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.

New in GitKraken 1.3.0 (May 10, 2016)

  • NEW:
  • 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.)
  • 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.
  • 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.
  • 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.
  • 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 25, 2016)

  • NWW:
  • That’s right! Now you can compare merge conflicts side-by-side, and resolve the conflict without ever leaving GitKraken. This feature is a huge, HUGE step for the app and for its users, so here are the highlights:
  • The obvious: compare text files side-by-side.
  • Click one version’s button (A only or B only) to select that version.
  • Compare the usual text files, image files, and select which versions of binary files to take.
  • Take elements of each file using a handy checkbox for each conflict in each file. You can take all changes in a file, or select specific hunks or lines from each file.
  • Next and previous buttons help you quickly find the next and, umm, previous conflicts in the file without having to scroll your life away.
  • Look, we’re not in the business of telling you what to do. If you’d rather use your own merge tool, you can click the Open in merge tool button and handle things there. GitKraken will leave a light on for you when you return.
  • The merge tool feature gets at the heart of GitKraken’s principle to minimize unnecessary interactions and do away with dependencies. We put a lot of effort into it, and we hope you love it.
  • You can now create a new repo on your GitHub/Bitbucket account directly from within GitKraken. Yep, we’re pretty keen on keeping you in the app with this version.
  • FIXED:
  • When viewing file diffs, graph scrolling sometimes got weird. We’ve made it behave normally.
  • The graph would always scroll HEAD into view when the user was in a detached HEAD state. This sounds more gruesome than it was, but it was annoying and we’ve fixed it.

New in GitKraken 1.1.0 (Apr 13, 2016)

  • NEW:
  • Fuzzy finder: A new and faster way to interact with GitKraken's most-used processes! Less clicking around to find stuff == more productive!
  • And, because it’s fuzzy, you don’t need to be 100% accurate in your commands (you don’t even need to type the command but it helps narrow down the options). The Kraken will guess what you are trying to do and offer useful suggestions in a contextual dropdown (think Atom’s fuzzy finder rather than Microsoft’s Clippy).
  • Stashes are easier to manage now that they have their own section in the left panel. Quickly pop or delete them from one location.
  • cmd + P on Mac / ctrl + P on Windows & Linux opens a new text field, in which you can begin typing a command followed by a name:
  • open + {repo name}: open a repo
  • checkout + {branch name}: checkout a branch
  • history + {filename}: view a file’s history
  • FIXED:
  • Lots of bugs have been fixed. Sorry we couldn’t make this statement more exciting, but hopefully any bugs you have been experiencing are no more.

New in GitKraken 1.0.0 (Mar 29, 2016)

  • Fixed:
  • Occasionally, when resetting diffs in GitKraken (if you have a new file in your working directory), you’d receive an error message about updating diffs for a file that does not exist. This very message was an error, making the whole experience a meta nightmare that we have now resolved.
  • Blame view: if you renamed a file, the blame would show “unknown” under the previous name. We were to blame for this, and we have now branched the naming so that you can follow name histories and point the finger at your 👉 fellow devs 👈 once more.
  • 775b3d237e52df5b11e1f3f346b13fc7dbd80e39. Oh, you can’t read SHA hashes? We’ve updated submodule conflicts to make sense to human beings with more conflict info.
  • Up-to-date merge fails silently. No more silent screams when you drag and drop to merge up-to-date. 😱
  • White screening: When you launch GitKraken, it should do something other than nothing. We’ve worked our tentacles to the bone to ensure that white screens of death do not happen on as many platforms and in as many configurations as possible.

New in GitKraken 0.9.2 Beta (Mar 20, 2016)

  • Fixed: Got rid of the constant white-screening while opening a repo that some of you guys were experiencing.

New in GitKraken 0.9.0 Beta (Mar 17, 2016)

  • New:
  • We heard you and Submodules are now supported! Say hello to the new section in the left ref panel to initialize an existing submodule or add one to track. Let the GitKraken Submodule-ception begin. 💻 🐙 💭 💻 🐙
  • Improved:
  • Welcome Resizable Graph, a valuable addition on the interface side! Drag the vertical bar to obtain precisely how much of the graph you want to see. This also allows you to have a completely collapsed and minified graph at will!
  • New buttons for Mark Resolved, Mark Conflicted, and Open Merge Tool for improvements in the Merge Conflict panel to get you in the flow and resolving conflicts faster and more efficiently
  • The Amend commit message button looked bad at one point and should not look bad. We adjusted the style to give our seal of quality
  • In File View, the styling of the preview when hovering over commit in condensed graph has been updated to be up to spec including font and colors
  • Fixed:
  • With the new resizable graph, now getting two honorable mentions here, when there are a large number of branches on the repository we have the ability to show an accurate graph and you can always control how much you want to see
  • Failing on open merge tool? Not anymore it's not. We made some changes when the merge tool is not found and when there is no common ancestor of the commits
  • The merge conflict panel will open accordingly when applying a stash which conflicts with changes
  • We'll present a message when there are failures on remote actions
  • The client will not crash when there are unicode characters in the file path name of the repository to be opened
  • Fixed a small leak with fetching from prolonged use 🚱

New in GitKraken 0.8.3 Beta (Mar 15, 2016)

  • White screen on repo open fix:
  • Fixed an error that some people were seeing the app white screen after opening a repo.

New in GitKraken 0.8.2 Beta (Mar 15, 2016)

  • Bitbucket fix:
  • Fixed an error that would break fetching/pushing with Bitbucket

New in GitKraken 0.8.1 Beta (Mar 4, 2016)

  • New:
  • Level 🆙 Search Index grew to Level 2! You've learned a new skill Search by Field. Use one or combination of:
  • sha: full hash of commit
  • message: commit message description
  • author: author of changes
  • email: email of author
  • Improved:
  • OAuth will now properly flow through your external browser and communicate on authorization success or failure
  • Also in Authentication, relevant configuration for SSH will only be shown when Use local SSH Agent is disabled
  • Make a best effort to set defaults on creating a new pull request if unable to authenticate when fetching the origin
  • The order of colors has been updated in the graph for a more optimized contrast resulting in a prime exhibition of the work you've done. The colors of the rainbow so pretty in the sky 🎵
  • Fixed:
  • Successfully loading mergetools to resolve merge conflicts. Common locations on mac for mergetool defaults will be located accordingly
  • Perform a revert on a merge commit rather than producing an error
  • We won't allow spaces when naming a branch
  • Present a nice error message and refresh the graph if there is a merge conflict when finishing a branch through git flow

New in GitKraken 0.8.0 Beta (Feb 26, 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

New in GitKraken 0.7.2 Beta (Feb 21, 2016)

  • Fixed:
  • Fixed an error when opening up certain repo's with submodules
  • Fetching will now result in more fetching and less crashing

New in GitKraken 0.7.0 Beta (Feb 17, 2016)

  • New:
  • Right click a ref label in the graph to change the upstream through Set upstream
  • Push a local branch directly to remote via drag and drop even when the target remote is not the set upstream.
  • As an alternative to the ref panel, in the graph quickly checkout through double click on a ref label
  • Need to undo changes? Right click on a commit entry in the graph to Revert commit
  • Fixed:
  • The improved file view mode for the diff panel has horizontal scrolling again! Scroll right 80 characters and beyond, no matter how much real estate the display has. You'll see line numbers too! ↔️
  • Bitbucket team owned repositories are now accessible through the service
  • Validating credentials to improve error messaging and also prompting for login only when necessary
  • Improved:
  • Looking for more information about us and the current GitKraken version you're running? We thought you were and that's why the GitKraken-About menu received a brand new update to contain more detail.

New in GitKraken 0.6.2 Beta (Feb 8, 2016)

  • Fixed:
  • Fixed search index loading.
  • Fixed app getting into an unresolveable merge state.