Removes unused walkthrough files

walkthroughs/getting-started/0-tutorial.md

@@ -1,7 +0,0 @@
-<p align="center">
-  <a title="Watch GitLens Getting Started video" href="https://www.youtube.com/watch?v=UQPb73Zz9qk">
-    <img src="../../images/docs/gitlens-tutorial.png" alt="GitLens Getting Started video" />
-  </a>
-</p>
-
-GitLens **supercharges** Git inside VS Code and unlocks the <b>untapped knowledge</b> within each repository. Whether you’re a seasoned Git user or just getting started, GitLens makes it easier, safer and faster to leverage the full power of Git. This tutorial will show you how to get the most out of GitLens in VS Code.

walkthroughs/getting-started/1-setup.md

@@ -1,9 +0,0 @@
-## Quick Setup
-
-<p align="center">
-  <img src="../../images/docs/quick-setup.png" alt="GitLens Interactive Quick Setup" />
-</p>
-
-GitLens is powerful, feature rich, and highly customizable to meet your needs. Do you find code lens intrusive or the current line blame annotation distracting — no problem, quickly turn them off or change how they behave using the Quick Setup.
-
-💡 Use the [GitLens: Welcome (Quick Setup)](command:gitlens.showWelcomePage?%22quick-setup%22) command from the [Command Palette](command:workbench.action.quickOpen?%22>GitLens%3A%20Welcome%22) to open it.

walkthroughs/getting-started/10-interactive-rebase-editor.md

@@ -1,16 +0,0 @@
-## Visual Interactive Rebase
-
-<p align="center">
-  <img src="../../images/docs/rebase.gif" alt="Interactive rebase editor"/>
-</p>
-
-Simply drag & drop to reorder commits and select which ones you want to edit, squash, or drop.
-
-To use this directly from your terminal, e.g. when running `git rebase -i`,
-
-- set VS Code as your default Git editor
-  - `git config --global core.editor "code --wait"`
-- or, to only affect rebase, set VS Code as your Git rebase editor
-  - `git config --global sequence.editor "code --wait"`
-
-> To use the Insiders edition of VS Code, replace `code` in the above with `code-insiders`

walkthroughs/getting-started/11-terminal.md

@@ -1,7 +0,0 @@
-## Git Autolinks in Your Terminal
-
-<p align="center">
-  <img src="../../images/docs/terminal-links.gif" alt="Links in Integrated Terminal"/>
-</p>
-
-Autolinks are added for branches, tags, and commit ranges in the integrated terminal to quickly explore their commit history. While autolinks for commits will open a quick pick menu with commit details and actions.

walkthroughs/getting-started/12-plus.md

