Hash-pin licensee/setup-licensed action #111
Open
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
2 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.
TLDR
Hash-pin an action in a workflow.
Description
Hash-pin an action in a workflow.
Fixes
SECVULN-22904
Type of change
Workflow update. No behavioral changes.
How Has This Been Tested?
N/A
PCI review checklist
If applicable, I’ve documented a plan to revert these changes if they
require more than reverting the pull request.
If applicable, I’ve worked with GRC to document the impact of any changes
to security controls.
Examples of changes to controls include access controls, encryption, logging,
etc.
If applicable, I’ve worked with GRC to ensure compliance due to a
significant change to the cardholder data environment.
Examples include changes to operating systems, ports, protocols, services,
cryptography-related components, PII processing code, etc.
If you have any questions, please contact your direct supervisor, GRC
(#team-grc), or the PCI working group (#proj-pci-core). You can also find more
information at
PCI Compliance.