Update Rails to 4.2.10 and 5.0.6 and remove gemfiles/*.gemfile.lock files #174
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
|
You are completely right @fatkodima! Feel free to add them to thx! |
fatkodima
force-pushed
the
update-railses
branch
from
8af3a81 to
88b96cf
Compare
fatkodima
changed the title
|
@epergo Done. |
|
Thank you! |
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.
Is there a reason why
.gemfile.lockfiles are keeping within source control? Their updates generate a lot of churn and looks like many popular gems add them to their.gitignorefiles like Appraisal recommends.