Same issue here

I've got same issue

@sooknarine is this happening with the non dockerized 1.15.0-rc?

@ferrarimarco unfortunately I've changed roles and no longer have access to the system that used your tool :( Perhaps @alicon or @arturalbov can try the non dockerized 1.15.0-rc?

Hi! Just wanted to a leave a note this is happening for me too!

I ❤️ this project (we're using it over on Agones, but there are some bugs in the 1.14.3 (issues going into the wrong release), that I'm hoping will be fixed in a new release, so I don't have to manually fix them by hand.

Any chance for a new release on this project, and a subsequent push to the new Docker image? It's been a year since release 😄

If you need a later Docker image that works - I just threw together a Docker image that runs the latest code in Github: https://hub.docker.com/r/markmandel/github-changelog-generator/

Mount your code to /project in the container, and you are good to go.

@markmandel
It seems that the --release-branch option doesn't work with your docker image. I tried to generate CHANGELOG for the not master branch but got weird CHANGELOG. It didn't match neither master branch nor branch I specified.

@dskrypko
My image may not be up to date with what is in github - it's not an automatic rebuild.

But you can likely take the Dockerfile and create your own, up to date image from it!

The version that is currently tagged as a docker image is in sync with the latest GCG version.

As soon as a new version is released, I'll update the image.

Actually since we saw no version in a few months, I may release an updated "latest" image pointing to the current master.

BTW we are tracking this issue in #644

Closing for now as we know we have to release an updated version.