Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 133 words in the discussion.

Trending Topics

#worktrees#branches#author#using#magit#old#due#agents#love#didn

Discussion (4 Comments)Read Original on HackerNews

brabelabout 1 hour ago
As the author, I have been using worktrees due to AI agents. And I love Magit but didn’t know it handles git worktrees so well! Thanks for letting me know, will start using magit to manage my worktrees immediately.
anilakar35 minutes ago
Worktrees are a must if you work with monorepos or just multiple branches in general. Lack of conventions (or rather the braindead defaults) and having to explicitly type out everything is what hinders adoption the most.

I've solved this by running thin bash script wrappers that keep the workflow SVN-like with a root directory that contains per-branch directories and a hidden bare repo).

black_knight6 minutes ago
I think my layout is similar to yours. What do your scripts do?

My branches end up in a tree structure (no shit!), and I rebase and merge up stream as changes land. I guess it could be more automated, but the only tedious part is remembering to remove old worktrees and prune the old branches

zrgabout 1 hour ago
I'm currently very much on the jujutsu train as the author also mentioned, i do recommend y'all give it a try