fix: ignore baseline if path was not relative in source #1101
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.
Description:
There is currently a bug with the baseline ignore.
If gitleaks is not executed in the current directory and --source is used to specify a custom path, the baseline file is not ignored correctly because the relative file paths do not match. That check is done in
Detect()
.This will currently report secrets in the baseline file, however the baseline file should be excluded.
Basically as for now the baseline only works if gitleaks is executed directly in the target repository and the baseline path is set relative to it.
This pr fixes that bug so the baseline path is resolved correctly and can be compared during fragments check no matter what directory.
Checklist: