On Fri, Apr 8, 2022 at 6:10 AM <jurgen_gjoncari@xxxxxxxxxx> wrote: > > I think that often commit messages are unnecessary. I propose that by default a user should be able to commit without a message. We prefer to encourage users to do the right thing by default and provide a commit message. We think that good software development practices should be encouraged and that providing a good commit message is good software development practice. > I don't think this would be a problem from the UX point of view, because a user could get a lot of information about a change, from the history of the GitHub repository, such as from the time of change, and seeing the diff. What about `git log --oneline`? > I think that making commit messages options wouldn't even be a problem for retro compatibility because the feature would remain still functional for those who would want to use it. Yeah, there is no compatibility issue because `git commit` already has an `--allow-empty-message` option, so empty commit messages are already supported. That's not a good reason to make it the default though.
