I was also in the habit of add and then commit -am until I realised the value of having a concise comment about what was done. Can't really have a long comment explaining everything that was done over lots of files, so best git practice is commit small and concise commits with comments often. :)
Thank you for stopping by! I am a full-stack developer that combines the power of entrepreneurship and programming to make the lives of programmers easier.
I was also in the habit of add and then commit -am until I realised the value of having a concise comment about what was done. Can't really have a long comment explaining everything that was done over lots of files, so best git practice is commit small and concise commits with comments often. :)
Definitely, committing often is much easier to revert afterwards. I hate it when I have to revert a very large commit for just a simple feature x.x