secure CI for fork and trusted pull requests - #39
Open
erivaninan wants to merge 1 commit into
Open
erivaninan wants to merge 1 commit into
erivaninan wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
This PR updates the test workflow to handle fork and trusted pull requests separately.
OPENAI_API_KEYthrough the protectedcausal-agentenvironment.pull_requestinstead ofpull_request_target.actions/checkoutis updated from v3 to v4.The previous workflow used
pull_request_target, checked out code from a fork, and executed it with access to repository secrets. GitHub now blocks this pattern because it can lead to a "pwn request" vulnerability.The new workflow preserves regular unit testing for fork contributions while keeping API-backed tests available only in trusted contexts. (This PR should be merged before PR#36 so that its pytest workflow can run safely.)