bureaucracy: PRs should have a CHANGELOG entry #2386
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r10s
changed the title
r10s
force-pushed
the
r10s/update-changelog-handling
branch
3 times, most recently
from
3f49c8c
to
62ef33a
Compare
r10s
changed the title
r10s
force-pushed
the
r10s/update-changelog-handling
branch
from
62ef33a
to
80df0b2
Compare
r10s
force-pushed
the
r10s/update-changelog-handling
branch
from
80df0b2
to
9b1fa14
Compare
zeitschlag
approved these changes
Nov 5, 2024
Co-authored-by: zeitschlag <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this PR updates some guidelines, to the discussed idea of adding CHANGELOG entries sooner.
background is that the "list of recent" PR is unreliable and things easily get overseen. same for creating milestones
for that, which was also not working in practise.the CHANGELOG approach has the advantage of having the incentive of easier releases at the end :)
it is known, there are tools forcing CHANGELOG entries, however, we decided to try without first and see how it goes
nb: that this "compliance" or "bureaucracy" PR actually removes lines is also a good sign :)