> Best practices in git are to have frequent, small commits. I'd qualify that to only on a working branch - it's preferable to squash it all to 1 commit when m

> Best practices in git are to have frequent, small commits. I'd qualify that to only on a working branch - it's preferable to squash it all to 1 commit when merging upstream in order to make reverting painless if there is something wrong with the proposed change. Lots of small commits cause massive pain with git :( .