---
title: "Discussion on \"Git Worktree vs Branch: Why I Switched (And When You Shouldn't)\" | Hashnode"
description: "Discussion on \"Git Worktree vs Branch: Why I Switched (And When You Shouldn't)\". For years my mental model of Git was: \"branches are how you separate work.\" So whenever someone said \"use a worktree,\" I'd nod and quietly think isn't that just... another branch?\nIt's not. And after"
url: "https://hashnode.com/posts/git-worktree-vs-branch-why-i-switched-and-when-you-shouldn-t/6a11ae831a3cf7bffc250ff4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Git Worktree vs Branch: Why I Switched (And When You Shouldn't)](https://qcrao.hashnode.dev/git-worktree-vs-branch-why-i-switched-and-when-you-shouldn-t?utm_source=hashnode&utm_medium=feed)

For years my mental model of Git was: "branches are how you separate work." So whenever someone said "use a worktree," I'd nod and quietly think isn't that just... another branch? It's not. And after

May 23 · 3 min read · qcrao.hashnode.dev  
Read the article

-   [#github](https://hashnode.com/tag/github)
-   [#productivity](https://hashnode.com/tag/productivity)
-   [#devops](https://hashnode.com/tag/devops)
-   [#programming-blogs](https://hashnode.com/tag/programming-blogs)

## Written by

[qcrao](https://hashnode.com/@qcrao)

@qcrao

  
[View profile](https://hashnode.com/@qcrao)

Golang developer and indie maker.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
