3 ms·
A change should be atomic. Whether the unit of change is a commit or a pull request that gets squashed is irrelevant, what matters is that the resulting histor
by SAI_Peregrinus 3y ago
A change should be atomic.
Whether the unit of change is a commit or a pull request that gets squashed is irrelevant, what matters is that the resulting history can be understood & bisected, that changes can be reverted, and that changes can be cherry-picked.
Work-in-progress changes should be able to be backed up. This doesn't have to happen in the version control system, but it can, and if it does this should not interfere with the goals of atomic changes.