Update "Ruby gems" article with aliases #99
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.
We've recently started using ruby alias versions in R&D to mitigate issues with versions on our CI where only the most recent patch version is available.
@arthurpalves suggested that this be incorporated into the existing "The better way with Ruby Gems" article.
This brief summary introduces the concept of Ruby version aliases and how to configure them, as well as touching on the advantages / disadvantages of taking this route.
What is this article about?
R:
Checklist:
assets/images/post/
).bundle install && bundle exec jekyll serve
.