If no one reads the git log, what's the harm in squashing small commits together? You don't lose the change history, just the separate commit messages that you don't think people will read.
Your developers want to have that information while they're bisecting, too.
And your auditors hate messy logs. Even if they don't realise it, or just don't complain to you about it, they do.
I have lost countless hours doing my job with colleagues who believe as you that the log is write-once-read-never. That is the ideal but it certainly isn't the reality, and when reality trumps it sucks to have followed the ideal.
2
u/mflood Jun 19 '15
If no one reads the git log, what's the harm in squashing small commits together? You don't lose the change history, just the separate commit messages that you don't think people will read.