Ensure that annotated tag content is available #6
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.
As in the similar bisontrails/rules_kustomize#15, when preparing the notes to accompany a release that we issue upon receiving a pushed tag, we try to include both the subject and body of an annotation attached to the motivating Git tag. The actions/checkout GitHub Action does not fetch tag annotations by default, and coercing it to do so (in its current form) would require fetching all of the Git repository's history.
Work around this problem by continuing to fetch the repository history shallowly, but then fetching the repository's tags separately afterward. Doing so makes these annotations available.