Handle "leapfrog" case for --audit#47
Merged
Merged
Conversation
jfagoagas
pushed a commit
to jfagoagas/detect-secrets
that referenced
this pull request
Mar 14, 2026
Add usage for reporting functionality
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.
Bug
When applying an audit, to an already audited baseline, users may find themselves in a strange case: through a combination of skips and decisions, secrets may be overridden in the baseline accidentally.
This should not happen.
Testing
You would expect that the output is like the below illustration:
However, it would have actually ended up as follows: