@james I dig the talk, just can’t get behind treating the history as mutable. Once code is shared, mucking about with commit IDs causes havoc to understanding what’s going on with the code.
@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.
@james thinking about merges and rebased again? 😊
A Mastodon instance for Rubyists & friends