Should we start mandating that Pull Requests update the CHANGELOG? #1504
Unanswered
tomchristie
asked this question in
General
Replies: 1 comment 3 replies
-
Personally don't mind experimenting with that for a bit. :-) Right now maintainers have to go through the git history and decide which PRs should go into a release and which shouldn't. I don't think the cumbersomeness of it is a problem, but it certainly is a bit risky — might miss important PRs, not see what's breaking and what's not, etc. How would we enforce this new policy?
How do we feel about something like Reno? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So, I've been thinking that we might have reached a point in our workflow where we'd like pull requests to also include a relevant CHANGELOG entry.
We're pretty low churn at this point, plus GitHub's UI now makes it super easy to resolve the sort of simple merge conflicts that CHANGELOG-entries-in-PRs often introduce.
If we forced pull requests to include CHANGELOG entries, then...
(Note that refactors and docs changes don't require CHANGELOG entries, since they're not behavioural changes.)
Beta Was this translation helpful? Give feedback.
All reactions