Product discovery: increase commit message visibility in merge requests
Commit messages are can be an incredibly valuable asset that is developed over many years that describes why code is what it is. We minimize them visually by default by only showing short messages by default, and hide them in a tab that is rarely seen, and thereby contribute to the problem.
Commit messages should be treated as a first part of the code review process, with greater visibility and consideration as an important artifact of the merge request.
- Design which can be implemented in following release which makes the squash commit message visible before merging when squash and merge is enabled, and the foundation for: #47149 (closed)
- Direction for increasing the visibility of commit messages during code review that could allow comments to be added to commit messages