Consider rendering the change file in a different way

[ematipico]

Consider rendering the change file in a different way

[dbanty]

Knope was originally using bullets for changes, but once we started supporting changesets, the generated changelogs became too hard to follow. Since you can put arbitrary Markdown for each change, you can put bullets and code blocks and other things that break the flow unless each change file has a header. There is still some Markdown you can put in changesets which will break the flow of the log (for example, headers), but it's much more flexible. In addition, headers usually result in links in their rendered form (like GitHub releases), so it's easy to point someone at a particular change when answering a question.

Perhaps, though, there's a way to go to a hybrid style, where complex changesets get their own little subsection, but simple changes are summarized as bullets in the top section? So conventional commits would always be bullets, and change files would be bullets as long as there was no content outside the header.

Changes

• feat: A feature
• fix: A quick fix

---
pizza: patch
---

## Fixed name of the pizza

---
pizza: patch
---

## Fixed size of the pizza

- Big pizzas were too small
- Small pizzas were also too small

> Can never have enough pizza!

Generated Changelog Section

Features

• A feature

Bug fixes

• A quick fix
• Fixed name of the pizza

Fixed size of the pizza

• Big pizzas were too small
• Small pizzas were also too small

Can never have enough pizza!

[ematipico]

This kind of approach would be amazing!