Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork304
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
I am trying to set-up commitizen as my standard toolchain for commiting and publishing. I like it pretty much as it is a handy all-in solution. However, I have some trouble setting ub the changelog generation. I encounter the problem, that the header line is duplicated. Does anybody experience this issue and knows how to resolve ? Another problem is that generated changelog runs into an error with the trailing-whitespace check. However, this can be overcome with retry option even this is still somewhat weird. |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 4 comments 1 reply
-
That's strange, which version are you running? |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Latest version 4.9.1 The issue seems to occur when I do a Here is my Jinja template (sightly modified to include the commit tags on GitHub) |
BetaWas this translation helpful?Give feedback.
All reactions
-
I did some further investigations. I wonder if this is causes by the difference between complete new changelog and incremental. However, I think it is desirable to fix that to allow to maintain a headline in the template without running into the trouble this headline to be duplicated during incremental changelog updates. |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
I think I am right :-) To overcome I guess an easy improvement would be to provide the changleog generation mode as additional variable. This would allow to control in the jinja template if an headline is generated or not. For incremental changlogs then the headerlines (or footer lines if desired) would not be generated. Another option: |
BetaWas this translation helpful?Give feedback.
All reactions
-
So, tried it. One additional line (inserted between lines 247 and 248 in /commitizen/commands/changelog.py ... and following change in the template does the job. |
BetaWas this translation helpful?Give feedback.