# Alex Kladov - How I Use Git Worktrees (Highlights)
## Metadata
**Review**:: [readwise.io](https://readwise.io/bookreview/42641419)
**Source**:: #from/readwise #from/reader
**Zettel**:: #zettel/fleeting
**Status**:: #x
**Authors**:: [[Alex Kladov]]
**Full Title**:: How I Use Git Worktrees
**Category**:: #articles #readwise/articles
**Category Icon**:: 📰
**URL**:: [matklad.github.io](https://matklad.github.io/2024/07/25/git-worktrees.html)
**Host**:: [[matklad.github.io]]
**Highlighted**:: [[2024-07-26]]
**Created**:: [[2024-07-27]]
## Highlights
- # Undo the last commit, but keep its changes in the working tree $ git reset HEAD~ ([View Highlight](https://read.readwise.io/read/01j3prt2p1e6m7mffwg0pnm2a6)) ^750465362
- TL;DR: consider using worktrees not as a replacement for branches, but as a means to manage concurrency in your tasks. My level of concurrency is:
• `main` for looking at the pristine code,
• `work` for looking at my code,
• `review` for looking at someone elses code,
• `fuzz` for my computer to look at my code,
• `scratch` for everything else! ([View Highlight](https://read.readwise.io/read/01j3psr58qe04xt7gbdkn915z9)) ^750473785