Ignore Gemfile.lock #126
Merged
Ignore Gemfile.lock #126
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
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.
Description:
I might not be really agreeing with this, but if we are not pushing the
Gemfile.lock, let's make it explicit.The other way to do this is to keep the
Gemfile.lockwith the latest supported version and have agemfilesfolder to use with previous Ruby versions, and so, I agree this might require some more effort, and that might be why we preferred just not to push theGemfile.lock.No need to add it to the CHANGELOG.
I will abide by the.