-
Notifications
You must be signed in to change notification settings - Fork 122
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
allow specifying fragment types to consider as "valid" for towncrier check
#617
Comments
Hi Ben. Thanks for the report. I don't think I understand what is the request here. Sorry. Can you please give a step by step example with the current behaviour/result of Cheers |
Hi Adi. What I want is for
Then Also, I realized that the original issue incorrectly referenced the |
Let me see if I got this right. For example you have a branch called And on that branch you might have the following newsfragments
So with with just Is that correct ? Feel free to send a PR. As long as the PR has documentation and automated tests, we can have it merged. |
Yes, that's right, I will work on a PR |
Hello, it would be helpful to us to be able to specify within
towncrier check
which fragment types it should look for or not look for.Background on why this would be useful: We have automatic processes that create a newsfragment of a special type (
dependency_bump
) whenever a version of one of dependency libraries is updated. Even though these are real changes that we'd like to be noted in the changelog, we'd liketowncrier check
to assert that there are real human-readable newsfragments that explain the actual change, if any.I propose an additional, optional key to configured sections (
[[tool.towncrier.type]]
):ignore_on_check
. if this key is configured toTrue
,towncrier check
will ignore all newsfragments of this typeThe text was updated successfully, but these errors were encountered: