Skip to content

Adapt pull request workflow to work properly for PRs from forked repositories #168

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

Closed
OptimumCode opened this issue Jul 26, 2024 · 0 comments · Fixed by #169
Closed

Adapt pull request workflow to work properly for PRs from forked repositories #168

OptimumCode opened this issue Jul 26, 2024 · 0 comments · Fixed by #169
Labels
repository enhancement Changes to make the repository look better

Comments

@OptimumCode
Copy link
Owner

As I recently discovered the secrets are not available in workflows triggered from forked repositories:

With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository.

https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow

There is a suggestion on what can be done to mitigate this.

We need to split workflows into parts that execute code from forked repositories (which don't need access to secrets) and that process the results (e.g. publishing coverage report)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repository enhancement Changes to make the repository look better
Projects
1 participant