It's out of your way if you so desire, just squash and commit. What you pay the price for isn't satisfying git's whims; it's a better debugging or learning experience months or years down the line, which is something that git enables you to do.

A set of basic Git commands for everyday use is a good starting point and of course knowing a bit about the staging area and remote/upstream sources as well.

But if you move into the enterprise with multiple releases in active development and multiple teams, then it's hard to keep Git out of the way.

This is honestly where I think good git GUI tools help, and for those I go to Git Extensions, or did until I had to use a Mac for work.

I learned enough using it that I can work through most issues in a regular and natural way nowadays.