-
-
Notifications
You must be signed in to change notification settings - Fork 849
What is the expected behavior of "between-tags"? #450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry @olleolleolle, but it'd be great if I can have an answer in the next couple days. I have some time-sensitive work that depends on the answer. |
I have not investigated @skywinder, do you know? @tduffield If you feel like poking through the history and deduce, it's all there. |
@olleolleolle I did look through the history briefly but I didn't see anything that answered my question super clearly. |
The |
I have to disagree. The between-tags is super useful for us (given my PR) in that we bump the version after every PR automatically but want the change log to reflect stable "releases." Im down if we want to deprecate that but having a way to specify section groupings is a must for us. |
The |
How can we achieve the functionality of |
The wording of the description of "between-tags" says that the "Change log will be filled only between specified tags". What I took that to mean was that if I specified tags, the section headers would combine the changelog for those tags.
For example, say I have the following tags: 1.2.[0-20], 1.3.[0-40], and 1.4.[0-10].
Now, lets say that I specify the following config:
I would expect the following:
But instead, I get the following:
Which of these two is the expected behavior?
The text was updated successfully, but these errors were encountered: