I know there are tools for this purpose (just formatting), but the specifics still need to be modified by the Committer (at merge time), so it is recommended to add the corresponding tool to check. If we simply rely on verbal or article conventions, we will spend a lot of time on this. Also, some basic formatting is almost already standard, and there is no need to stress it again.
Best wishes?? Calvin Kirs On 10/7/2022 01:07??TaoZex<[email protected]> wrote?? +1 Very important advice, preferably also updated on the website. It will help people who are new to the community to submit PR better. Best Regards, Bingye Chen ------------------ ???????? ------------------ ??????: "dev" <[email protected]>; ????????: 2022??10??6??(??????) ????10:59 ??????: "dev"<[email protected]>; ????: [DISCUSS] Standardized commit message Hi, all At present, the commit message format of our committer and PMCs is not uniform when merging code. I expect to be able to standardize commit message, The advantages of standardization: 1. Easy to quickly browse the commit log 2. Supports filtering commits (such as document changes) for quick information search 3. Change logs(Release) can be generated directly from the commit log. For details, see https://github.com/apache/incubator-seatunnel/issues/3011 -- Best Regards, Zongwen Li
