You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The motivation for this is that some tools (like GitHub releases) will not parse the message content of git tags as Markdown. GitHub releases does however support Markdown in the release body if you specify it manually, which can be done in CI.
So, to make that content available to other tooling, it would be ideal to optionally allow a separate file, such as RELEASE_CHANGELOG.md, which could be loaded directly
The text was updated successfully, but these errors were encountered:
frankdugan3
changed the title
Add option to output release-specific notes to CHANGELOG.md or an alternative file
Add option to output release-specific notes to RELEASE_CHANGELOG.md or an alternative file
May 25, 2022
The motivation for this is that some tools (like GitHub releases) will not parse the message content of git tags as Markdown. GitHub releases does however support Markdown in the release body if you specify it manually, which can be done in CI.
So, to make that content available to other tooling, it would be ideal to optionally allow a separate file, such as
RELEASE_CHANGELOG.md
, which could be loaded directlyThe text was updated successfully, but these errors were encountered: