AboutAI ToolsCursorClaude CodeLovableBolt.newAI tool reviewsTutorialsVibe codingAI agentsMobile apps with AIAll tutorialsBlogSponsorWork With MeJoin 285K+ Subscribers

Video tutorial · The Metaverse Guy

How GitLens and GitKraken Transformed My Git Workflow

After a decade of using Git, I finally explored GitLens and GitKraken properly — and these features now save me hours every week.

How I Fixed My Code Faster Than Ever! GitKraken Tutorial
Published
21 November 2025
Length
7 min
Views
10,856 views
On YouTube
How I Fixed My Code Faster Than Ever! GitKraken Tutorial

I've used Git for over 10 years, but I never knew about half of the features in GitLens and GitKraken. Last week I sat down to explore them properly, and they completely changed how I handle branches, PRs, bugs, refactors, and code reviews. In this article, I'll walk through the specific features that now make my workflow feel smooth.

The Git Problem I Didn't Know I Had

I've been using Git for over a decade, and I thought I had a decent workflow. But last week I realised I was spending more time fighting Git than writing code. Switching branches, managing pull requests, and writing commit messages felt like friction. Then I sat down to properly explore GitLens and GitKraken, and it changed everything.

Worktrees: Working on Multiple Branches at Once

One of the first features that blew me away was GitLens Worktrees. Normally, if I need to work on a feature branch while a hotfix comes in, I'd have to stash changes, switch branches, and lose context. Worktrees let me have multiple branches checked out in parallel workspaces. I can run two branches at the same time, each in its own VS Code window, without any switching. It's like having separate copies of the repo that share the same Git history. This alone saves me hours of context-switching every week.

  1. Open the GitLens Worktrees panel in VS Code.
  2. Create a new worktree from your current branch or any other branch.
  3. Open the worktree in a separate VS Code window.
  4. Work on both branches simultaneously without stashing or switching.

Commit Graph: Drag-and-Drop Rebase

The Commit Graph in GitKraken isn't just a pretty visualisation. It's a fully interactive tool. I can drag and drop branches to rebase them instantly. No more typing rebase commands and dealing with conflicts in the terminal. I just grab a branch and move it onto another, and GitKraken handles the rest. It makes cleaning up my commit history trivial.

  1. Open the Commit Graph view.
  2. Drag a branch and drop it onto the target branch.
  3. Confirm the rebase action.

AI That Writes Commit Messages and PR Descriptions

Writing good commit messages takes time, and I often default to lazy ones. GitKraken's AI feature writes perfect commit messages for me based on the changes. It also generates pull request descriptions, saving me from having to summarise everything manually. I just review and accept. It's surprisingly accurate and keeps my history clean.

One-Click Branch Creation from Issues

Another friction point was creating branches from issues. I'd have to open Jira or GitHub, copy the issue number, switch to my terminal, and type a branch name. With GitKraken, I can create a branch directly from an issue with one click. It links the branch to the issue automatically, so I never have to switch contexts. This keeps my workflow inside VS Code.

  1. Open the Issues panel in GitKraken.
  2. Click on an issue.
  3. Select 'Create Branch' — the branch is created and linked automatically.

Launchpad for Smoother PR Reviews

Launchpad is a feature that helps manage pull requests. It shows all my open PRs, their status, and any blockers. I can quickly see which reviews are stuck and take action. It's like a dashboard for my code reviews, making it easier to keep things moving without digging through GitHub.

Visual File History and Cloud Patches

Visual file history lets me see every change to a file over time in a clean graph. I can click on any commit to see the diff. Cloud patches are another gem: I can create a patch from any set of changes and share it with my team via a link. No more attaching patch files or explaining which commits to cherry-pick.

A Workflow That Finally Feels Smooth

After a week of using these features, my Git workflow feels effortless. I'm not fighting the tool anymore. GitLens and GitKraken have removed the friction I didn't even realise was there. If you spend a lot of time in Git, I'd recommend giving the free trial a go. The Pro version adds the AI and Launchpad, but even the free GitLens extension in VS Code has Worktrees and the Commit Graph. It's worth exploring.

This video was sponsored by GitKraken, but everything I've shown is genuinely how I now use Git every day.

Tools used in this video

  • GitLens
  • GitKraken
  • VS Code
  • Jira
  • GitHub

Questions

What is GitLens?
GitLens is a VS Code extension that supercharges Git capabilities, adding features like Worktrees, visual file history, and a commit graph directly in your editor.
How do GitLens Worktrees work?
Worktrees let you check out multiple branches simultaneously in separate workspaces, so you can work on different tasks without stashing or switching branches.
Is GitKraken free?
GitKraken offers a free version with core Git features. The Pro version includes AI commit messages, Launchpad for PR management, and cloud patches.
Can I use GitKraken AI for commit messages?
Yes, GitKraken's AI can automatically generate commit messages and pull request descriptions based on your code changes, which you can review and accept.

Chapters

  1. 00:00 The Git Problem Nobody Talks About
  2. 00:18 Why My Workflow Was Wrong
  3. 00:42 Discovery That Changed Everything
  4. 01:04 Worktrees: Parallel Workspaces Explained
  5. 01:40 Running Two Branches at the Same Time
  6. 02:10 Commit Graph: Drag-and-Drop Rebase
  7. 02:45 AI That Writes Your Commit Messages
  8. 03:25 One-Click Branch Creation from Issues
  9. 03:55 No More Switching Between Jira & VS Code
  10. 04:20 Launchpad for PR Reviews
  11. 04:44 Visual File History & Cloud Patches
  12. 05:10 What I Love About GitLens + GitKraken
  13. 05:40 Who Should Use the Free vs Pro Version
  14. 06:10 5 Ways to Instantly Improve Your Git Workflow
  15. 06:35 Final Thoughts & Call to Action
Video description and links
I’ve been using Git for over 10 years… and somehow nobody told me about half of these features. Last week I finally sat down and explored GitLens + GitKraken PROPERLY — and it completely transformed how I handle branches, PRs, bugs, refactors, and code reviews. If you’ve ever felt like you spend more time fighting Git than actually writing code, this video will save you hours every week. In this video, I break down: 🔹 How GitLens Worktrees let you work on multiple branches at the same time 🔹 Why the Commit Graph isn’t just visualization — it’s a drag-and-drop superpower 🔹 How GitKraken AI writes perfect commit messages & PR descriptions 🔹 One-click branch creation from issues (no more switching to Jira/GitHub) 🔹 How Launchpad fixes PR reviews and blocks 🔹 Visual file history + cloud patches 🔹 The Git workflow that finally feels smooth This is a sponsored video, but everything I show is exactly how I now use Git every day — and honestly I’m annoyed I didn’t learn these features years ago. 👉 Try GitLens + GitKraken Pro (free trial + supports the channel) https://www.gitkraken.com 💬 Comment below: What’s your biggest Git pain point? Or share a GitLens trick you think I should try next! 🔍 SEO Keywords (Invisible to viewer but boosts ranking) gitlens tutorial gitlens review gitlens pro features gitkraken tutorial gitkraken review best git tools for developers vs code git extensions drag and drop rebase gitlens worktrees gitkraken ai improve git workflow git branch best practices vs code git tools developer productivity tools

This article was written from the video's description with the help of AI. Watch the video for the full walkthrough.

Related tutorials