-
Notifications
You must be signed in to change notification settings - Fork 489
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
🐛 Fix remediation text when Scorecard is run multiple times within a program #2168
🐛 Fix remediation text when Scorecard is run multiple times within a program #2168
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2168 +/- ##
==========================================
+ Coverage 42.39% 44.67% +2.27%
==========================================
Files 94 95 +1
Lines 7824 7868 +44
==========================================
+ Hits 3317 3515 +198
+ Misses 4249 4086 -163
- Partials 258 267 +9 |
Could we simply extend This isn't ideal, and really the raw data struct should have a common struct to hold this info. But atleast this avoids passing in the CheckRequest to |
Integration tests success for |
I was just following your quick fix comments in #2152. Also, I was hesitant to touch RawData for fear of messing up the json/cron job flow.
|
SGTM, approved. Could we have a follow-up PR to address this? |
Integration tests success for |
👍 |
@@ -133,10 +136,10 @@ func PinningDependencies(name string, dl checker.DetailLogger, | |||
"dependency not pinned by hash detected", score, checker.MaxResultScore) | |||
} | |||
|
|||
func generateRemediation(rr *checker.Dependency) *checker.Remediation { | |||
func generateRemediation(remediaitonMd remediation.RemediationMetadata, rr *checker.Dependency) *checker.Remediation { |
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.
nit: remediaitonMd
What kind of change does this PR introduce?
bug fix for incorrect repo info in remediation text. the problem affected the weekly scorecard cron job
What is the current behavior?
The remediation text used to reflect the first repo / branch processed by a scorecard cron worker.
What is the new behavior (if this is a feature change)?**
The remediation text will now match the repo/branch being analyzed.
Which issue(s) this PR fixes
#2152
Special notes for your reviewer
This is a temporary fix, and modifies the function signatures for
evaluation.PinningDependencies
andevaluation.TokenPermissions
. I don't think anyone besides ourselves are using these exported functions.Does this PR introduce a user-facing change?
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.)