Skip to content
Discussion options

You must be logged in to vote

That limitation is described in the documentation, and it's the same as for pull_request events:

With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository. The GITHUB_TOKEN has read-only permissions in pull requests from forked repositories. For more information, see "Automatic token authentication."

It's a matter of security, because the workflow is used as it's at a temporary merge commit, and could've been modified maliciously.

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by aptalca
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Actions Build, test, and automate your deployment pipeline with world-class CI/CD
4 participants