Open DennisDobslaf opened 4 years ago
Self-answering my question:
here is the reason: https://github.com/churchtools/changelogger/blob/master/app/Commands/ReleaseCommand.php#L103
As a workaround one can insert <!-- CHANGELOGGER -->
at the top of a legacy CHANGELOG.md file.
Yes, the tool looks for <!-- CHANGELOGGER -->
and uses this as placeholder. I will document this. Thx for pointing this out.
Thanks for the tip, i had the same problem.
I used this tool on a repo with an existing but old CHANGELOG.md file with no common schema. This tool doesn't write to may legacy CHANGELOG.md on changelogger release but deletes the unreleased files.