Closed tisonkun closed 3 months ago
Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️
Let me think of it ... It means other commits doesn't follow the conventional commit pattern so get skipped?
This should be the case.
After set filter_unconventional = false
and add { message = "\\[", group = "<!-- 0 -->🚀 Features" },
to commit_parsers
, it can select the proper range of commits.
Glad that this is resolved! Let me know if there is anything else.
Is there an existing issue for this?
Description of the bug
I'm wondering how RANGE selection works because a
release-1.17.0..release-1.18.0
selection on Flink give fewer result than expected.Steps To Reproduce
Expected behavior
The cliff output is:
... while the log diff tells:
Screenshots / Logs
No response
Software information
Additional context
No response