We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.bug
.bugfix
We have multiple developers and sometimes end up with changelog files like 123.bugfix.md and 123.bug.md.
123.bugfix.md
123.bug.md
I would love to have multiple fragment types grouped together.
Currently we use some CI task to verify no unknown fragments get committed, but I would love to see this as a feature.
Configuring multiple fragment types using the same name attribute just doubles the entry in the parsed changelog file.
name
The text was updated successfully, but these errors were encountered:
Thanks for the feedback.
This would be nice to be part of towncrier check CLI.
towncrier check
I don't understand what is the issue here?
What is the expected behaviour and what is the current behaviour?
I know that sometimes, for the same work ID / ticket ID / issue ID, I need to have separate bugfix entries.
I do a hack and have 123.bugfix and 123.1.bugfix ...
123.bugfix
123.1.bugfix
Right now, the full content of a fragment file is rewrapped.
What I can think of, is that if there is an empty new line, then a separate bullet entry is created in the final NEWS file
So for a file like 123.bugfix
Description of the first bugfix on a wrapped line. Another description of another bugfix.
The NEWS will be like
Bugfix ------ * Description of the first bugfix on a wrapped line. [#123] * Another description of another bugfix. [#123]
Sorry, something went wrong.
No branches or pull requests
We have multiple developers and sometimes end up with changelog files like
123.bugfix.md
and123.bug.md
.I would love to have multiple fragment types grouped together.
Currently we use some CI task to verify no unknown fragments get committed, but I would love to see this as a feature.
Configuring multiple fragment types using the same
name
attribute just doubles the entry in the parsed changelog file.The text was updated successfully, but these errors were encountered: