@travis once it’s in master, complete agreed (and I think he says so in the talk).
For collaborative branches, a little work is required sure, but it’s hard to avoid unless you want to save all your merge conflicts to the end and have a bunch of “fix build” commits in there.
@travis For me, the benefits of a super helpful git log and blame workflow vastly outweighs the challenges of coordinating rebasing feature branches.
And over time it encourages us to be more mindful of the commits we create in the first place, making them cleaning and more coherent from the outset.
A Mastodon instance for Rubyists & friends