About commit log style

[zuston]

Currently, the commit messages in the Curvine project do not follow a consistent style, which makes the history harder to read and maintain.

I suggest that we establish a unified commit message format to improve clarity and maintainability. We can take inspiration from best practices adopted by mature projects, such as Apache Gravitino, which uses prefixes like feat, fix, chore, and improvement to indicate the type of change.

This structured approach would help reviewers, contributors, and automation tools better understand the purpose of each commit.

For reference, a similar discussion has also taken place in the Apache Uniffle project.

[zuston]

cc @bigbigxu

[szbr9486]

Thank you for your suggestion, that's a good idea. We will standardize commit messages to follow industry best practices, making it easier for contributors to submit code.

[lzjqsdd]

Thank you very much for your suggestion, and the project has added commitlint for commit log style