Pin slackify-markdown-action to specific commit for improved security #219
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
Contributor
|
Resolved by #221 |
Contributor
|
Huh, just realised we opened the same PR - sorry 😂 |
Member
|
I merged the newer one, my bad 😅 #221 |
Member
|
Thanks for the contribution 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR updates the action reference from a version tag (@v1) to a specific commit SHA (@698a1d4) for the action LoveToKnow/slackify-markdown-action.
This change follows security best practices recommended by GitHub: Security hardening for GitHub Actions
By explicitly pinning the action to a commit SHA, we avoid creating an "unpinnable dependency" for users consuming this action, as described here: Risks of unpinnable GitHub actions