feat: optionally allow to push to other repositories #67
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
Owner
|
Hello @fauno, thank you for your PR. Would you mind provide more context/background on this? Thank you. |
Author
|
Sure! We're pre-compiling gems from rubygems.org and pushing them to our own private repository. Gems that have these options enabled on their gemspec would fail. The docs recommend setting this to prevent accidentally pushing private gems to rubygems.org, but I've found some gems that set rubygems.org as the only allowed repository, so https://guides.rubygems.org/publishing/#serving-your-own-gems |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
if you're pushing to your own repository, these gemspec options would prevent it, so i added the --unsafe flag