ci: enable Gitleaks scan in daily build - #57
Open
roshan-ku wants to merge 3 commits into
Open
Conversation
Wire the existing .github/actions/analysis/gitleaks composite action into the Daily Build workflow so secrets scanning runs alongside the other static analysis steps.
Download a pinned, checksum-verified Gitleaks release binary into /usr/local/bin and run both 'gitleaks git -v' (commit history) and 'gitleaks dir . -v' (working tree). This removes the dependency on gitleaks-action, which requires a GITLEAKS_LICENSE for org-owned repos, and fixes the previous history-scan step that called a gitleaks binary that was never installed on the runner. Scan output is written as plain text logs under reports/; no CSV or SARIF is generated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wire the existing .github/actions/analysis/gitleaks composite action into the Daily Build workflow so secrets scanning runs alongside the other static analysis steps.
Description
Checklist
Code Quality
Testing
Review Readiness
Documentation
Security
PR Type
What kind of change does this PR introduce?