Creating a worktree in Git - Why You Should Know This

The Big Idea

What if you could work on two features at once without losing your place or risking mistakes?

The Scenario

Imagine you are working on two different features in the same project. You need to switch back and forth between branches frequently. You try to do this by changing branches in your single project folder.

The Problem

Switching branches manually means you lose your current changes or have to stash them every time. It's slow and risky because you might forget to stash or accidentally overwrite work. Managing multiple features becomes confusing and error-prone.

The Solution

Creating a worktree lets you have multiple working directories linked to the same repository. Each worktree can be on a different branch, so you can work on multiple features side-by-side without switching or losing changes.

Before vs After

✗ Before

git checkout feature1
// work
git checkout feature2
// stash changes or risk conflicts

✓ After

git worktree add ../feature1 feature1
cd ../feature1
// work on feature1
cd -
git worktree add ../feature2 feature2
cd ../feature2
// work on feature2 simultaneously

What It Enables

You can work on multiple branches at the same time, speeding up development and reducing mistakes.

Real Life Example

A developer can fix a bug on the main branch while simultaneously developing a new feature on another branch, without losing progress or switching back and forth.

Key Takeaways

Manual branch switching is slow and risky.

Worktrees create separate folders for different branches.

This allows parallel work without conflicts or lost changes.