Skip to content

Commit 42382b7

Browse files
authored
Merge pull request #189 from jkelroy/9.11-doc-updates
9.11 Updates
2 parents 8bae4ca + 1cb2783 commit 42382b7

File tree

8 files changed

+102
-5
lines changed

8 files changed

+102
-5
lines changed

_images/Cloud-Patch-Permissions.png

29.6 KB
Loading

_images/Focus-View-Actions.png

173 KB
Loading

_images/only-collaborators.png

39.5 KB
Loading

gitkraken-client/current.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,76 @@ Check out our [GitKraken Roadmap](https://www.gitkraken.com/git-client/roadmap)
1616

1717
***
1818

19+
<a id="v9-11-0"></a>
20+
## Version 9.11.0
21+
22+
_"Don't be so tight-fisted with that patch. Or actually, do be?"_
23+
24+
### Wednesday, December 13th, 2023
25+
26+
### New ✨
27+
- Added new actions to Focus View items:
28+
- Merge pull request
29+
- Close pull request
30+
- Update issue status
31+
- Mark issue as closed
32+
- Open pull request/issue in the browser
33+
- Added new ways to share Cloud Patches:
34+
- 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`.
35+
- You can now share Cloud Patches directly with members of your organization by selecting specific users when creating a Cloud Patch.
36+
- You can now view Cloud Patches shared with you in the Cloud Patches Left Panel section under `Shared with Me`.
37+
- You can now create Cloud Patches from the Command Palette (<kbd>Ctrl/Cmd+P</kbd>).
38+
- You can now use the left and right arrow keys (as well as <kbd>h</kbd> and <kbd>l</kbd>) to navigate between a commit in the Commit Graph and the first file in that commit.
39+
40+
### Improvements 🙌
41+
- Experimental Feature - Git Executable:
42+
- Added merge support.
43+
- Add pull support when the selected branch is not active.
44+
- Added new log level `GIT_SILLY` to get extra info about `git` and `ssh` commands in logs.
45+
- Added new UI Customization setting in preferences to use generic hosting service icons in `branch/tags`.
46+
47+
### Bug Fixes 🐛
48+
- The commit message view in the Commit Panel now resizes properly when rebasing.
49+
- Fixed an issue where SSH signed tags would display the signature in their tooltip.
50+
- Fixed an issue where pull requests for GitHub Enterprise would not load in Workspaces.
51+
- Fixed an issue where dragging a Commit Graph label onto a Left Panel branch could present a fast-forward option for the wrong remote.
52+
- 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.
53+
- 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.
54+
- Fixed an issue where the Commit Graph could display a black region after closing an issue view.
55+
- Fixed an issue where the Commit Graph would not always take you to the commit when searching.
56+
- Fixed an issue where grouped `branch/tag` nodes would not expand after losing focus on Windows and Linux.
57+
- Fixed an issue where synced Azure Workspaces would have duplicate entries in the repositories page.
58+
- Moved the `branch/tag` icons after their name label in the Commit Graph.
59+
- Fixed a case where the Focus View was in an infinite loading state if no issue tracker is selected.
60+
- Fixed an issue where detached heads were displayed in the `TAGS` section instead of the `BRANCH` section of the Left Panel.
61+
- Fixed an issue where the context menu would not display when dragging a tag into a local branch.
62+
- Fixed an issue where cloning repos from Workspaces would not work if at least 1 repo failed to fetch data.
63+
- Fixed flicker on commit selection when holding up/down on the Commit Graph.
64+
- Improved performance in the Commit Graph when moving between commits using the up/down keys.
65+
- Fixed an issue where inviting users to an organization would silently fail.
66+
- Added missing options for `detached head` context menu: `Copy commit sha`, `Solo`, `Hide`, `Create patch` and `Create cloud patch`.
67+
- Fixed an issue where GitLab Self-Managed Workspaces would not load repos, merge requests, or issues if a repo was deleted.
68+
- Fixed an issue where some deep links may not be recognized by GitKraken Client.
69+
- Fixed an issue where patch files containing multi-byte characters could fail to apply.
70+
71+
### New actions from Focus View
72+
73+
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.
74+
75+
<img src="/wp-content/uploads/Focus-View-Actions.png" class="img-responsive center img-bordered">
76+
77+
### Set permissions for Cloud Patches
78+
79+
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.
80+
81+
<img src="/wp-content/uploads/Cloud-Patch-Permissions.png" class="img-responsive center img-bordered">
82+
83+
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.
84+
85+
<img src="/wp-content/uploads/only-collaborators.png" class="img-responsive center img-bordered">
86+
87+
***
88+
1989
<a id="v9-10-0"></a>
2090
## Version 9.10.0
2191

gitkraken-client/experimental-features.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,12 @@ Find below a list of features using the Git binary if the Git Executable experim
6666
**Added in 9.10.0:**
6767
- Added Pull (fast-forward if possible) and Pull (fast-forward only) support.
6868
- Added cherry-pick support
69+
70+
**Added in 9.11.0:**
71+
- Added merge support.
72+
- Add pull support when the selected branch is not active.
73+
- Added new log level `GIT_SILLY` to get extra info about `git` and `ssh` commands in logs.
74+
6975
---
7076

7177
### AI Commit Message Generation
@@ -82,7 +88,7 @@ With this setting enabled, GitKraken Client will have the ability to generate co
8288

8389
**Prompt:** This is what is sent to OpenAI. We have it pre-filled to hopefully get Open AI on the right track. However, you can enter whatever you want here and it will be sent when you click ✨.
8490

85-
#### How to use in GKC
91+
#### How to use in GitKraken Client
8692

8793
Once you have AI commit message generation enabled you will see ✨ sparkles ✨ in the commit message field. Stage your changes and click this button to get the AI magic started!
8894

@@ -132,7 +138,11 @@ To create a Cloud Patch, click the share icon <i class="fa-solid fa-share"></i>
132138

133139
<img src='/wp-content/uploads/gkc-create-cloud-patch.png' class='img-bordered img-responsive center'>
134140

135-
This link can be shared with users to open the Cloud Patch in GitKraken Client or GitLens. When a Cloud Patch link is opened, the user will be prompted to open the client, clone or open the repository if not known to GitKraken Client, and then select the base branch to apply the patch to. From here, they can simply select `apply patch to <branch>`.
141+
When creating a Cloud Patch, you have the options to share with `Anyone with the link`, `Anyone in my org`, or `Only collaborators`. You can also share Cloud Patches directly with members of your organization. Cloud Patches shared with you can be viewed in the Cloud Patches Left Panel section under `Shared with Me`.
142+
143+
<img src='/wp-content/uploads/Cloud-Patch-Permissions.png' class='img-bordered img-responsive center'>
144+
145+
Cloud Patch links can be shared with users to open the Cloud Patch in GitKraken Client or GitLens. When a Cloud Patch link is opened, the user will be prompted to open the client, clone or open the repository if not known to GitKraken Client, and then select the base branch to apply the patch to. From here, they can simply select `apply patch to <branch>`.
136146

137147
<img src='/wp-content/uploads/gkc-apply-cloud-patch-example.gif' class='img-bordered img-responsive center'>
138148

gitkraken-client/gitkraken-client-home.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Check out the introduction video and links below to get started with GitKraken C
1414
## GitKraken Client Tutorial
1515

1616
<div class='embed-container embed-container--16-9'>
17-
<iframe width='560' height='315' src='https://www.youtube.com/embed/RiAeNSFjjLc?rel=0&vq=hd1080' frameborder='0' allowfullscreen></iframe>
17+
<iframe width='560' height='315' src='https://www.youtube.com/embed/LBlijN29gb8?rel=0&vq=hd1080' frameborder='0' allowfullscreen></iframe>
1818
</div>
1919

2020
***

gitkraken-client/keyboard-shortcuts.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,15 +98,23 @@ We know keyboard shortcuts help get things done faster, and here’s a handy lis
9898
</thead>
9999
<tbody>
100100
<tr>
101-
<td>Select next commit in graph</td>
101+
<td>Select previous item</td>
102102
<td><kbd>J</kbd> or <kbd>&darr;</kbd></td>
103103
<td><kbd>J</kbd> or <kbd>&darr;</kbd></td>
104104
</tr>
105105
<tr>
106-
<td>Select previous commit in graph</td>
106+
<td>Select next item</td>
107107
<td><kbd>K</kbd> or <kbd>&uarr;</kbd></td>
108108
<td><kbd>K</kbd> or <kbd>&uarr;</kbd></td>
109109
</tr>
110+
<tr>
111+
<td>Select the item to the right</td>
112+
<td><kbd>L</kbd> or <kbd>&rarr;</kbd></td>
113+
</tr>
114+
<tr>
115+
<td>Select the item to the left</td>
116+
<td><kbd>H</kbd> or <kbd>&larr;</kbd></td>
117+
</tr>
110118
<tr>
111119
<td>Select next item in branch</td>
112120
<td><kbd>Shift</kbd><kbd>&darr;</kbd><br>

gitkraken-client/workspaces.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,15 @@ Pull Requests and Issues can be pinned (and unpinned) by selecting the <i class=
106106

107107
<img src="/wp-content/uploads/9-10-pin-and-snooze.gif" class="img-bordered img-responsive center">
108108

109+
From the Focus View, you can take action quickly on items such as:
110+
- Merge pull request
111+
- Close pull request
112+
- Update issue status
113+
- Mark issue as closed
114+
- Open pull request/issue in the browser
115+
116+
<img src="/wp-content/uploads/Focus-View-Actions.png" class="img-bordered img-responsive center">
117+
109118
Instead of hunting for these pieces of information separately, you can get a holistic view of what you’re working on.
110119

111120
### Team view

0 commit comments

Comments
 (0)