You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although towncrier create enforces valid fragment file names, creating a fragment file manually can sometimes lead to mistakes in the file name. It would be useful to include in our CI a check that all files in changes.d/ have valid fragment file names (excluding changelog-template.jinja of course).
Note we don't use towncrier check as we don't create fragments for small or non-user-facing changes.
The text was updated successfully, but these errors were encountered:
Can you please define what is considered a "valid fragment file name" ?
How else, other that via towncrier check are you expecting to have this implemented ?
Note we don't use towncrier check as we don't create fragments for small or non-user-facing changes.
You can create .misc or .ignore or '.hidden' fragments for small or non user facing changes.
In this way, you explicitly acknowledge that this branch doesn't need public release notes.
I would say that you should start using towncrier check.
It can help detect some errors in fragment file names.
Although
towncrier create
enforces valid fragment file names, creating a fragment file manually can sometimes lead to mistakes in the file name. It would be useful to include in our CI a check that all files inchanges.d/
have valid fragment file names (excludingchangelog-template.jinja
of course).Note we don't use
towncrier check
as we don't create fragments for small or non-user-facing changes.The text was updated successfully, but these errors were encountered: