GitKraken V8.5.0

DevOpsリポジトリをサポート
5月 19, 2022
新バージョン

機能

  • GitKraken WorkSpaces now support Microsoft 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.
  • Git LFS Improvements:
    • Users will now experience a reduced delay in updating the graph and commit detail panel when selecting commits in LFS enabled repos.
  • 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 now open it in a Repo Tab.
    • Organization admins and owners will now see a new "Show All Workspaces" checkbox, which makes seeing all available Workspaces simpler.
    • Users can now leverage GitHub’s search syntax when using the Workspaces Pull Requests view search.
    • Added more options for filtering in the Workspaces Pull Requests view. The new options include:
      • "Opened by Me" which shows pull requests that were opened by the user. This filter is available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
      • "At Risk" which shows 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" which limits 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 Microsoft 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.
GitKraken

GitKraken

開発者向けの強力なGitツールスイート

ご質問がありますか?

今すぐ GitKraken ライセンススペシャリストとライブ チャット