Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit d84147a

Browse files
Merge pull request #116 from jjsilva4/purple-docs-pass/initial-audit
Improves 7 GitLens doc pages and feature descriptions
2 parents 59ceac5 + 4cbfa19 commit d84147a

7 files changed

+1160
-554
lines changed

‎gitlens/GL-GK-Account.md‎

Lines changed: 48 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,46 +1,72 @@
11
---
2-
3-
title: GitKraken Account - Gitlens
4-
description: Learn about GitKraken Accounts
2+
title: GitKraken Account – GitLens
3+
description: Learn how to create and manage your GitKraken account for GitLens features.
54
taxonomy:
6-
category: gitlens
7-
5+
category: gitlens
86
---
97

10-
Your GitKraken account is your key to unlock the most personal experience across GitKraken products.
8+
Your GitKraken account is your key to unlocking the most personal experience across GitKraken products.
119

12-
<div class='callout callout--basic'>
13-
<p>Note that your GitKraken account is not compatible with <a href="/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud/">Git Integration for Jira</a>.</p>
14-
<p>It is recommended to create and use a single GitKraken account for yourself, to not create a second account for yourself, and to not share an account with others.</p>
15-
</div>
10+
<figure class='callout callout--basic'>
11+
<p><strong>Note:</strong> GitKraken accounts are not compatible with <a href="/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud/">Git Integration for Jira</a>.</p>
12+
<p>We recommend creating and using a single GitKraken account per person. Avoid creating duplicate accounts or sharing your account with others.</p>
13+
</figure>
1614

1715
***
1816

19-
## Login
17+
## Sign In or Create an Account
18+
19+
You can create a GitKraken account at [gitkraken.dev](https://gitkraken.dev/register?source=help_center&product=gitkraken_dot_dev) or directly within GitLens.
20+
21+
When prompted with the login screen, select **Create an account** to begin. Choose one of the following seven identity providers:
22+
23+
- GitHub
24+
- GitLab
25+
- Bitbucket
26+
- Azure DevOps
27+
- Email
28+
- Google
29+
- [Single Sign-On (SSO)](/gk-dev/gk-dev-single-sign-on/)
2030

21-
You can create your GitKraken account at [gitkraken.dev](https://gitkraken.dev/register?source=help_center&product=gitkraken_dot_dev) or from within Gitlens. When presented with the login page (see image below), you may need to select "Create an account" before selecting how you would like to create your GitKraken account. There are seven options available to create your GitKraken account and login. You can choose your preferred hosting service (GitHub, GitLab, Bitbucket, and Azure DevOps), login with email, Google, or [SSO](/gk-dev/gk-dev-single-sign-on/).
31+
<figure>
32+
<img src="/wp-content/uploads/gk-dev-create-account.png" alt="GitKraken account creation screen with multiple login options" class="img-responsive center img-bordered">
33+
<figcaption style="text-align: center; color: #888">Select a login method to create your GitKraken account</figcaption>
34+
</figure>
2235

23-
<imgsrc="/wp-content/uploads/gk-dev-create-account.png"class="img-responsive center img-bordered">
36+
Once your account is created, it is linked to the primary email associated with your selected login method. If you choose **Sign up with Email**, check your inbox for a verification link to complete the process.
2437

25-
Once you have created your GitKraken account, your account is tied to the primary email address of whichever method you selected. If you use the "Sign up with Email" method, you will need to verify your email address with a link sent to your email.
2638

2739
***
2840

29-
## Personalization
41+
## Personalize Your Account
3042

31-
You can personalize your account to determine how you appear to other users within any GitKraken [organization](/gk-dev/gk-dev-organization/) your account may be associated with. You can personalize your account at [gitkraken.dev/account](https://gitkraken.dev/?source=help_center&product=gitkraken_dot_dev) once you have logged in. Here you can change your avatar, name, username, email, and password.
43+
You can personalize your GitKraken account to control how your profile appears to other users within any associated [organization](/gk-dev/gk-dev-organization/). Visit [gitkraken.dev/account](https://gitkraken.dev/?source=help_center&product=gitkraken_dot_dev) after logging in to:
3244

33-
If you select your profile picture, you will be taken to [Gravatar](https://gravatar.com). This is where you can select your avatar which your GitKraken account pulls from Gravatar and is associated with the shared email between your GitKraken account and your Gravatar. Please note that it may take several hours for your avatar change to reflect in GitKraken.
45+
- Update your avatar
46+
- Edit your name, username, and email
47+
- Change your password
3448

35-
<imgsrc="/wp-content/uploads/gk-dev-account-personalization.png"srcset="/wp-content/uploads/gk-dev-account-personalization@2x.png"class="img-responsive center img-bordered">
49+
To change your avatar, click your profile picture. This will redirect you to [Gravatar](https://gravatar.com), where you can manage the avatar linked to your email address. GitKraken retrieves your avatar from Gravatar based on the shared email between accounts.
3650

51+
> It may take several hours for avatar changes to appear in GitKraken.
52+
53+
<figure>
54+
<img src="/wp-content/uploads/gk-dev-account-personalization.png" srcset="/wp-content/uploads/gk-dev-account-personalization@2x.png" alt="GitKraken account personalization options" class="img-responsive center img-bordered">
55+
<figcaption style="text-align: center; color: #888">Customize your name, email, avatar, and password</figcaption>
56+
</figure>
3757

3858
***
3959

40-
## Delete
60+
## Delete Your Account
61+
62+
To delete your GitKraken account:
63+
64+
1. Go to [gitkraken.dev/account](https://gitkraken.dev/account?source=help_center&product=gitkraken_dot_dev).
65+
2. Select **Delete my Account** (highlighted in red).
66+
3. Follow the on-screen confirmation steps.
67+
4. Select **Delete your Account** to confirm deletion.
4168

42-
You can delete your GitKraken account at any time by navigating to [gitkraken.dev/account](https://gitkraken.dev/account?source=help_center&product=gitkraken_dot_dev) and selecting "<spanstyle='color: red;'>Delete my Account</span>." Complete the confirmation instructions and select "<spanstyle='color: red;'>Delete your Account</span>" to complete the process.
69+
> Important: If you're a non-admin member of a GitKraken organization, you must ask an admin to remove your account before you can delete it. Organization admins have control over employee accounts.
4370
44-
One exception to this is if you are a non-admin of a GitKraken organization. This is due to company organizations having administrative control over employee accounts. You need to ask an administrator of the GitKraken organization to remove your account from it before deleting your GitKraken account.
71+
GitKraken complies with GDPR. Once deleted, your account cannot be restored. This action permanently removes your subscriptions, Cloud Workspaces, Insights data, and organizations.
4572

46-
GitKraken is compliant with GDPR. Once you delete your GitKraken account, it cannot be undone. By doing so you will lose the remainder of your subscription (if applicable), cloud workspaces, Insights, organizations, and more.
Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,22 @@
11
---
2-
3-
title: Gitlens Interactive Code History
4-
description: New Page Description
2+
title: GitLens Interactive Code History
3+
description: Learn how GitLens helps you explore and understand your repository’s commit history.
54
taxonomy:
6-
category: gitlens
7-
5+
category: gitlens
86
---
97

10-
<div class='embed-container embed-container--16-9'>
11-
<iframe width='560' height='315' src='https://www.youtube.com/embed/uSc7aQV8uMs?si=7bGXpqRI0lv7k-A0' frameborder='0' allowfullscreen></iframe>
12-
</div>
8+
<kbd>Last updated: July 2025</kbd>
9+
10+
<figure class='embed-container embed-container--16-9'>
11+
<iframe width='560' height='315' src='https://www.youtube.com/embed/uSc7aQV8uMs?si=7bGXpqRI0lv7k-A0' frameborder='0' allowfullscreen title="GitLens Interactive Code History video overview"></iframe>
12+
</figure>
13+
14+
&nbsp;
15+
16+
Understanding code history in large repositories can be challenging, especially with multiple branches and contributors. GitLens helps simplify this process by providing tools that surface meaningful context:
1317

14-
<p> &nbsp; </p>
18+
- **Commit Graph** – Visualize the structure of your repository.
19+
- **GitLens Inspect** – Drill into file and line-level history.
20+
- **Inline Blame and Hovers** – Quickly see who changed what and when.
1521

16-
Understanding code history can be difficult when looking at complex repositories with multiple branches and contributors. Developers can struggle to easily see who made changes, why, and when. With the use of The Commit Graph, GitLens Inspect, and Inline Blame and Hovers, GitLens offers the ability to easily navigate through your repository to provide insights about the history and interact with it to better manage your code.
22+
These features make it easier to navigate your repository, understand changes, and make informed decisions about your code.

‎gitlens/GL-Streamline-Collaboration.md‎

Lines changed: 44 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,62 @@
11
---
2-
3-
title: Gitlens Streamline Collaboration
4-
description: How can gitlens help streamline collaboration
2+
title: GitLens Streamline Collaboration
3+
description: How GitLens helps teams collaborate efficiently using Cloud Patches and Code Suggest.
54
taxonomy:
6-
category: gitlens
7-
5+
category: gitlens
86
---
7+
<kbd>Last updated: July 2025</kbd>
8+
9+
<figure class='embed-container embed-container--16-9'>
10+
<iframe width='560' height='315' src='https://www.youtube.com/embed/ljKEzaCMEow?si=YFf7oME8PG926kET' frameborder='0' allowfullscreen title="GitLens Streamline Collaboration video overview"></iframe>
11+
</figure>
12+
13+
&nbsp;
14+
15+
Collaborating in a repository can be tricky—especially when you want to share work without flooding the remote with temporary commits or branches. Traditional pull request workflows also limit which files you can review or comment on—typically only those that have changed.
16+
17+
GitLens helps streamline collaboration through:
18+
19+
- **Cloud Patches** – Share uncommitted code changes without pushing to a remote.
20+
- **Code Suggest** – Propose changes on any file, not just modified ones.
21+
22+
## Cloud Patches <span style="color: #888;">`PRO`</span>
923

24+
Cloud Patches are Git patches that can be shared with anyone in your GitKraken organization. Teammates can apply them directly to their working directory—ideal for reviewing or collaborating on code before it’s committed.
1025

11-
<div class='embed-container embed-container--16-9'>
12-
<iframe width='560' height='315' src='https://www.youtube.com/embed/ljKEzaCMEow?si=YFf7oME8PG926kET' frameborder='0' allowfullscreen></iframe>
13-
</div>
26+
To create a Cloud Patch:
1427

15-
<p> &nbsp; </p>
28+
1. Make and save changes to any file.
29+
2. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
30+
3. Run: `GitLens: Share as Cloud Patch...`
31+
4. Select teammates to share with.
1632

17-
When collaborating with others in a repository, it can be difficult to share code without bloating your repository with multiple commits and branches that may not be ready to contribute to the remote. Additionally, pull request reviews can be limiting for what you have access to review, comment on, and does not give you the ability to review files that have not been modified. With the use of Cloud Patches and Code Suggest, GitLens offers the ability to easily share code without needing to commit/push it to a remote and allows you to suggest code changes to any file in the repository.
33+
Recipients will see the patch in the **Cloud Patch** sidebar and can apply it directly to their workspace.
1834

19-
#### Cloud Patches `PRO`
35+
[Open the Cloud Patches View in GitLens](vscode://eamodio.gitlens/link/command/cloud-patches)
2036

21-
Cloud Patches are Git patches that can be shared with anyone in your GitKraken organization to quickly share code changes with others. It can be applied to their working directory to continue to collaborate on or commit to the repository.
37+
<figure class='callout callout--warning'>
38+
<p>This feature is available with a GitLens Pro subscription or higher.</p>
39+
</figure>
2240

23-
To create a cloud patch, make changes to any file in a repository and then save those changes. Then, use the command palette (command/ctrl + shift + P) > _GitLens: Share as Cloud Patch..._.
2441

25-
When you select members to share it with, they will see this in the Cloud Patch sidebar to be able to apply to their working directory.
42+
## Code Suggest <spanstyle="color: #888;">`PRO`</span>
2643

27-
<a href="vscode://eamodio.gitlens/link/command/cloud-patches">Open the Cloud Patches View in GitLens</a>.
28-
<div class='callout callout--warning'>
29-
<p>This feature is only available for Pro subscription tiers or higher</p>
30-
</div>
44+
Code Suggest lets you propose edits to any file in a repository—regardless of whether the file was modified. You can submit these suggestions directly to another team member’s open pull request.
3145

32-
#### Code Suggest `PRO`
46+
To create a Code Suggestion:
3347

34-
Code Suggest allows you to make edits across the entire repository that can be submitted to anyone's open pull request.
48+
1. Check out a branch that has an open pull request.
49+
2. Make and save changes to any file.
50+
3. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
51+
4. Run: `GitLens: Show Inspect View` > **Suggest Changes for PR**.
3552

36-
To create a Code Suggestion, have a branch checked out with an open pull request, make changes to any files and save those changes. Then, use the command palette (command/ctrl + shift + P) > _GitLens: Show inspect view_ > Suggest Changes for PR.
53+
The PR creator can:
3754

38-
The pull request creator can then review these changes, apply them to their working directory to continue updating them, and accept the changes to commit/push them to the pull request.
55+
- Review your suggestions
56+
- Apply them to their working directory
57+
- Commit and push the changes to the open pull request
3958

40-
<div class='callout callout--warning'>
41-
<p>This feature is only available for Pro subscription tiers or higher</p>
42-
</div>
59+
<figure class='callout callout--warning'>
60+
<p>This feature is available with a GitLens Pro subscription or higher.</p>
61+
</figure>
4362

44-
***

‎gitlens/GL-accelerate-pr-reviews.md‎

Lines changed: 47 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,65 @@
11
---
2-
32
title: Accelerate PR Reviews
4-
description: Explore using Gitlens to accelerate your PR Reviews
3+
description: Explore how GitLens helps streamline pull request reviews using Launchpad and Worktrees.
54
taxonomy:
6-
category: gitlens
7-
5+
category: gitlens
86
---
97

8+
<kbd>Last updated: July 2025</kbd>
9+
10+
<figure class='embed-container embed-container--16-9'>
11+
<iframe width='560' height='315' src='https://www.youtube.com/embed/FJ_IdTcqBi0?si=PFT5wDTiGs87Eu0-' frameborder='0' allowfullscreen title="Accelerate PR Reviews with GitLens"></iframe>
12+
</figure>
13+
14+
&nbsp;
15+
16+
Reviewing pull requests (PRs) in the browser can interrupt your workflow. Switching tabs, checking email notifications, and managing local branches can be time-consuming—especially when the PRs aren’t even relevant to you.
17+
18+
GitLens helps streamline PR reviews directly inside Visual Studio Code. With **Launchpad** and **Worktrees**, you can:
19+
20+
- View all relevant PRs grouped by actionable categories.
21+
- Avoid context switching with an integrated experience.
22+
- Work across multiple branches using separate working directories.
23+
24+
## Launchpad <span style="color: #888;">`PRO`</span>
25+
26+
To use Launchpad:
27+
28+
1. Connect your [GitHub Integration](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
29+
2. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
30+
3. Run: `GitLens: Open Launchpad`.
1031

11-
<div class='embed-container embed-container--16-9'>
12-
<iframe width='560' height='315' src='https://www.youtube.com/embed/FJ_IdTcqBi0?si=PFT5wDTiGs87Eu0-' frameborder='0' allowfullscreen></iframe>
13-
</div>
32+
Launchpad displays grouped pull requests:
1433

15-
<p> &nbsp; </p>
34+
- On your current branch
35+
- Assigned to you for review
36+
- Waiting for follow-up
37+
- Blocked or in draft
1638

17-
Reviewing pull requests can be cumbersome due to needing to context switch to a browser to search through pull requests that are irrelevant to you. Email notification updates can interrupt your workflows when checking out branches if you have work in progress. With the use of Launchpad and Worktrees, GitLens offers the ability to see all pull requests that are organized in groups of actions that you need to take and utilize worktrees to simultaneously have separate working directories, all without leaving Visual Studio Code.
39+
To start reviewing:
1840

19-
#### Launchpad `PRO`
41+
- Select a PR.
42+
- Choose **Open in Worktree** or **Switch to Branch or Worktree**.
2043

21-
To begin working with the Launchpad, connect the [GitHub Integration](gitkraken.dev/settings/integrations?source=help_center&product=gitlens). Once connected, you can access the Launchpad from the command palette (command/ctrl + shift + P) > _GitLens: Open Launchpad_.
44+
[Open the Launchpad in GitLens](vscode://eamodio.gitlens/link/command/launchpad)
2245

23-
Here, you can see pull requests that are open on your current branch, blocked, need your review, require follow-up, waiting for a review, and in draft.
46+
<figure class='callout callout--warning'>
47+
<p>This feature is available with a GitLens Pro subscription or higher.</p>
48+
</figure>
2449

25-
To begin reviewing a pull request, simply select a pull request and then Open in Worktree or Switch to Branch or Worktree.
2650

27-
<a href="vscode://eamodio.gitlens/link/command/launchpad">Open the Launchpad in GitLens</a>.
28-
<div class='callout callout--warning'>
29-
<p>This feature is only available for Pro subscription tiers or higher</p>
30-
</div>
31-
#### Worktrees
51+
## Worktrees
3252

33-
Worktrees allow you to have separate working directories, meaning you can check out and work in multiple branches at once. This allows you to not need to commit or stash changes you are currently working on in order to review a pull request.
53+
Worktrees let you check out multiple branches simultaneously in separate working directories. This means you don’t need to commit or stash in-progress changes before switching to another branch—perfect for reviewing pull requests without disrupting your workflow.
3454

35-
Once you have opened a worktree, you can easily begin reviewing all changes made in the Pull Request sidebar. You can see what commits have been made, what files have been changed, open the file diffs, and more.
55+
After opening a worktree, use the Pull Request sidebar to:
3656

37-
<a href="vscode://eamodio.gitlens/link/command/worktrees">Open the Worktree View in GitLens</a>.
57+
- Review all commits in the PR
58+
- Explore changed files
59+
- View diffs and inspect updates line by line
3860

39-
<div class='callout callout--warning'>
40-
<p>Community plan is restricted to public and local repositories only.</p>
41-
</div>
61+
[Open the Worktree View in GitLens](vscode://eamodio.gitlens/link/command/worktrees)
4262

43-
***
63+
<figure class='callout callout--warning'>
64+
<p>The Community plan supports only public and local repositories.</p>
65+
</figure>

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /