[quote="mehrdadh, post:14, topic:12334"] 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). [/quote] Speaking from previous experience, having the PR title and description become the commit message was super helpful. Many developers would use the PR description markdown support to write detailed PR descriptions, complete with sections, formatting, and links where needed, as well as having references to related bugs or work items included in the commit message by the tool. I know Azure DevOps supports this and I believe other platforms do also, but [it doesn't appear that is an option on GitHub](https://github.community/t/how-to-change-the-default-squash-merge-commit-message/1155) currently. From my experience it works very well, especially as projects get larger. Hopefully this is something that is added in the future.
--- [Visit Topic](https://discuss.tvm.apache.org/t/commit-message-guideline/12334/15) 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/ff6481b69a04825a467f2d079fec4b97e09c087a71b68e72383b64104a708549).
