feat: openemr #6141 implement changelog #7033
Open
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
This implements a changelog generator using the github issues api for a given milestone release. It takes the milestone name, grabs all of the attached issues and prs that have been tagged with the release milestone and then converts it into a changelog. Issues are separated out for user/provider oriented issues, and issues that impact developer or core internals. It grabs the category of the issue and converts it into a changelog that follows the structure here: https://keepachangelog.com/en/1.0.0/ Everything is spat out to stdout so the release changelog version can be outputted. People generating the changelog release will need to copy the output and add it into the CHANGELOG.md file. An example of generating the changelog is as follows for the 7.0.2 release. ./command-runner -c CreateReleaseChangelog -m "7.0.2" > CHANGELOG.md Issues are grabbed in batches of 100 issues at a time up to 15 batches before the request will bail out automatically. Hopefully we don't have more than 1500 issues in a single release but if so this will need to be adjusted. If for some reason you need to use your own access token you can do so by specifying the -token parameter in the command.
Following the naming convention in https://keepachangelog.com/en/1.0.0/ this adds in the changelog for the 7.0.2 release. This is generated from our milestone issues.
Changed the release change log format to be the new command syntax.
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.
Fixes #6141 Following the naming convention in https://keepachangelog.com/en/1.0.0/ this adds in the changelog for the 7.0.2 release. This is generated from our milestone issues.
This also implements a changelog generator using the github issues api for a given milestone release. It takes the milestone name, grabs all of the attached issues and prs that have been tagged with the release milestone and then converts it into a changelog.
Issues are separated out for user/provider oriented issues, and issues that impact developer or core internals. It grabs the category of the issue and converts it into a changelog.
Everything is spat out to stdout so the release changelog version can be outputted. People generating the changelog release will need to copy the output and add it into the CHANGELOG.md file.
An example of generating the changelog is as follows for the 7.0.2
release.
Issues are grabbed in batches of 100 issues at a time up to 15 batches before the request will bail out automatically. Hopefully we don't have more than 1500 issues in a single release but if so this will need to be adjusted.
If for some reason you need to use your own access token you can do so by specifying the -token parameter in the command.