-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Remove automated commits from release notes #1062
Comments
How about using release-drafter? we used it in cpp-linter org and it works well HERE. It can automatically label PRs, automatically classify them, and guess new versions. Finally, the publisher opens the Draft release and clicks to publish. I can draft a PR for reference If you are interested. UPDATE: GitHub Releases also support classifying release notes automatically by creating a |
the intent is to migrate towards using towncrier and/or scriv to produce the changelog fragments and using those to fill in the release |
Not sure where else to put this, but could you please keep
pre-commit.ci
anddependabot
commits out of the release notes? They make it very hard to see what actually changed, which makes my life as a dependency update reviewer much harder.For example, the 8.1.0 release notes contain the following line 12 times, vs 24 real changes (not counting 3 dependabots)
If you really want to keep them (though I doubt their usefulness in release notes), could you at least move them to a dedicated "Automated commits" block?
The text was updated successfully, but these errors were encountered: