-
Notifications
You must be signed in to change notification settings - Fork 13
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
Using fork of ci-action fails #267
Comments
Sam issue if it's a PR in the seL4 organization, see https://github.com/Hensoldt-Cyber/camkes-vm-examples/actions/runs/4617763392/jobs/8164399372?pr=5
|
We could try to make Testing action code works differently and depends on what kind of action it is. If it is a docker action you need to build and deploy that container manually somewhere and modify the workflow file in the repo you are testing to point to that new container. You'll usually want to change the test trigger to This is not anything to do with the action setup in ci-actions, it's just how GitHub actions work. I don't think there is anything to implement or fix here, even if it is annoying to do. What I could try to do is write up a small doc that has instructions on how to do this, because it is absolutely true that this all a bit complex. |
In Hensoldt-Cyber/camkes-vm-examples#5 I want to test with a custom ci-action and use "Test with: Hensoldt-Cyber#3" but this fails. In https://github.com/Hensoldt-Cyber/camkes-vm-examples/actions/runs/4617639833/jobs/8164126406 is says
Why can't it fetch this PR, it is really
GIT_DISCOVERY_ACROSS_FILESYSTEM
that must be set?The text was updated successfully, but these errors were encountered: