Populate GitHub release with relevant data #392
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
nre-ableton
force-pushed
the
nre/master/github-release-info
branch
5 times, most recently
from
1c4aec7 to
120598c
Compare
|
FYI, I've tested this out with a forced deployment (while commenting out the branch forwarding and immediately deleting the tag/release after it was published). The result looks like this:
|
nre-ableton
force-pushed
the
nre/master/github-release-info
branch
from
120598c to
0732bab
Compare
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 PR sets the release title to the version number, and the release body to a list of commits since the last tag along with their corresponding SHA1 hashes.