Refactor release cleanup step to use GH_TOKEN for authentication and improve error handling for release listing #107
Conversation
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
…improve error handling for release listing
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.
This pull request includes changes to the GitHub Actions workflow to improve the authentication process and error handling when using the GitHub CLI.
Improvements to authentication and error handling:
.github/workflows/build.yaml: ReplacedGITHUB_TOKENwithGH_TOKENto avoid conflicts withgh authand removed explicit authentication steps since GitHub CLI now usesGH_TOKENautomatically. [1] [2].github/workflows/build.yaml: Improved error handling by checking the success ofgh release listcommand and using conditional statements to handle potential failures gracefully. [1] [2]