`GH action` : Use GITHUB_OUTPUT instead of set-output in github actions
- Dominant language
- Java
- Stars
- 7
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
### Expected Behaviour
save-state and set-output commands used in GitHub Actions are deprecated and [GitHub recommends using environment files](https://github.blog/changelog/2023-07-24-github-actions-update-on-save-state-and-set-output-commands/).
This PR updates the usage of set-output to $GITHUB_OUTPUT
Instructions for envvar usage from GitHub docs:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter
### Actual Behaviour
### Reproduce Scenario (including but not limited to)
#### Steps to Reproduce
#### Platform and Version
#### Sample Code that illustrates the problem
#### Logs taken while reproducing problem
Contributor guide
Research direction
Search the repository's GitHub Actions workflow files for the deprecated set-output usage, then read the surrounding workflow steps and the linked GitHub documentation. Done means the affected outputs use GITHUB_OUTPUT and the workflows remain valid; no specific test file is mentioned, so validate the workflow configuration as far as the repository permits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100