-
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
Enforce fragment name structure #649
Comments
Thanks for the report which There is only support to check that Happy to review and approve a PR that adds this functionality. As long as it has documentation, tests and it does't break the existing tests, it should be good to merge. |
Didn't think of that, so I assume all of them, unless you have another idea?
Thanks
|
I think that We do some validation in You can give it a go and see what option is best for you. I can image that in the future we can go crazy and allow towncrier to call a project specific python method that will check that the ticket actually exists and is not already closed :) ... but that is for another time. Most of my errors with ticket ID is messing up the digits ... for example using We can keep it simple and add a regex. |
We're using Jira, and want all fragments to be named according to the issue numbering format (e.g.
ABCD-12345.feature.md
).Is there any way to configure towncrier to enforce the fragment file name somehow? (e.g. supplying a regex)
If there isn't one, I may be able to contribute it.
The text was updated successfully, but these errors were encountered: