I would also like to thank you for this great tool!
I would like to ask, do you guys suffer from having in the Release Notes Merge Requests that do not have as a target branch this branch that is specified as the parameter TARGET_BRANCH(for instance, 'master')? Like it is mentioned in the "How it works" section, today in the release notes are added Merge Requests within the time range defined by the last two tags. However, within this time range can be merged Merge Requests to different branches, and the issue is that in the Release Notes go all of the MRs and not only the one merged into TARGET_BRANCH.
This brings confusion, because I use the tool for the 'master' branch, but we have 'feature branches' for features that are under development and when we release in master, then in the Release Notes are displayed MRs from the feature branches which are not released actually.
Hi,
I would also like to thank you for this great tool!
I would like to ask, do you guys suffer from having in the Release Notes Merge Requests that do not have as a target branch this branch that is specified as the parameter TARGET_BRANCH(for instance, 'master')? Like it is mentioned in the "How it works" section, today in the release notes are added Merge Requests within the time range defined by the last two tags. However, within this time range can be merged Merge Requests to different branches, and the issue is that in the Release Notes go all of the MRs and not only the one merged into TARGET_BRANCH.
This brings confusion, because I use the tool for the 'master' branch, but we have 'feature branches' for features that are under development and when we release in master, then in the Release Notes are displayed MRs from the feature branches which are not released actually.
Thanks