Recently I have been scavenging(xd) older PRs for some help related to an issue. I found it very difficult to understand or for that matter read the commit messages and understand what each commit did until I saw the changes in the
file changes section of that commit(PR).
@4ian, I don’t want to compare GDevelop to other organizations but I found Zulip’s concept of contribution guidelines to be very helpful. you may have a look here. At first, it was irritating and tedious to remember each of the commit rules but after I spent time working on some issues I realized why commit discipline is so important and helpful to the whole community.
I am not suggesting you impose the same rule but from your experience as a Software Developer, I am sure that you can impose similar “guidelines” for a commit message. It will not only help you (Since your repository will have cleaner commit messages & PRs) but also the novice contributors like me who want to learn how contributions are done to a codebase as a Software Developer.
Hope you understand Cheers!