Update release pipeline #46
Merged
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
miry
force-pushed
the
deploy-on-tags
branch
2 times, most recently
from
101758c
to
0396462
Compare
Introduce release shipit pipeline. It checks if the tag exists and then allow to deploy.
miry
requested review from
a team,
muz,
spike01 and
shopifyshuhei
and removed request for
a team
muz
approved these changes
Mar 18, 2022
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.
Rename shipit pipeline
rubygems->release.Block release pipeline if there is no tag exists.
Deliver each commit separately to make sure to not miss a tag.
Skip install test gems during release.
Post merge steps