-
Notifications
You must be signed in to change notification settings - Fork 121
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
Keep CHANGELOG updated with PRs? #148
Labels
Comments
@nicoddemus I think we have #66 and #73 already to get this in yeah? |
Definitely, my bad! 😁 Closing as duplicate of #66. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I suggest we keep the CHANGELOG updated as we merge PRs (even so far as making it part of the PR to update the CHANGELOG). Benefits:
No need to dig around to see which issues have been addressed since the last release, making the job of people making releases (mainly @tgoodlet lately) a lot easier.
Clear overview of what is about to be released at a glance.
We could adopt
towncrier
like pytest does, but given thatpluggy
does not have the same PR activity as pytest this is not necessary IMO.The text was updated successfully, but these errors were encountered: