Commit Gemfile.lock after adding Gemfile ruby declaration
#120
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
Rails no longer includes a `ruby` declaration in the generated Gemfile. When nextgen adds it, a side-effect is that the Gemfile.lock will change the next time `bundle install` is run. This means that after generating a project, when you run `bin/setup` for the first time, it may cause the Gemfile.lock to change. Fix by proactively running `bundle lock` and committing the result, so that the Gemfile.lock in the generated project is guaranteed to be up to date.
mattbrictson
added
automerge
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.
Rails no longer includes a
rubydeclaration in the generated Gemfile. When nextgen adds it, a side-effect is that the Gemfile.lock will change the next timebundle installis run. This means that after generating a project, when you runbin/setupfor the first time, it may cause the Gemfile.lock to change.Fix by proactively running
bundle lockand committing the result, so that the Gemfile.lock in the generated project is guaranteed to be up to date.