[CI] Pin remaining actions to SHA for supply chain security#3070
Open
jbampton wants to merge 1 commit into
Open
[CI] Pin remaining actions to SHA for supply chain security#3070jbampton wants to merge 1 commit into
jbampton wants to merge 1 commit into
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
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.
Cleans up the zizmor.yml linter file.
https://github.com/apache/infrastructure-actions/blob/25ab499ef9c241b64a56860245e57c195baddec6/approved_patterns.yml#L279
r-lib/actions@a51a801
Did you read the Contributor Guide?
Is this PR related to a ticket?
[CI] my subjectWhat changes were proposed in this PR?
Pinning GitHub Actions to a specific commit SHA is the primary method to prevent supply-chain attacks. It guarantees that your continuous integration (CI) workflows execute the exact, unalterable version of code you have verified
How was this patch tested?
prek run -aDid this PR include necessary documentation updates?