Use process.env instead of core.exportvariable to set env
#138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MoChilia
temporarily deployed
to
Automation Test
GitHub Actions
Inactive
MoChilia
temporarily deployed
to
Automation Test
GitHub Actions
Inactive
YanaXu
approved these changes
Feb 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since setting environment variable for agent is required in current process, there is no need to use core.exportVariable. See https://github.com/actions/toolkit/blob/main/packages/core/README.md#exporting-variables, core.exportVariable is used to add environment variable to this step and future steps environment blocks.
The same implementation as Azure/login#384.