-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fix GH actions to work on forks! #402
Comments
On other repos, the fork contribution workflow is supported disabling all actions where permissions are required. For instance, push a docker image to the registry. See example: https://github.com/Kuadrant/limitador-operator/blob/main/.github/workflows/build-images-for-tag-release.yaml#L174
Why do you need to test if some secret is nil additionally? Is it not enough to test repository owner? Or even |
Don't focus on that... it doesn't even fix the issue... for some reason the |
I used github context dump step to see the value of - name: Dump GitHub context
env:
GITHUB_CONTEXT: ${{ toJson(github) }}
run: echo "$GITHUB_CONTEXT" It turns out that If I am not mistaken on your goal, the way to achieve that is like this for jobs being run on pull requests
Fossa license scan job is the only one job that runs when PR's are open with a guard like |
Our actions are currently broken. I'm unsure to what extent, but at least the FOSSA one still is, despite me trying to get it working.
See here for the latest type of failure. I reverted that, but now that means that again, on forks and PR of forks, that step will be broken!
I don't know whether its the action itself, or what it is... but this whole
secrets
stuff is broken beyond belief! It was a mistake to put all this config stuff in the repo alongside the code, blame GH... but what can we do? Should we move all our CI out of this mess? I've searched, but can't seem to find what are the proper patterns to support this fork contribution workflow, which... is actually how GH is supposed to work, but... not GH actions? What am I missing?The text was updated successfully, but these errors were encountered: