chore: Change security-scan workflow to inherit secrets#134
Merged
bendiknesbo merged 1 commit intomainfrom Feb 10, 2025
Merged
Conversation
bendiknesbo
approved these changes
Feb 10, 2025
bendiknesbo
deleted the
pravindahal/chore/Change-security-scan-workflow-to-inherit-secrets
branch
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.
Since security scan workflow does not have access to GitHub token, it cannot download private submodules:
internalsubmodules github-workflow-supply-chain-security-validation#109While it only affects repos with go projects which use private/internal submodules, there are no downsides to having
this in every repo and it helps us keep things consistent.
This PR was automatically generated by a codemod implemented in the following PR: