• 2 Posts
  • 5 Comments
Joined 2 years ago
cake
Cake day: August 12th, 2023

help-circle



  • Thanks for your feedback!

    Some thoughts:

    • You could configure your cliff.toml (generated with git-cliff --init) to ignore any commits that aren’t interesting to your users
    • You could use “squash merge” to the prerelease/staging/development branch so that you can commit without worry, and then only have your PR titles follow conventional commits (if the change is interesting to your users)

    I should probably add those to the blog.

    But yeah, I get preferring to write manual tailored changelogs. Personally I am just a little neurotic about single source of truth and a huge Git nerd. And I know that at least in this job, my users are neurotic enough to prefer completeness.