-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Document the equivalent of core.exportVariable for Docker actions #61
Comments
This is a great place!
Well, if you run javascript in the container you can call Note that docs for this are tracked in #57 and that this doesn't match exactly what |
Actually, scratch that - for now you should still use |
I can confirm this is working @damccorm , thanks for your help :) |
Awesome! I'm going to close here and follow up in #57 |
Closing since we have docs as of #105 (and I said I'd close 2 weeks ago 😳) |
Hello,
I'm sorry if this is not the best place to ask this, I've looked if there aren't already communities more "support-oriented", but as GitHub actions is still in beta, it seems this question hasn't been properly settled yet.
There's a
core.exportVariable
method which allows one to "export variables and secrets for future steps". However, I haven't found a way to do the same thing with aDocker
action.I (naïvely) tried adding something like
export MY_VAR='tada'
to theentrypoint.sh
file from the template, but I am unable to read the variable from a subsequent step.exportVariable
forDocker
actions? If so, I think it should be documented in the template. If not, it should also be documented 😄Thanks for your help!
The text was updated successfully, but these errors were encountered: