Use GITHUB_OUTPUT instead of GITHUB_ENV #5293
Merged
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
…UB_ENV We get a GITHUB_OUTPUT file per job, so we can feel confident that we are not overwriting variables written to the environment file
This way we can avoid overwriting variables in the global environment file
This comment was marked as off-topic.
This comment was marked as off-topic.
sgibson91
added
the
deployer:skip-deploy
|
I've confirmed this behaviour with a test workflow: https://github.com/sgibson91/testing-gh-actions/actions/workflows/multijob-output-file.yaml |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/12380566384 |
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.
GITHUB_OUTPUT is defined per job, as opposed to GITHUB_ENV that is global. By making this switch, we can be more flexible with reusing variable names