undefined | Better HN

0 pointstoenail1mo ago0 comments

What does that even mean? Multiple branches is a git feature.

0 comments

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

_fizz_buzz_1mo ago

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.

stingraycharles1mo ago

Yes, this is the obvious solution. Multiple agents working on multiple features should use feature branches.

Can’t believe how this whole AI movement seems to want to reinvent software engineering, poorly.

1 more reply

BatteryMountain1mo ago

claude can use worktrees.. so if you have a system with say 10 agents, each one can use a worktree per session.. no need to clone the the repo 10 times or work on branches. Worktreeees.

user342831mo ago

That has been implemented 10 years ago:

  git worktree add -b feature-2 ../feature-2

skydhash1mo ago

Even before git has the worktree feature, you could just clone the repo again (shallowly if it’s big).

PunchyHamster1mo ago

Sooooo git worktree. It's exactly that. One repository dir checked out in different places with different branches.

farouqjalabi1mo ago

Not quite, Gitbutler allows you to apply multiple branches to the code base at once. With codebases you will have multiple code bases not one.

for example: It allows me to test coworkers branches with mine without merging or creating new branch.

It has many features that makes it super easy to add patch to any commit in any branch

3 more replies

17186274401mo 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.

rimliu1mo ago

and worktrees too.

doublesocket1mo ago

Which Claude literally uses.

nacozarina1mo ago

‘Embrace, extend, extinguish.’

1 more reply

j / k navigate · click thread line to collapse

0 comments

arnvald1mo ago

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

_fizz_buzz_1mo ago

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.

stingraycharles1mo ago

Yes, this is the obvious solution. Multiple agents working on multiple features should use feature branches.

Can’t believe how this whole AI movement seems to want to reinvent software engineering, poorly.

1 more reply

BatteryMountain1mo ago

claude can use worktrees.. so if you have a system with say 10 agents, each one can use a worktree per session.. no need to clone the the repo 10 times or work on branches. Worktreeees.

user342831mo ago

That has been implemented 10 years ago:

  git worktree add -b feature-2 ../feature-2

skydhash1mo ago

Even before git has the worktree feature, you could just clone the repo again (shallowly if it’s big).

PunchyHamster1mo ago

Sooooo git worktree. It's exactly that. One repository dir checked out in different places with different branches.

farouqjalabi1mo ago

Not quite, Gitbutler allows you to apply multiple branches to the code base at once. With codebases you will have multiple code bases not one.

for example: It allows me to test coworkers branches with mine without merging or creating new branch.

It has many features that makes it super easy to add patch to any commit in any branch

3 more replies

17186274401mo ago

rimliu1mo ago

and worktrees too.

doublesocket1mo ago

Which Claude literally uses.

nacozarina1mo ago

‘Embrace, extend, extinguish.’

1 more reply

j / k navigate · click thread line to collapse