I don’t care how long it is, but knowing that many tools show only the first bit, it’s helpful if the message is phrased with the most important words near the beginning.
I’d much prefer to encourage rather than discourage descriptive commit messages. Even better if all commit messages mentioned more about _why_ the change is being made, not just describe the diff. But most important of all, NEVER forget the colon between the ticket number and the rest. I learned that the hard way :( -Owen On Tue, Oct 8, 2019 at 1:52 AM Ju@N <jujora...@gmail.com> wrote: > Hello devs, > > I've notice that, lately, not everybody is following the guidelines we have > highlighted in our Wiki under *Commit Message Format [1]*, specially the > first requirement: *GEODE-nn: Capitalized, 50 chars or less summary. *As an > example, out of the last 33 commits in develop, only 11 follow the 50 chars > max rule. > Even though I've always followed this "rule", I often find it hard to > provide a summary of the commit in less than 50 chars, that's probably the > reason why other people are just ignoring this part of the guidelines?. > Should we increase the maximum amount of characters from 50 to something > else?, should we add a hard check in order to automatically enforce the > rule?, should we delete the rule altogether?, thoughts?. > Best regards. > > [1]: > https://cwiki.apache.org/confluence/display/GEODE/Commit+Message+Format > > -- > Ju@N >
