> The reason you are asving this is because git is so aweful at managing many tiny commits. So you work around it by squashing. I don’t think the real issue is

> The reason you are asving this is because git is so aweful at managing many tiny commits. So you work around it by squashing. I don’t think the real issue is Git’s features. Even if Git had whatever additional features you wish it had, it still doesn’t change the fact that a history of typos and stupid mistakes isn’t very useful to anybody (especially in the long-run), and hence there is little or no value in preserving it; while a faked history which breaks the change down into logical steps does have some real long-term value, in terms of helping anyone who needs to review and understand the change in the future