Is your feature request related to a problem? Please describe.
Many commits to main have been committed without any message or with a messy unreadable message. Prior to the fork, Elasticsearch's commit messages are normally helpful for understanding the reasons for a given commit. Recently I noticed a severe degradation in this respect, in the OpenSearch repo. For example, see commits #829, #712, #818 (there are many more across the project, in opensearch-dashboards and various plugin repositories as well).
Describe the solution you'd like
In CONTRIBUTING.md add the following:
- Guidelines for writing good commit messages
- Requirement that the commit message is provided by the pull request author as part of the review process.
Additional context
Discussion in OpenSearch forum - https://discuss.opendistrocommunity.dev/t/missing-commit-messages-and-changelogs/
Is your feature request related to a problem? Please describe.
Many commits to main have been committed without any message or with a messy unreadable message. Prior to the fork, Elasticsearch's commit messages are normally helpful for understanding the reasons for a given commit. Recently I noticed a severe degradation in this respect, in the OpenSearch repo. For example, see commits #829, #712, #818 (there are many more across the project, in opensearch-dashboards and various plugin repositories as well).
Describe the solution you'd like
In
CONTRIBUTING.mdadd the following:Additional context
Discussion in OpenSearch forum - https://discuss.opendistrocommunity.dev/t/missing-commit-messages-and-changelogs/