SachoChangelogs written for users

Keep one fragment with each change, catch missing entries in CI, and compile a clean changelog when you release.

Write for users

Sacho never turns commit messages into changelog prose. You decide what changed for users and say it in their language.

Each unreleased entry is a Markdown file that follows its change through merges, rebases, cherry-picks, and reverts.

Hooks and CI can require fragments, validate their shape, and detect a generated changelog that has fallen out of sync.