The seven regulations of an excellent Git commit communication
1. split topic from system with an empty range
From git make manpage:
Though not necessary, ita€™s a smart idea to start the commit message with a single small (lower than 50 characteristics) range summarizing the change, with a blank line right after which an even more complete definition. Continue reading “There are certain additional contexts in Git the spot where the distinction between matter series and the entire body kicks ina€”but do not require work effectively without the blank range around”