feat: allow GEM_HOST_API_KEY to be used for any gemHost #26
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
bobvanderlinden
changed the title
bobvanderlinden
changed the title
bobvanderlinden
force-pushed
the
pr-support-other-hosts
branch
from
1531c1b to
589b02e
Compare
|
Hey @rylanc @avalanche123 @satoruk, apologies for the ping, but is there any chance any of y'all could take a look at this? 😄 |
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 allows using different hosts with
gemHostwhile usingGEM_HOST_API_KEY. This allowed me to push to gemfury.com with their push key.The
--keyis described as:In this PR the key is set to a static value, so that whichever
gemHostwas supplied, the key fromGEM_HOST_API_KEYis always used.