# Unified Commit Message Brainstorming ###### tags: `Brainstorming` In an open-source organization, many developers will be working on each project. Therefore, maintaining order is important to ensure consistency of quality. Unified commit messages will result in a more organized way of keeping up with the project. This also will enforce a quality check of the commit as following the guidelines will make for more informative commit message. ## Advantages * Easy to read and get most of a commit message * Checks for quality message * Makes it easier for a new developer to read commit messages to get an overall view of the project ## Implementation We can write a bash script can be executed right before the commit is executed to check for format of message. If the format is not followed the commit is not complete until the developer edits the message to follow the format. ### Suggested Message Format ``` what - description ``` what: It will what will tell developers what you were working on (eg: feature, bug, checkpoint, etc) description: It will further expand to let us know what exactly we did