4 ms·
(Author here) Yes, "release notes" is probably the appropriate term. The issue remains however: many projects generate their release notes from their git commit
by agateau 4y ago
(Author here) Yes, "release notes" is probably the appropriate term. The issue remains however: many projects generate their release notes from their git commit messages.
Regarding the conflicts issue, this is where tools like Changie can help: instead of modifying one single file, every merge adds its own separated entry. They are then assembled together at release time with `changie batch $VERSION` to produce a single file for $VERSION, then merged into the global changelog/release notes file with `changie merge`.
- kazinator 4y agoThis is something you could do with a commit hook which verifies that commit messages have a well-formed release notes entry section, and some seven line Awk script to combine them together when needed. If "every merge adds its own separated entry" and that doesn't refer to a special section of the commit message, you're doing something silly.