-
Notifications
You must be signed in to change notification settings - Fork 507
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
🐛 Bug fixing: Using the wrong URI to initialize the repo in Dependencydiff #2072
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2072 +/- ##
==========================================
+ Coverage 42.11% 44.53% +2.41%
==========================================
Files 92 92
Lines 7551 7554 +3
==========================================
+ Hits 3180 3364 +184
+ Misses 4122 3934 -188
- Partials 249 256 +7 |
Integration tests success for |
Integration tests success for |
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!
Integration tests success for |
Integration tests success for |
Head branch was pushed to by a user without write access
Integration tests success for |
Integration tests success for |
Integration tests success for |
…ydiff (ossf#2072) * temp * temp * temp * temp * temp * temp * temp
What kind of change does this PR introduce?
Fixing a bug introduced in PR #2046 where the
ghRepo
type of (clients.Repo) was created wrongly by the inputrepoURI
rather than the dependency repoURI to be checked by scorecard.What is the current behavior?
The Dependencydiff module uses the input repo to initialize the
ghRepo
to run the scorecard check, resulting in all of the dependencies having the same check results and scores (of the input repo).What is the new behavior (if this is a feature change)?**
The module will correctly initialize
ghRepo
using the dependency's srcRepo URI.Which issue(s) this PR fixes
Fixes #2046
Special notes for your reviewer
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.)