Document the equivalent of core.exportVariable for Docker actions about toolkit HOT 5 CLOSED

I can confirm this is working @damccorm , thanks for your help :)

from toolkit.

Awesome! I'm going to close here and follow up in #57

from toolkit.

Closing since we have docs as of #105 (and I said I'd close 2 weeks ago 😳)

from toolkit.

I'm sorry if this is not the best place to ask this

This is a great place!

Is there an equivalent of exportVariable for Docker actions?

Well, if you run javascript in the container you can call exportVariable with this library and it should work. Otherwise, you should be able to replicate what we do in our exportVariable function by doing something like echo "::[set-env name=FOO;]BAR", which will set FOO=BAR in the env for future steps.

Note that docs for this are tracked in #57 and that this doesn't match exactly what exportVariable does yet because of #59

from toolkit.

Actually, scratch that - for now you should still use echo "##[set-env name=FOO;]BAR". Note though, that we're going to replace ## with :: in the near future and ## will be (gracefully) deprecated.

from toolkit.