-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Gitleaks 8.23.2 #96
Comments
Hi @scrocquesel-ml150 , What is the issue with 8.23.2? |
I think it is related to this issue gitleaks/gitleaks#1729 |
@scrocquesel-ml150 Can you explain what the issue is? I am aware of the deprecation of the commands |
Since 8.23.2, gitleaks detects leaks in PR when it should not.
The reported file is not modified in the one commit of this PR. |
I just tried setting version to
Task version is |
Sorry it is not clear what the issue is. Can you:
|
My settings are
Everything worked fine before the release of gitleaks 8.23.2.
As expected only one commit is scanned with 8.23.1
36 commits instead of just one with 8.23.2. |
Specifying 8.23.1 works here, If there is an issue with 8.23.2 you can go back to version 8.23.1. I only maintain the extension, not Gitleaks itself |
Yes, sorry, doing many tests and retaining to older version worked as expected. I know you are not maintainng GitLeaks itself and I'm glad you are aware of the deprecated stuff. Just guessing that if the extension was already using newer git command, we would not have to set version to 8.23.1. This was the main reason of creating this issue. |
Hi @scrocquesel-ml150 thank you for the notion of the deprecated stuff. I appreciate that. Yes unfortunately this issue pops up due to the deprecation and a bug. Reverting back to 8.23.1 is a good thing to do. I've created a separated issue to track the deprecation. Will work on that when I have some spare time. Is it allright if I close this issue? I cannot do anything to help you at this moment, sorry. |
I found this gitleaks/gitleaks#1504 because of an issue with 8.23.2
The text was updated successfully, but these errors were encountered: