Repository navigation
Add pinned read-only gitleaks scan - #14
Merged
Merged
Conversation
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
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.
Adds a separate secret-scan workflow alongside the existing CI.
Gitleaks action v3.0.0 and checkout are pinned to immutable commit SHAs. The scanner binary is pinned to 8.30.1. Every pushed branch is scanned; weekly and manual runs scan history. The upstream action needs extra PR-read permission for private PR scans, so this workflow uses push/schedule/manual events to retain
permissions: contents: read. Checkout credentials are not persisted; comments, finding artifacts and summaries are disabled. No custom secret or license is required for this personal-account repo.Validation: actionlint including inline ShellCheck, permission/action-pin checks, redacted working-tree secret scan and diff checks passed. Existing CI is unchanged. No deploy or live-host work. Leave unmerged.