←back to thread

128 points nvader | 1 comments | | HN request time: 0.001s | source
Show context
michaelbuckbee ◴[] No.46190907[source]
The usage of worktrees is seeing a big comeback in the era of AI assisted coding.

I have a script that takes Github issues and spins them out into their own worktrees with corresponding stack.

I can then run individual instances of Claude Code in each and easily flip between them.

replies(2): >>46191265 #>>46202702 #
1. jackschultz ◴[] No.46191265[source]
Same. Never used worktrees before, but mapping a worktrees to tickets I’m assigned to for Claude to work on is really great.

Heck with the ai, I even have it spin up a dev and test db for that worktree in a docker container. Each has their own so they don’t conflict on that front either. And I won’t lie, I didn’t write those scripts. The models did it all and can make adjustments when I find different work patterns that I like.

This is all to the point of me wondering why I never did this for myself in the past. With the number of times I’m doing multiple parts of a codebase and the annoyance of committing, stashing, checking out different branch and not being able to go more quickly between when blockers are resolved.