Use :rubygems shortcut as standard Gemfile's source instead of explicit URL
#4684
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
…plicit URL. Theoretically this would future-proof Gemfiles against possible (albeit unlikely) change in the rubygems URL.
fxn
added a commit
that referenced
this pull request
Jan 26, 2012
Use `:rubygems` shortcut as standard Gemfile's `source` instead of explicit URL
|
Using FYI - Some time back I had submitted a pull request to bundler to change the default usage of |
|
There's honestly no benefit to using HTTPS when requesting rubygems. I don't see why the argument is made one way or another here. |
sgerrand
pushed a commit
to sgerrand/rails
that referenced
this pull request
Nov 2, 2013
…ygems" This reverts commit 33b29e0, reversing changes made to ac8c729. Reason: rails#4684 (comment)
brigade-gerrit
pushed a commit
to causes/rails
that referenced
this pull request
Nov 15, 2013
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.
Theoretically this would future-proof Gemfiles against possible (albeit unlikely) change in the rubygems URL.
Documentation