The community's commit message currently has some problems
1. Many commit messages don't explicitly indicate what the code has modified, so we need to guess what it has done. 2. Some of the commit messages are associated with the issue on Github, while others are not, so it is difficult to trace the specific issue and pull request from a certain commit message. 3. The format of commit messages is not uniform. We need some conventions to help the commit messages become clean and tidy, so as to help developers and release managers better track issues and clarify the optimization in the version iteration. As Peter Hutterer puts it: "Any software project is a collaborative project. It has at least two developers, the original developer and the original developer a few weeks or months later when the train of thought has long left the station. This later self needs to reestablish the context of a particular piece of code each time a new bug occurs or a new feature needs to be implemented. " So,I combined the specifications of RocketMQ and other communities , drafted the Chinese version of the CommitMessage of the DolphinScheduler community. For the link, see: https://github.com/apache/incubator-dolphinscheduler-website/pull/146 If you have good suggestions, please communicate with me, thank you Best regards！ CalvinKirs
