Repository navigation
ci(github): publish the tag annotation as notes - #10
Merged
Merged
Conversation
Every GitHub release so far carries the message of the tagged commit instead of the notes written in the tag annotation. actions/checkout fetches the tagged commit by its hash into refs/tags/<tag>, so the local tag has no annotation and gh release create --notes-from-tag reads the commit message. The workflow now fetches the annotated tag from origin before it creates the release.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitHub releases carry the message of the tagged commit instead of the notes from the tag annotation.
actions/checkoutfetches the tagged commit by hash intorefs/tags/<tag>, so the local tag has no annotation, andgh release create --notes-from-tagreads the commit message.The release workflow now fetches the annotated tag from origin before it creates the release.
Verified locally against
usherv0.2.0: a checkout-style fetch (git fetch --no-tags --depth=1 origin +<sha>:refs/tags/v0.2.0) gives acommitobject whose contents aredocs(repo): trim comments to the irreducible why; aftergit fetch --force origin refs/tags/v0.2.0:refs/tags/v0.2.0the object is atagand its contents are the release notes.