@@ -1,26 +0,0 @@
-## GitLens+ Features
-
-All-new, powerful, additional features that enhance your GitLens experience.
-
-[GitLens+ features](https://gitkraken.com/gitlens/plus-features?utm_source=gitlens-extension&utm_medium=in-app-links&utm_campaign=gitlens-plus-links) are free for local and public repos, no account required, while upgrading to GitLens Pro gives you access on private repos.
-
-[Learn more about GitLens+ features](https://gitkraken.com/gitlens/plus-features?utm_source=gitlens-extension&utm_medium=in-app-links&utm_campaign=gitlens-plus-links 'Learn more')
-
-🛈 All other GitLens features can always be used on any repo
-
-GitLens+ features include the Commit Graph, Visual File History, Worktrees, and more.
-
-<p align="center">
-  <img src="../../images/docs/commit-graph-illustrated.png" alt="Commit Graph illustration"/>
-  <br/>New Commit Graph
-</p>
-
-<p align="center">
-  <img src="../../images/docs/visual-file-history-illustrated.png" alt="Visual File History illustration"/>
-  <br/>Visual File History
-</p>
-
-<p align="center">
-  <img src="../../images/docs/worktrees-illustrated.png" alt="Worktrees illustration"/>
-  <br/>Worktrees
-</p>

walkthroughs/getting-started/2-customize.md

@@ -1,9 +0,0 @@
-## Customize GitLens
-
-<p align="center">
-  <img src="../../images/docs/settings.png" alt="GitLens Interactive Settings" />
-</p>
-
-GitLens provides a rich interactive settings editor, an easy-to-use interface, to configure many of GitLens' powerful features.
-
-💡 Use the [GitLens: Open Settings](command:gitlens.showSettingsPage) command from the [Command Palette](command:workbench.action.quickOpen?%22>GitLens%3A%20Open%20Settings%22) to open it.

walkthroughs/getting-started/3-current-line-blame.md

@@ -1,31 +0,0 @@
-## Current Line Blame []()
-
-<p align="center">
-  <img src="../../images/docs/current-line-blame.png" alt="Current Line Blame" />
-</p>
-
-GitLens adds an unobtrusive Git blame annotation at the end of the current line, which shows the author, date, and message of the current line's most recent commit.
-
-💡 Use the [Toggle Line Blame](command:workbench.action.quickOpen?%22>GitLens%3A%20Toggle%20Line%20Blame%22) command from the Command Palette to turn the annotation on and off.
-
-⚙️ Use the settings editor to customize the [current line annotations](command:gitlens.showSettingsPage?%22current-line%22 'Jump to the Current Line Blame settings').
-
-## Hovers
-
-<p align="center">
-  <img src="../../images/docs/hovers-current-line.png" alt="Current Line Blame Hover" />
-</p>
-
-Hovering over these blame annotations will reveal more details and links to explore. The **details** hover (the top section) provides many commit details and actions, including autolinks in commit messages, while the **changes** hover (the bottom section) shows a diff of the current line with its previous version and related actions.
-
-⚙️ Use the settings editor to customize the [hovers](command:gitlens.showSettingsPage?%22hovers%22 'Jump to the Hover settings').
-
-## Status Bar Blame
-
-<p align="center">
-  <img src="../../images/docs/status-bar.png" alt="Status Bar Blame" />
-</p>
-
-GitLens also adds Git blame information about the current line to the status bar.
-
-⚙️ Use the settings editor to customize the [status bar](command:gitlens.showSettingsPage?%22status-bar%22 'Jump to the Status Bar settings').

walkthroughs/getting-started/4-git-codelens.md

@@ -1,13 +0,0 @@
-## Git CodeLens
-
-<p align="center">
-  <img src="../../images/docs/code-lens.png" alt="Git CodeLens" />
-</p>
-
-GitLens adds Git authorship CodeLens to the top of the file and on code blocks. The **recent change** CodeLens shows the author and date of the most recent commit for the code block or file, while the **authors** CodeLens shows the number of authors of the code block or file and the most prominent author (if there is more than one).
-
-Clicking on the CodeLens performs a [customizable](command:gitlens.showSettingsPage?%22code-lens%22 'Jump to the Git CodeLens settings') action. For example, the **recent change** CodeLens will open a quick pick menu with the commit's file details and actions, where as the **authors** will toggle the whole file Git blame annotations.
-
-💡 Use the [Toggle Git CodeLens](command:workbench.action.quickOpen?%22>GitLens%3A%20Toggle%20Git%20CodeLens%22) command to turn the CodeLens on and off.
-
-⚙️ Use the settings editor to customize the [Git CodeLens](command:gitlens.showSettingsPage?%22code-lens%22 'Jump to the Git CodeLens settings').

walkthroughs/getting-started/5-revision-history.md

@@ -1,7 +0,0 @@
-## Navigate Revision History
-
-<p align="center">
-  <img src="../../images/docs/revision-navigation.gif" alt="Revision Navigation" />
-</p>
-
-With just a click of a button, you can navigate backwards and forwards through any file's history. Compare changes over time and see the revision history of the whole file or every individual line of code. Customizable and unobtrusive Git blame annotations are still shown on every line, telling you the author, date, and message for the last commit!

walkthroughs/getting-started/6-file-annotations.md

@@ -1,43 +0,0 @@
-## File Annotations
-
-<p align="center">
-  <img src="../../images/docs/gutter-toggle.png" alt="Toggle File Annotations" />
-</p>
-
-GitLens adds on-demand annotations for the whole file directly to the editor's scroll bar and in the gutter area, the space beside the line number, to help you gain more insights into your code.
-
-### File Blame
-
-<p align="center">
-  <img src="../../images/docs/gutter-blame.png" alt="File Blame" />
-</p>
-
-When activated, GitLens expands the gutter area to show the commit and author for each line of the file, similar to the current line blame. On the right edge of the gutter, an age indicator (heatmap) is shown to provide an easy, at-a-glance way to tell how recently lines were changed (see the Heatmap below for more details). An additional indicator, which highlights other lines that were also changed as part of the current line's commit, is shown both the far left edge and on the scrollbar.
-
-💡 On an active file, use the [Toggle File Blame](command:workbench.action.quickOpen?%22>GitLens%3A%20Toggle%20File%20Blame%22) command from the Command Palette to turn the annotation on and off.
-
-⚙️ Use the settings editor to customize the [file blame](command:gitlens.showSettingsPage?%22blame%22 'Jump to the File Blame settings').
-
-### File Changes
-
-<p align="center">
-  <img src="../../images/docs/gutter-changes.png" alt="File Changes" />
-</p>
-
-When activated, indicators are shown on the editor to highlight any local, unpublished, changes or lines changed by the most recent commit.
-
-💡 On an active file, use the [Toggle File Changes](command:workbench.action.quickOpen?%22>GitLens%3A%20Toggle%20File%20Changes%22) command from the Command Palette to turn the annotation on and off.
-
-⚙️ Use the settings editor to customize the [file changes](command:gitlens.showSettingsPage?%22changes%22 'Jump to the File Changes settings').
-
-### Heatmap
-
-<p align="center">
-  <img src="../../images/docs/gutter-heatmap.png" alt="File Heatmap" />
-</p>
-
-When activated, color-coded indicators are shown on the editor to highlight how recently lines were changed relative to all the other changes in the file. The colors range from hot, orange, to cold, blue, based on the age of the most recent change. Changes are considered cold after 90 days.
-
-💡 On an active file, use the [Toggle File Heatmap](command:workbench.action.quickOpen?%22>GitLens%3A%20Toggle%20File%20Heatmap%22) command from the Command Palette to turn the annotation on and off.
-
-⚙️ Use the settings editor to customize the [file heatmap](command:gitlens.showSettingsPage?%22heatmap%22 'Jump to the File Heatmap settings').

walkthroughs/getting-started/7-git-side-bar-views.md

@@ -1,3 +0,0 @@
-## Side Bar Views
-
-GitLens adds side bar views for Commits, File History, Branches, Remotes, Stashes, Tags, Contributors, Search & Compare, and more that provide rich source control details and functionality.

walkthroughs/getting-started/8-hosting-service-integrations.md

@@ -1,9 +0,0 @@
-## Hosting Service Integrations
-
-<p align="center">
-  <img src="../../images/docs/hosting-integrations.png" alt="Hosting service integrations"/>
-</p>
-
-GitLens provides integrations with many Git hosting services, including GitHub, GitHub Enterprise, GitLab, GitLab self-managed, Gitea, Gerrit, Google Source, Bitbucket, Bitbucket Server, Azure DevOps and custom servers.
-
-All Git host integrations provide issue and pull request auto-linking, while rich integrations (e.g. GitHub & GitLab) provide more detailed hover information for auto-linked issues and pull requests, pull requests associated with branches and commits, and avatars.

walkthroughs/getting-started/9-git-command-palette.md

@@ -1,9 +0,0 @@
-## Git Command Palette
-
-<p align="center">
-  <img src="../../images/docs/git-command-palette.png" alt="Git command palette"/>
-</p>
-
-The [Git Command Palette](command:gitlens.gitCommands) provides guided, step-by-step access to many common Git commands, as well as quick access to commits (history and search), stashes, and status (current branch and working tree).
-
-You can quickly navigate and safely execute Git commands through easy-to-use menus where each command can require an explicit confirmation step before executing.

walkthroughs/plus/commit-graph.md

@@ -1,9 +0,0 @@
-## Commit Graph
-
-<p align="center">
-  <img src="../../images/docs/commit-graph-illustrated.png" alt="Commit Graph"/>
-</p>
-
-The Commit Graph helps you easily visualize your repository and keep track of all work in progress. Not only does it help you verify your changes, but also easily see changes made by others and when.
-
-Use the rich commit search to find exactly what you're looking for. It's powerful filters allow you to search by a specific commit, message, author, a changed file or files, or even a specific code change.

walkthroughs/plus/intro.md

@@ -1,20 +0,0 @@
-## Introducing GitLens+ Features
-
-All-new, powerful, additional features that enhance your current GitLens experience.
-
-[GitLens+ features](https://gitkraken.com/gitlens/plus-features?utm_source=gitlens-extension&utm_medium=in-app-links&utm_campaign=gitlens-plus-links) are free for local and public repos, no account required, while upgrading to GitLens Pro gives you access on private repos.
-
-[Learn more about GitLens+ features](https://gitkraken.com/gitlens/plus-features?utm_source=gitlens-extension&utm_medium=in-app-links&utm_campaign=gitlens-plus-links 'Learn more')
-
-🛈 All other GitLens features can always be used on any repo
-
-GitLens+ features include the Commit Graph, Visual File History, Worktrees, and more.
-
-<p align="center">
-  <img src="../../images/docs/commit-graph-illustrated.png" alt="Commit Graph Illustration"/>
-  <br/>New Commit Graph
-</p>
-
-## Does this affect existing features?
-
-No, the introduction of GitLens+ features has no impact on existing GitLens features, so you won't lose access to any of the GitLens features you know and love. In fact, we are heavily investing in enhancing and expanding the GitLens feature set. Additionally, GitLens+ features are freely available to everyone for local and public repos, while upgrading to GitLens Pro gives you access on private repos.

walkthroughs/plus/rich-integrations.md

@@ -1,19 +0,0 @@
-## Rich Self-Hosted Git Integrations
-
-GitLens Pro users can access rich integrations for self-hosted providers.
-
-### GitHub Enterprise
-
-GitHub Enterprise users can see GitHub avatars for commit authors, richer details for auto-linked issues and pull requests, as well as pull requests associated with commits and branches.
-
-<p align="center">
-  <img src="../../images/docs/hovers-github-integration.png" alt="Commit Hover with GitHub Rich Integration"/>
-</p>
-
-### GitLab Self-Managed
-
-GitLab Self-Managed users can see GitLab avatars for commit authors, richer details for auto-linked issues and merge requests, as well as merge requests associated with commits and branches.
-
-<p align="center">
-  <img src="../../images/docs/hovers-gitlab-integration.png" alt="Commit Hover with GitLab Rich Integration"/>
-</p>

walkthroughs/plus/visual-file-history.md

@@ -1,13 +0,0 @@
-## Visual File History
-
-<p align="center">
-  <img src="../../images/docs/visual-file-history-illustrated.png" alt="Visual File History View"/>
-</p>
-
-The Visual File History allows you to quickly see the evolution of a file, including when changes were made, how large they were, and who made them.
-
-Use it to quickly find when the most impactful changes were made to a file or who best to talk to about file changes and more.
-
-Authors who have contributed changes to the file are on the left y-axis to create a swim-lane of their commits over time (the x-axis). Commit are plotted as color-coded (per-author) bubbles, whose size represents the relative magnitude of the changes.
-
-Additionally, each commit's additions and deletions are visualized as color-coded, stacked, vertical bars, whose height represents the number of affected lines (right y-axis). Added lines are shown in green, while deleted lines are red.

walkthroughs/plus/worktrees.md

@@ -1,13 +0,0 @@
-## Git Worktrees
-
-<p align="center">
-  <img src="../../images/docs/worktrees-illustrated.png" alt="Worktrees View"/>
-</p>
-
-Worktrees help you multitask by minimizing the context switching between branches, allowing you to easily work on different branches of a repository simultaneously.
-
-Avoid interrupting your work in progress when needing to review a pull request. Simply create a new worktree and open it in a new VS Code window, all without impacting your other work.
-
-You can create multiple working trees, each of which can be opened in individual windows or all together in a single workspace.
-
-_Note: Worktrees do not yet work with VS Code on the Web._

walkthroughs/welcome/commit-graph.md

@@ -1,3 +0,0 @@
-<p align="center">
-  <img src="../../images/docs/commit-graph-illustrated.png" alt="Commit Graph"/>
-</p>