Review code changes, open coding issues, publish release notes. Every one is ready to run, and you can adjust it in plain language.
Email a linked changelog draft for release review.
Get a changelog draft for your next release, with customer-facing updates linked to the work behind them and emailed for review.
Send changelog drafts to release owners for signoff.
Get a changelog draft in your chosen format, with uncertain changes flagged before the release owner signs off.
Post a draft of newly shipped changes on the release review issue.
You get a release changelog draft on your review issue, with clear features and fixes linked to the completed work behind them.
Keep the running changelog current when a version is approved.
Your changelog gains a new version section after release approval, and your editor gets a revised Markdown file to review.
Draft a linked changelog from the ready branch for release review.
Get a GitLab changelog draft in an issue, with changes grouped by type and linked to the work behind them.
Open a changelog review issue for each tagged release.
Your conventional changelog draft arrives in an assigned review issue. Your maintainer sees grouped changes and questions about unclear commits.
Keep published release notes in step with new version tags.
Your GitHub releases get readable notes as new tags arrive, with changes grouped by type and linked to commits.