Released: Jun 14, 2022

Updates in GitKraken Desktop V8.6.0

Funktionen

• Users can now create Workspaces using Bitbucket Server repos.
• Users can now select Git Bash as their default shell in Microsoft Windows for GitKraken CLI.
• Repo and Terminal Tab aliases:
  • Users can now set an alias for a repository:
    • 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 now set an alias for individual Terminal Tabs:
    • 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.
• Git LFS performance improvements:
  • Users will now see faster performance when cloning LFS repositories.
  • Users will now 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.
• Users will now 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.

Fehlerkorrekturen

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