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.

Sign up for GitHub

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

Jump to bottom

Apply inconclusive status for not found gems #59

Open
alexeyschepin opened this issue Dec 18, 2020 · 1 comment
Open

Apply inconclusive status for not found gems #59

alexeyschepin opened this issue Dec 18, 2020 · 1 comment

Comments

@alexeyschepin
Copy link
Contributor

Hey @manuelmeurer, thanks for the great project.

I tried to use it for my Gemfile.lock but if failed with gem not found error. It happens for private gems. I assume it would be better to just ignore those gems or mark their compatibility as inconclusive.
What do you think about it? I can prepare a PR if you like this idea.
@manuelmeurer
Copy link
Collaborator

Yep, let's ignore them!
Would be great if you had time to work on a PR.
I'm happy to help with questions!
Thanks

@alexeyschepin alexeyschepin mentioned this issue Dec 21, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@manuelmeurer @alexeyschepin