I've used git-branchless in the past. It seems they have in common (suprise!) that branches are a distraction. And for a lot of workflows that has a lot less fr

I've used git-branchless in the past. It seems they have in common (suprise!) that branches are a distraction. And for a lot of workflows that has a lot less friction. The only thing is, a lot of version control users are only comfortable with branches. They can't think of an alternative with changes and patchsets.