[RF-26051] Fix pushing releases to RubyGems #26
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
|
/reviewme @rainforestapp/devs |
This config is copied from get-env's: rainforestapp/get_env@9bcd8cf
magni-
force-pushed
the
RF-26051/pp/rubygems
branch
from
864a2df to
64be26b
Compare
Merged
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.
#24 added a
push_to_rubygemsCI job copied from our other gems, but theRUBYGEMS_API_KEYit references wasn't added to the project in CircleCI. Rather than have to add the environment variable to all gem projects, I've copied it into a newRubyGemsCircleCI Context and referenced that here.