Seconding others here, what you're bringing up as distinct features of Gitbutler seems to just be stuff git can do.
- One local copy of a repo with multiple work trees checked out at once, on different branches/commits? Git does that.
- "Add a patch to any commit in any branch" I can't think of a way of interpreting this statement (and I can think of a couple!) that isn't something git can do directly.
Maybe it adds some new UI to these, but those are just git features. Doesn't mean it's a bad product (I have no idea, and "just UI" can be a good product) but these seem to be built-in git features, not Gitbutler features.
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
Seconding others here, what you're bringing up as distinct features of Gitbutler seems to just be stuff git can do.
- One local copy of a repo with multiple work trees checked out at once, on different branches/commits? Git does that.
- "Add a patch to any commit in any branch" I can't think of a way of interpreting this statement (and I can think of a couple!) that isn't something git can do directly.
Maybe it adds some new UI to these, but those are just git features. Doesn't mean it's a bad product (I have no idea, and "just UI" can be a good product) but these seem to be built-in git features, not Gitbutler features.
Yeah ur right, Gitbutler is just UI that makes it easier to do the mentioned stuff.
> for example: It allows me to test coworkers branches with mine without merging or creating new branch.
How is that not supported by worktrees? You are aware, that you can checkout commits?