octue / conventional-commits

Continuous deployment via Conventional Commits
MIT License
4 stars 0 forks source link

Improve upgrade instructions format in release notes generator #69

Closed cortadocodes closed 2 years ago

cortadocodes commented 2 years ago

@thclark says:

We need to talk about a convention/pattern for the upgrade instructions, because they need to be there but are too verbose as-is. Perhaps we could put them into <details> sections, where the first line of the breaking change note is the summary line?