-
Notifications
You must be signed in to change notification settings - Fork 46
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
changelog lint example #14
Comments
|
About version_added: for modules there's ansible/ansible#69291, but for plugins there's nothing yet. And it's both test and filter plugins which have neither docs nor version_added. (And of course new roles.) |
Thank you for offering to do this.
I'm OK with this.
As you suggest, as GitHub label could work well. |
If I'm reading the code correctly, no. It checks the docs for validity, but not whether (or not) a changelog snippet was added for a change. |
SUMMARY
I think this repo should provide a snippet example how collections can/should lint their changelogs (if they use antsibull at least).
This started as a discussion in
#ansible-community
with @gundalow and @felixfontein, and I thought writing down my ideas here would be good.ISSUE TYPE
COMPONENT NAME
examples
ADDITIONAL INFORMATION
I think the following two checks should be executed:
antsibull-changelog lint
)Number 2 is rather easy, we have a tool for that. Number 1 is not.
I think we should only enforce changelog entries for parts of the repository (ain't nobody needs a changelog entry when we fix something in
.github/
), so I think the example should only care aboutplugins/
(the users then can easily extend that to their needs).On IRC it was mentioned that new plugins don't need a fragment -- correct, but at the same time nothing validates the
version_added
entry right now (will that change?) and (as also mentioned on IRC) filter plugins don't have that anyways.So the simple (lol) logic that we could go for today would be something like:
This won't catch everything, but it's IMHO a good enough 80% solution we should start wirh.
From experience in other projects, there should be a way to ignore this check. Either by adding a "trivial" label or by adding "no issue" somewhere in the commit/PR message. So that will make the above logic a bit more convoluted (at least when implementing it), but at the same time it's not strictly MVP.
The text was updated successfully, but these errors were encountered: