Put Build/Test/Documentation changes in separate section of release notes #3173
Conversation
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
…otes This updates .github/release.yml so that it will combine build, test, and documentation changes into a separate section.
|
Decided not to use github's generate-release-notes feature, see #3174 |
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 updates .github/release.yml so that it will combine build, test, and documentation changes into a separate section.
I highly doubt this is the final iteration on the release notes generation, even in the very near future, but when you generate notes it takes the config from the tag being generated, so I want something better for the next release than having all the build/test changes under
Other Changes