ci: stop running untrusted PR code with secrets (pull_request_target -> pull_request)#87
Merged
Merged
Conversation
KABBOUCHI
approved these changes
May 31, 2026
bergben
approved these changes
May 31, 2026
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
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.
run-tests.ymlusedpull_request_targetwhile checking out the PR head SHA andrunning
npm install/npm run testwithsecrets.ALCHEMY_IDin the environment,so any fork PR could exfiltrate the secret. Switching to
pull_requestmeans fork PRsrun with a read-only token and no secrets. Please rotate ALCHEMY_ID as a precaution.