v0.12.11 release post #551
Merged
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
Member
|
Good to hear it work 👍 I'll take a look at fixing the header you mentioned |
phillipj
added a commit
that referenced
this pull request
Mar 14, 2016
- handle @author parsing when using . instead of , in the release version header - ensure ### prefixed Notable changes header - bumped changelog-url version too handle new v0.10.x releases Refs: #551 (comment) Fixes: #553 (comment)
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.
@phillipj FYI this is my first use of the release post script for <v4 and it worked like a charm, thankyou! I manually edited the ChangeLog text to be more markdowny but it was mostly fine as is. One tweak that could be made is that
Notable changes:doesn't come with a###on <v4, if we had that automatically added then the rest would be fine to go as is (although I'd personally still want to make the changelog more markdowny but that's not strictly necessary).