@gromero thanks for initiating this conversation. I think this is an important topic to consider as the TVM contributions are growing. Having a guideline that the community has accepted is important so the reviewers could use as a reference to make decisions. But more importantly, I totally agree with @driazati that without some sort of tooling it is very challenging to enforce those guidelines and it would also put too much responsibilities on reviewers.
Looking briefly at @manupa-arm's suggestion, I think `Gitlint` seems to be a good option to adopt in TVM. Regarding the guideline/tooling, in my experience I see that people spend a good time on writing the PR description and usually PR description includes enough information to get a good understanding of the commit after merge. I wonder if there's a way to add the PR description as part of commit message (or make it the commit message). --- [Visit Topic](https://discuss.tvm.apache.org/t/commit-message-guideline/12334/14) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/bfbbaa0af151596ae88eede3839937d0d3f84a61d8676a5705cbf6d5a05151e4).
