Skip to content
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

Depfu Error: Found both *.gemspec and Gemfile.lock #1

Closed
depfu bot opened this issue Nov 11, 2017 · 0 comments
Closed

Depfu Error: Found both *.gemspec and Gemfile.lock #1

depfu bot opened this issue Nov 11, 2017 · 0 comments

Comments

@depfu
Copy link

depfu bot commented Nov 11, 2017

Hello,

We've tried to activate or update your repository on Depfu and found something odd:

Your repo contains both a *.gemspec file and a Gemfile.lock.

Depfu can't really handle that right now, unfortunately, and it's also not best practice:

If your repo contains a *.gemspec that usually means it is meant to be used as a Gem, or put differently, a library. Locking dependencies on a library (via Gemfile.lock) doesn't really make sense, especially since the Gemfile.lock can't and won't be honored when building and installing the gem.

Instead, you should declare your dependencies as specifically as needed (but as loose as possible) in the *.gemspec and add the Gemfile.lock to your .gitignore.

By checking in the Gemfile.lock, you will not only break Depfu (which we might fix at some point, maybe), but you will also keep your CI from testing against real life sets of dependencies.


This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

@mikker mikker closed this as completed Nov 13, 2017
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

No branches or pull requests

1 participant