We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A clear and concise description of what the bug is.
Reproduction steps Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen. get score of all checks
however got '?' of dependency-update-tool and vulnerabilities. it prompts Error: check runtime error: internal error: search: unsupported feature,
anyone can give suggestion? thank you in advance
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Is there a update on this one? I too am facing the same issue
Sorry, something went wrong.
Is this specifically for the Dependency-Update-Tool? This is partially expected, but could be improved.
I believe Vulnerabilities check should be working now locally.
Vulnerabilities
This could be "fixed" by improving the error message to clarify that Dependency-Update-Tool doesn't work with --local (and why).
--local
In this particular case, I think the answer is "don't worry about searching for commits" if the repo client doesn't have them.
Successfully merging a pull request may close this issue.
Describe the bug
A clear and concise description of what the bug is.
Reproduction steps
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
get score of all checks
however got '?' of dependency-update-tool and vulnerabilities.
it prompts Error: check runtime error: internal error: search: unsupported feature,
anyone can give suggestion?
thank you in advance
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: