Changelog script#53
Merged
Merged
Conversation
elegios
force-pushed
the
changelog-script
branch
from
9a908cb to
280e2ba
Compare
elegios
force-pushed
the
changelog-script
branch
from
280e2ba to
aa445b4
Compare
…hey're mentioned in the changelog
elegios
force-pushed
the
changelog-script
branch
from
aa445b4 to
b9eeffa
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I realized we could semi-automatically pull changelog information from PRs in each repo, or at least check that they've been considered for inclusion in the changelog. This PR adds a script that:
This means that I can just go through them in order and make sure all of them have been mentioned properly after merging PRs.
It also contains a list of PRs that are to be ignored, typically because it's not actually relevant to TreePPL itself, which are not printed in step 4 above.
In the future I imagine that PRs in
treeppl,treeppl-python, andtreepplrshould contain their own changelog items, and that this script could extract them automatically.mikingandmiking-dpplPRs should probably not have such things, since they're distinct projects, so they'd have to be examined manually.