| Re: [sw360-dev] conventional changelog |
That’s a great idea! +1 Here is another example: https://github.com/fossology/fossology/blob/master/CONTRIBUTING.md#git-commit-conventions Cheers Roger From: Michael C. Jaeger [mailto:mcj@xxxxxx] Sent: Donnerstag, 8. Dezember 2016 17:50 To: sw360-dev@xxxxxxxxxxx Cc: sw360dev@xxxxxxxxxxx Subject: conventional changelog Hi, how about improving the commit style of messages using conventional changelog? It is just very simple: you have (as examples) fix(licenseinfo) correcting bug with GPL-2.0 missing feat(portlets) improving attachment list with datatable docs(docker) adding information to install compose separatedly style(vulnerabilities) changing indendation refactor(scheduling) moving out specific scheduling functionality test(projects) adding test for access by moderators chore(whatever) whatever more here: http://blog.thoughtram.io/announcements/tools/2014/09/18/announcing-clog-a-conventional-changelog-generator-for-the-rest-of-us.html Then, if we have sufficient coverage, we could go over and auto generate the release notes … Any doubts? - Michael