Repository navigation
docs: fix tag verification command in Action guide - #28
Merged
Merged
Conversation
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.
What changed?
Correct the tag-verification command in the GitHub Action guide. It now matches the README's valid
git fetch --tags originand annotated-tag resolution command.Why?
The prior
gh api ... git fetchexample was not executable and could not resolve the release commit SHA.Tests
npm testnpm run lintnpm run typechecknpm run buildgit diff --checkAlso ran the documented command;
v0.2.4^{commit}resolves to30d08c644114399c0ee0257954205b97fb9fcbd3.Shopify source/evidence
N/A; documentation-only command correction.
Security/privacy impact
N/A.
Documentation impact
Updated
docs/github-action.md.