Updates Gemfile.lock after poltergeist gem has been removed from the Gemfile #943
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
…has been removed from the Gemfile
This was referenced Mar 6, 2019
Contributor
|
D'oh, I forgot how to Ruby |
BPScott
approved these changes
Mar 6, 2019
matyikriszta
deleted the
update-gemfile-lock-after-removing-poltergeist-app
branch
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
After merging in #942 auto deployment to codebar-staging failed because the updated Gemfile.lock wasn't committed after removing the poltergeist app from the Gemfile. Per the error message from the build log:
This PR updates and commits the new Gemfile.lock.