John T. Wodder II

@yarikoptic * The tag is created directly by the release workflow. I don't see an easy way to extract the changelog entries for use as the tag annotation message. *...

@yarikoptic The HTML anchor tags were added in scriv in response to https://github.com/nedbat/scriv/issues/46, which seems like the proper place to comment on your desire for getting rid of them.

@yarikoptic > trigger github making a release from an annotated tag What mechanism are you expecting to be used for this? As far as I'm aware, if no release notes...

@yarikoptic > changelog entries for annotation message -- just all new lines added on top from what it was before running scriv to compose changelog How exactly should I extract...

@yarikoptic Issues with entry separators reported to scriv at: https://github.com/nedbat/scriv/issues/62

@yarikoptic > > What mechanism are you expecting to be used for this > >could you please check how auto did that? I'm positive that auto just uses the GitHub...

@yarikoptic > it could well be -- how do they get then annotated git tags? The annotated tags are created in a separate operation from the GitHub releases.

@yarikoptic So what do you want the tag annotation messages to say?

@yarikoptic I've successfully tested the requested changes in https://github.com/datalad/temp-release-devel. The [latest release](https://github.com/datalad/temp-release-devel/releases/tag/0.0.2) includes emoji in the category headers (also in [the CHANGELOG](https://github.com/datalad/temp-release-devel/blob/master/CHANGELOG.md)), and the lines are not broken. GitHub doesn't...

@yarikoptic As I understand scriv, `new_fragment.md.j2` is only used by `scriv create`, which we don't use (favoring automatic snippet generation instead).