-
Notifications
You must be signed in to change notification settings - Fork 363
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
feat: replace "skip-git" with "include-git", making git repository scanning not the default #1311
base: v2
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1311 +/- ##
=======================================
Coverage 68.43% 68.43%
=======================================
Files 183 183
Lines 17606 17606
=======================================
Hits 12049 12049
Misses 4895 4895
Partials 662 662 ☔ View full report in Codecov by Sentry. |
f17cacf
to
c1409f3
Compare
… our osv-scanner.toml in fixtures (google#1337) Uses the new feature landed in google#1214
…ncy resolution (google#1331) Part of google#1330 No functional change is made compared to the version in `internal/manifest`, just switched to use the osv-scalibr interface. Extractors moved to lockfilescalibr as a temporary staging ground before moving to osv-scalibr.
Can you update the target to the v2 branch? |
…anning not the default BREAKING CHANGE: don't scan git repositories by default, replacing "--skip-git" with "--include-git"
c1409f3
to
c0265ae
Compare
@oliverchang given we don't have any tests for this area of the scanner and the conflicts with the v2 branch, it might be better if someone else on the team whose more familiar with the C/C++ stuff take this up, if that's possible |
BREAKING CHANGE: don't scan git repositories by default, replacing "--skip-git" with "--include-git"
I've gone with renaming the property so it aligns with being false by default, though we could keep the existing property if we really wanted; likewise, I've also changed this for both the API and CLI as I think it makes sense to have them aligned even though we could technically have them different.
Resolves #1277
(also, I think the fact that we use
--skip-git
in our workflows is another good sign it should be disabled by default 😅)