Move to using GITHUB_OUTPUT from set-output #1079
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
maxxboehme
changed the title
astarche
reviewed
Aug 9, 2024
astarche
approved these changes
Aug 9, 2024
reckenro
reviewed
Aug 13, 2024
reckenro
approved these changes
Aug 13, 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.
What does this Pull Request accomplish?
Fixes #908
set-output is deprecated and there are warnings being logged in our CI build specifying so. Here is a github blog article about it, GitHub Actions: Deprecating save-state and set-output commands. I followed that article along with this github doc Workflow commands for GitHub Actions on how to use the new environment file correctly.
Why should this Pull Request be merged?
Move away from deprecated set-output to github's new suggested workflow using
$GITHUB_OUTPUTenvironment file.What testing has been done?
PR build