>> how much time would you have wasted writing good commit messages? or time wasted writing unit tests, or pull requests, or code reviews? (1) It's about effe

>> how much time would you have wasted writing good commit messages? or time wasted writing unit tests, or pull requests, or code reviews? (1) It's about effective communication. Why do developers appear to care so much about the way we write our code but not the artifacts that form it's ecosystem (and have a much wider audience)? (2) If you're going to write a commit message, why not take the incrementally very tiny extra bit of time to do it right? If you don't really care about the quality of your commit messages I'd suggest stop requiring them and allow blank commits. IMO this is preferable over the false impression that a garabage commit history provides any value.