Derek Smith

👍 seeing this as well.

I believe that feature PR #62 would help accomplish this.

Thank you for the report @philippeboyd It looks like what is happening is that when the change set is a part of the `Unreleased` category, the `BREAKING CHANGE` is not...

Can you provide 1. An example of the output you are seeing? 2. A small sample of the `git log` output? 3. The `.git-chglog/config.yml` you are using? It sounds like...

Another thing to consider is is you are using a "Merge Commit" or a "Squash and Merge". With a "Merge Commit", you will see an entry in `git log` for...

This is something that I have wanted as well. Every time I spin up a new project, I work around this. I will take a look at putting this in...

> @iedsapala you can set a `--next-tag` option like in the following command: > > ```shell > git-chglog --next-tag 'Unreleased' --output CHANGELOG.md > ``` > > The value inside `--next-tag`...

I believe that feature PR #62 would help accomplish this. This feature was released in version `v0.11.0` https://github.com/git-chglog/git-chglog/releases/tag/v0.11.0 Can you download the latest version and git a shot? ``` git-chglog...

Thank you for the write up on your idea. I've got some internal projects that have a mixed bag of message types and conventions from many contributors. Definitely helpful if...

This repo contains a configuration that follows the [Conventional Commit Spec](https://www.conventionalcommits.org/en/v1.0.0/) and generates a changelog with `Type`, `Scope` and `Subject` [`@goodwaygroup/lib-hapi-good-tracer` CHANGELOG](https://github.com/GoodwayGroup/lib-hapi-good-tracer/blob/master/CHANGELOG.md) Example Config changes: https://github.com/GoodwayGroup/lib-hapi-good-tracer/blob/master/.chglog/config.yml#L26-L31