[Refactoring the nRF520 mega-PR to follow the standards...]
I guess this has been bashed to death, but I am annoyed.
With long paths, the 50 characters limit on the first line
of the commit message makes it impossible to have any meaningful
explanation of what the commit actually does. Actually,
the limitation makes the commit messages unintelligible.
_Any_ change of increasing the limit to e.g. 72 characters?
the 50 chars is just the warning bound. You can go up to 70 until the commit message check fails on you. Longer will make GitHub break the commit message in the webview with the dreaded […] ;-).
My usual approach is to boil down the summary to the bare minimum within these constraints (even using just the module name instead of the full path) and go into details in the following lines of the commit message.
Martine and I discussed this over a PR a few months ago. The outcome was to update the Good Pull Request wiki page , which basically says what has just been discussed on this thread. Good to spread the word and share the link.