Skip to content

Remove gemfile.lock #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 30, 2019
Merged

Remove gemfile.lock #53

merged 2 commits into from
Oct 30, 2019

Conversation

dmitry-shibanov
Copy link

@dmitry-shibanov dmitry-shibanov commented Oct 28, 2019

  • Remove Gemfile.lock from root of project
    It is legacy Gemfile.lock that contains dependency on run_loop 3.x (current version is 4.x) so it causes cucumber test failures.

Let's remove Gemfile.lock and just install latest version via bundle install

@dmitry-shibanov dmitry-shibanov marked this pull request as ready for review October 29, 2019 08:12
Copy link
Contributor

@jmoody jmoody left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not enough.

We need to add Gemfile.lock to the .gitignore.

It is legacy Gemfile.lock that contains dependency on run_loop 3.x (current version is 4.x)

Another solution would have been to run bundle update and commit the new Gemfile.lock to GitHub. However, I think removing is correct choice because we are trying to automate the maintenance of these repos and I can foresee cases where we would need to manually visit the repo to update the Gemfile.lock.

@jmoody
Copy link
Contributor

jmoody commented Oct 30, 2019

I made a note that we need to investigate the flickering tests on Xcode 11.2

@jmoody jmoody merged commit 754ce3f into master Oct 30, 2019
@jmoody jmoody deleted the v-dmshib/remove-gemfile-lock branch October 30, 2019 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants