Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running CI for a branch on a fork does not have access to ENV or SECRETS #150

Open
2 tasks done
w3cj opened this issue Sep 15, 2023 · 2 comments
Open
2 tasks done

Comments

@w3cj
Copy link
Member

w3cj commented Sep 15, 2023

Describe the bug

From some initial research it looks like this might only be possible on private repos?

We need this option mentioned in the docs for private repos but I cannot find it on a public repo:

"Send secrets to workflows from pull requests - Makes all secrets available to the pull request."

Screenshots

No response

Reproduction

See current open PRs from a fork.

Logs

No response

Have you checked if this issue has already been raised?

  • I did not find any similar issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
@w3cj
Copy link
Member Author

w3cj commented Sep 15, 2023

Looks like the option on private repos might be called "Send secrets to workflows from pull requests" - referenced from here

@w3cj
Copy link
Member Author

w3cj commented Sep 15, 2023

Confirmed. In the github actions / secrets settings of the repo it mentions:

Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant