ci: Improve create-release action #46
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
Now it extracts the info for the latest release through the changelog.
vinisalazar
approved these changes
Jan 21, 2021
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.
Changes made:
Something that bothered me seeing the releases for your repo was that it usually contained the default text, requiring you to manually go and edit the release so it contains something meaningful, which is a bit tedious.
See the current release (v0.1.22) for reference, which I believe you forgot to edit hahah.
Now I added some bash magic to the action so it extracts the info for the latest release through the changelog file. Basically an awk extraction that gets the text between the lastest and the second-to-latest tag.
I've tested it and it's working as intended. As long as you keep the same format for the changelog, should be all good. Just so you know how it would look, I used your changelog on a private repo and the action created this for v0.1.4:
