CI Test: Deprecating 'set-output' command #3757
Merged
JelleZijlstra merged 4 commits intopsf:mainfrom Jun 30, 2023
Merged
Conversation
Collaborator
|
Thanks! |
Closed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR replaced the deprecating
set-outputcommand used in thediff_shades_commentGitHub Action with latest GitHub supported method.See this GitHub blog about this deprecation.
The original method of setting variables directly using the
set-outputcommand has now been replaced with setting variables through theGITHUB_OUTPUTenvironment variable.After this fix, there will be no more warnings like this popping up when executing this CI test:
Checklist - did you ...
CHANGES.mdif necessary?