Comment by farouqjalabi
2 days ago
Gitbutler is backed by git. Gitbutler is essentially just ui for git which also allows you to have multiple branches. It isn't meant to replace git.
2 days ago
Gitbutler is backed by git. Gitbutler is essentially just ui for git which also allows you to have multiple branches. It isn't meant to replace git.
"Backed by" as in "running git under the hood", not as in "supported by the git organization". I'd probably use "powered by" in this case to avoid confusion
Not quite - it totally takes over your branching strategy and locks you into GitButler.
So.. worktrees?
What does that even mean? Multiple branches is a git feature.
I think it means parallel branches. Normally in git you can use one branch at a time. With agentic coding you want agents to build multiple features at the same time, each in a separate branch
Can agents not checkout different branches and then work on them? It's what people also do. I have a hard time to understand what problem is even solved here.
5 replies →
That has been implemented 10 years ago:
Does it checkout different branches at the same time, provides an in memory representation to be modified by another API, or does it to multitasking checkouts. The first thing is already natively in Git. I guess the others are innovation, although the second sounds unnecessary and the third like comedy.
Sooooo git worktree. It's exactly that. One repository dir checked out in different places with different branches.
5 replies →
Even before git has the worktree feature, you could just clone the repo again (shallowly if it’s big).
and worktrees too.
Which Claude literally uses.
‘Embrace, extend, extinguish.’
[dead]