ci: Use GITHUB_OUTPUT envvar instead of set-output command#141
ci: Use GITHUB_OUTPUT envvar instead of set-output command#141VenelinBakalov merged 3 commits intovmware:masterfrom arunsathiya:master
Conversation
|
@arunsathiya, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Signed-off-by: Arun <arun@arun.blog>
|
Should be signed now. |
|
@arunsathiya, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Signed-off-by: Arun <arun@arun.blog>
|
@arunsathiya, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
save-stateandset-outputcommands used in GitHub Actions are deprecated and GitHub recommends using environment files.This PR updates the usage of
set-outputto$GITHUB_OUTPUTInstructions for envvar usage from GitHub docs:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter