-
Notifications
You must be signed in to change notification settings - Fork 553
🌱 add support for hadolint SAST #4688
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4688 +/- ##
==========================================
+ Coverage 66.80% 68.28% +1.47%
==========================================
Files 230 249 +19
Lines 16602 18890 +2288
==========================================
+ Hits 11091 12899 +1808
- Misses 4808 5131 +323
- Partials 703 860 +157 🚀 New features to boost your workflow:
|
Signed-off-by: Adam Korczynski <adam@adalogics.com>
"sonarqubecloud": true, | ||
"hadolint-action": true, |
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.
this section is normally for github apps, is it an app or an action?
for _, tt := range tests { | ||
searchRequest := clients.SearchRequest{ | ||
Query: "github/codeql-action/analyze", | ||
Path: "/.github/workflows", | ||
} | ||
t.Run(tt.name, func(t *testing.T) { |
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.
was there a driver behind redefining this in every test instead of once?
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
feature
What is the current behavior?
Scorecard does not support hadolint SAST.
What is the new behavior (if this is a feature change)?**
Scorecard supports hadolint SAST.
Which issue(s) this PR fixes
Partially fixes #2318 (comment)
Special notes for your reviewer
Does this PR introduce a user-facing change?