Stop using deprecated set-output in GitHub Actions
#10588
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
Mab879
force-pushed
the
fix_save_set_state
branch
2 times, most recently
from
f1f3d96
to
16e0f4d
Compare
Per GitHub's blog post (https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) The `set-output` command will start to fail on June 1, 2023.
Mab879
force-pushed
the
fix_save_set_state
branch
from
16e0f4d
to
7d43e11
Compare
There was a problem hiding this comment.
@Mab879 thank you for the fix and for noticing this. I went through all workflow files and no instance of set-output is left.
I will merge it after you remove the triggering commit.
ggbecker
changed the title
set-output in GitHub Actionsset-output in GitHub Actions
Mab879
force-pushed
the
fix_save_set_state
branch
from
7d43e11
to
98f9ff9
Compare
The commit has been pulled. |
|
Code Climate has analyzed commit 98f9ff9 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 52.5% (0.0% change). View more on Code Climate. |
|
resolves #9679 |
Description:
This PR removes the usage
set-outputin our actions, plus a temporary commit to modify the content to trigger the CI.Rationale:
Our actions will start to fail on 1 June 2023.
See GitHub's blog.
Review Hints:
Please leave a comment before merging as I pull the content modification commit before this is merged to master.