GitKraken V9.1.0

Released: Feb 7, 2023

Updates in V9.1.0

Features

  • Improved Microsoft Windows Subsystem for Linux (WSL) 2 support for the Linux version of GitKraken Client.
    • Users can now install GitKraken Client in a WSL 2 distribution with WSLg and work with their Linux repos.
    • For the best experience, it is recommended to also install GitKraken Client on a Microsoft Windows machine to work with repos hosted outside their WSLg distribution.
  • Added new encoding support - Configure from Preferences > Encoding or from the top right of any File Diff view.
  • Users can now bypass Git Hooks when committing after entering a commit message.
  • GitKraken Insights now available for Cloud Workspaces connected to Microsoft Azure DevOps.
  • You can now amend (rename) stashes.
  • 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.

Fixes

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