Release blog post script improvements #164
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
* Added explicit version argument in case one wants to create the blog post *before* the version has been released. * Fetch changelog from nodejs/node repo tag rather than master as it's more likely to have the correct changelog in place. * Leave [INSERT SHASHUMS HERE] if shasums could not be found on nodejs.org/dist. Will happen if one are creating the blog post before having released a new version of node. Refs nodejs#156.
phillipj
force-pushed
the
blog-post-changelog
branch
from
908dbdb
to
90283ca
Compare
6 tasks
phillipj
added a commit
that referenced
this pull request
Sep 17, 2015
Release blog post script improvements
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.
Addresses some issues raised with the release blog post scripts as is, discussed in #156.
[INSERT SHASHUMS HERE]if shasums could not be found on nodejs.org/dist. Will happen if one are creating the blog post before having released a new version of node.