Deploy Alpha GitHub action #195
Merged
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
GPortas
added
Size: 3
g-saracca
approved these changes
Sep 24, 2024
Contributor
g-saracca
left a comment
g-saracca
left a comment
There was a problem hiding this comment.
Looks really good! This will help us a lot!
Contributor
|
looks good! |
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 this PR does / why we need it:
Implements a new GitHub action
deploy_alpha, which deploys an unstable alpha version on every commit to the develop branch.Which issue(s) this PR closes:
Special notes for your reviewer:
These versions are generated on every commit made to the develop branch, ideally after each pull request is merged.
They follow the structure 2.0.0-alpha.NUMBER, where number is an incremental value that starts at 1 and increases with each build.
These versions are also unstable and represent the latest work in progress on the develop branch.
Suggestions on how to test this:
Visual inspection of the code and the past commits in this PR, where I tested the action using the PR branch as the target branch and confirmed that the package was deployed with the auto-incremented tag on every push
Is there a release notes update needed for this change?:
No
Additional documentation:
No