Comment by marliechiller

What I've observed both in the comments here, and in my professional network is that people tend to fall into two distinct camps:

1) Those that use git like a crude autosave who then squash on merge

2) Those that prefer neatly wrapped, fully functional atomic commits

It seems those ideas are in direct opposition to one another with 1) being more common in my experience, perhaps as github naturally supports it better plus the fact that stacked commits can solve some of the problems 2) accounts for... but if I had a choice, 1) definitely makes more sense to me.