Repository navigation
docs(readme): add SHA-pinning section for strict supply-chain policies - #7
Merged
Merged
Conversation
Adds a Quickstart-adjacent section explaining when and how to pin by commit SHA instead of tag. Matters for repos with a GitHub Actions policy that rejects tag-only refs (e.g., nerdalytics org rule that rejects `@v1` with 'Actions must be pinned to a full-length commit SHA'). Shows how to resolve the SHA both via the GitHub UI and via the gh CLI, and explains the exact-release vs floating-major tradeoff.
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
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.
Adds a Quickstart-adjacent section explaining when and how to pin this action by commit SHA instead of the tag
@v1.This matters for repos with a GitHub Actions policy that rejects tag-only refs (e.g., the nerdalytics org rule that rejects
@v1with 'Actions must be pinned to a full-length commit SHA'). The Marketplace "Use latest version" button hands out a tag-pin by default, which such repos cannot use.The new section covers:
gh api repos/.../commits/v1.0.1 --jq .shav1After merge, I'll cut
v1.0.2so the Marketplace listing picks up the new README.