Run gitleaks directly; the action breaks on a root commit's first push - #10
Merged
Conversation
gitleaks-action computes its scan range as <oldest>^..<newest> from the push event. On a repository's first push the oldest commit is the root, whose parent does not exist, and the scan fails with 'unknown revision' before reading a byte. The failure presents as a red check, not as a leak, so it erodes trust in the green one. Replaced with the gitleaks binary over full history (the checkout already fetches depth 0). Verified locally against this tree: 2 commits scanned, no leaks.
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.
gitleaks-action computes its scan range as
<oldest>^..<newest>from the push event. On a repository's first push the oldest commit is the root, whose parent does not exist, and the scan fails withunknown revisionbefore reading a byte.Replaced with the gitleaks binary over full history (checkout already fetches depth 0). Verified locally: 2 commits scanned, no leaks.