-
Notifications
You must be signed in to change notification settings - Fork 511
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
✨ Feature: Dependency-diff ecosystem naming convention mapping (GitHub -> OSV) #2088
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2088 +/- ##
==========================================
+ Coverage 42.13% 42.19% +0.06%
==========================================
Files 92 93 +1
Lines 7569 7595 +26
==========================================
+ Hits 3189 3205 +16
- Misses 4132 4141 +9
- Partials 248 249 +1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
The PR does a lot more than the title suggest. Try do do one thing as per tiel in each PR to simplify review.
I'll separate it into two PRs: (1) the mapping and (2) the optimizations (var name, logic) in my next push, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
Integration tests success for |
…b -> OSV) (ossf#2088) * save * save * save * save * save * save
What kind of change does this PR introduce?
What is the current behavior?
GetDependencydiffResults
returns depdency-diff check results with package ecosystem names in the GitHub naming convention.What is the new behavior (if this is a feature change)?**
GH -> OSV.
Which issue(s) this PR fixes
Fixes #2078
Special notes for your reviewer
Please LGTM and merge this PR first, then #2077. This one optimizes the Dependency-diff API and has higher priority.
Does this PR introduce a user-facing change?
No.
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)