D22973: docs: introduce commit message guideline
Roman Gilg <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kwin |
|---|---|
| Message-ID | <[email protected]> |
romangg added a comment. In D22973#509896 <https://phabricator.kde.org/D22973#509896>, @zzag wrote: > In D22973#509887 <https://phabricator.kde.org/D22973#509887>, @romangg wrote: > > > I don't really follow this argument > > > The prefix is not part of a proper sentence. It has a bit special purpose, we just use a colon to separate it from the rest of subject line. Therefore, we can follow our own rules. Colon is just a stylistic choice I guess. That's the same usage as in Angular project. Still they decided to use lower case. > I prefer to capitalize the "subject" because this way it's much easier to spot where the actual short description of a change begins when browsing git log. What type of change it is (and scope) is just as important as the subject when browsing the log. REPOSITORY R108 KWin REVISION DETAIL https://phabricator.kde.org/D22973 To: romangg, #kwin Cc: davidedmundson, yurchor, anthonyfieroni, zzag, ngraham, kwin, LeGast00n, sbergeron, jraleigh, fbampaloukas, GB_2, mkulinski, ragreen, jackyalcine, Pitel, iodelay, crozbo, bwowk, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, hardening, romangg, jensreuterberg, abetts, sebas, apol, mart