Hey, I think it might be beneficial to have some guidelines around commit messages. I've seen a few commits on this project that have commit messages akin to "added code" rather than explaining what the commit contains. For example, when updating a prefab (e.g. forgetting to add before pushing code changes), something along the lines of "updated <prefabName> prefab to change <attributeName> attribute field" is more meaningful than "oops". Even without the autogenerated prefab/unity object code being nigh impossible to read in git, good commit messages give context about what to expect and help understand the changes made. I found this blog post really useful in constructing meaninful commit messages: https://chris.beams.io/posts/git-commit/ While I don't think it completely necessary to have full subject-body commit notes, at the very least having a meaningful commit subject line should be encouraged. What does everyone think?