Add GitHub Actions workflow to automate release creation on tagged pushes #7209
Conversation
This file contains 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
This workflow automates the release creation process whenever a new tag is pushed to the repository. It checks if a release for the tag already exists and creates one if it doesn't, enhancing the release management and streamlining the deployment process.
Refactor the script to improve checking for existing releases by tag. Return an object instead of using core.setOutput to streamline the workflow logic. Also, set result-encoding to string for better compatibility.
Corrected the output handling in the 'release-on-tag.yml' workflow file by changing 'result-encoding' to 'outputs'. This ensures that the step correctly checks if a release exists before attempting to create a new one, thereby avoiding potential errors during the release process. Added a blank line for better readability.
Refactored how the release_exists output is set to be compatible with GitHub Actions syntax. This ensures the workflow reliably detects if a release already exists, improving the robustness of the release process.
Improved the way outputs are managed in the 'check_release' step by returning values instead of direct assignments. This change ensures better handling of release existence checks and improves code readability. Added 'result-encoding' to specify string encoding for results.
Refactored the release existence check to return a simple boolean
string ('true'/'false') rather than an object. Added a step to print
the release existence status for debugging purposes. This ensures
correct conditional evaluation and aids in troubleshooting workflow
issues.
The release-on-tag workflow has been streamlined by eliminating the redundant steps checking for existing releases. This change reduces complexity and speeds up the release process by directly creating a release on every tag push without prior existence verification.
|
Hi, I've noticed that the CI tests are failing on this pull request. I've only added a GitHub Actions workflow file to automate release creation on tagged pushes and haven't modified any application code or tests. I checked the CI logs but couldn't identify how my changes might have caused the failures. It seems the test failures might be unrelated to this PR. Could someone please take a look or advise me on how to proceed? Thank you! |
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.
What did this pull request do?
This pull request adds a GitHub Actions workflow that automatically creates a GitHub release whenever a new tag is pushed to the repository. This automation ensures that every tagged version has a corresponding release, simplifying the release management process and making it easier for users to access specific versions of the GORM library.
User Case Description
Motivation
Currently, releases may not be consistently created for every tagged version, which can lead to confusion for users looking to download specific versions of GORM. Automating the release creation process ensures that releases are always up-to-date with the latest tags.
Implementation Details
.github/workflows/release-on-tag.yml'*'), i.e., when a new tag is pushed.actions/create-release@v1: Creates a new GitHub release based on the pushed tag.Benefits
How did you test this code?
Additional Notes