git-chglog is only showing merges (I would like all commits)

[not-a-doctor-stromberg]

Hi! I am trying to generate a pretty change log for a project I don't personally develop for but am trying to support. Often, there are commits directly against the main branch that I'd like to include in the change-log. I don't have any filters on my commits. Am I missing anything?

Expected Behavior

git-chglog can include all commits, not just merges.

Actual Behavior

git-chglog seems to only include merges

Steps to Reproduce (including precondition)

Here's my setup

aaron@aarons-mbp pinenote-debian-recipes % git-chglog --init
? What is the URL of your repository? https://github.com/m-weigand/pinenote-debian-recipes
? What is your favorite style? github
? Choose the format of your favorite commit message <subject>
? What is your favorite template style? keep-a-changelog
? Do you include Merge Commit in CHANGELOG? Yes
? Do you include Revert Commit in CHANGELOG? Yes
? In which directory do you output configuration files and templates? .chglog

✨  Configuration file and template generation completed!
  ✔ .chglog/config.yml
  ✔ .chglog/CHANGELOG.tpl.md

Screenshot on This Problem (if possible)

Here is me showing git-chglog and then git log:

# git-chglog only shows the merges
aaron@aarons-mbp pinenote-debian-recipes % git-chglog v20221031..v0.3-beta1
<a name="unreleased"></a>
## [Unreleased]


<a name="v0.3-beta1"></a>
## [v0.3-beta1] - 2022-12-12
### Pull Requests
- Merge pull request [#5](https://github.com/m-weigand/pinenote-debian-recipes/issues/5) from SomeoneToIgnore/pin-custom-debs


<a name="v20221031"></a>
## [v20221031] - 2022-10-31
### Pull Requests
- Merge pull request [#1](https://github.com/m-weigand/pinenote-debian-recipes/issues/1) from not-a-doctor-stromberg/patch-1


[Unreleased]: https://github.com/m-weigand/pinenote-debian-recipes/compare/v0.3-beta1...HEAD
[v0.3-beta1]: https://github.com/m-weigand/pinenote-debian-recipes/compare/v20221031...v0.3-beta1
[v20221031]: https://github.com/m-weigand/pinenote-debian-recipes/compare/v0.1...v20221031


# git log shows all commits
aaron@aarons-mbp pinenote-debian-recipes % git --no-pager log v20221031..v0.3-beta1
commit 55bd0c34c32bc1338edf194e8f37fb893631e1be (HEAD -> mw_image, tag: v0.3-beta1, origin/mw_image, origin/HEAD)
Author: Maximilian Weigand <mweigand@geo.uni-bonn.de>
Date:   Mon Dec 12 08:52:35 2022 +0100

    use new xpp version

commit 40e0d35c77fca6d130a070c405615d7ce4cd1e7b
Author: Maximilian Weigand <mweigand@geo.uni-bonn.de>
Date:   Mon Dec 12 08:52:21 2022 +0100

    set ebc refresh_threshold=30

commit 7be2485aedecb7dcfd01db2d9b303d1262dc8097
Author: Maximilian Weigand <mweigand@mweigand.net>
Date:   Fri Dec 9 19:53:09 2022 +0100

    fix xournalpp deb name and use proper bookworm-modified mutter

commit 2159faea5ea2df87ac522bcf294cca9730c0645e
Author: Maximilian Weigand <mweigand@mweigand.net>
Date:   Thu Dec 8 19:51:55 2022 +0100

    another large round of updates

commit 175e5897bdedb5aeb04a7c4ef951e856d8095a02
Merge: b82f3d0 3ed014b
Author: Maximilian Weigand <mweigand@geo.uni-bonn.de>
Date:   Thu Dec 1 11:59:06 2022 +0100

    Merge branch 'mw_image' of github.com:m-weigand/pinenote-debian-recipes into mw_image

commit b82f3d09e2ed4f57b0dbb4d2c9a9c6b3021d1d83
Author: Maximilian Weigand <mweigand@mweigand.net>
Date:   Thu Dec 1 11:54:55 2022 +0100

    prepare the next iteration of the rootfs

commit 3ed014bc0db592561f162fd62d8e5cfb3b9f8762
Merge: 661803c af59a6e
Author: Maximilian Weigand <mweigand@geo.uni-bonn.de>
Date:   Thu Dec 1 09:28:17 2022 +0100

    Merge pull request #5 from SomeoneToIgnore/pin-custom-debs

     Do not allow updating patched deb packages

commit af59a6e2fe44b2be4b2dca84ff4a93c5b6e6a195
Author: Kirill Bulatov <mail4score@gmail.com>
Date:   Mon Nov 7 10:27:10 2022 +0000

    Do not allow updating patched deb packages

Your Environment

• OS: Darwin aarons-mbp.lan 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000 arm64
• git-chglog version: git-chglog version 0.15.1

[AlessandroMattiazzi]

When you choose the format of your favorite commit message in your setup you must use a different one, for example:

<<type> subject>