Merged
Conversation
Contributor
|
note : as a true human being, so not hesitate to remove entirely the agent context part ;) |
eskenazit
requested changes
Mar 20, 2026
farah-t-trigui
force-pushed
the
fix/gitleaks-issue
branch
from
f68823e to
7de1b93
Compare
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
2 participants
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.
Related Issue
Closes #162
What does this PR do?
Context : workflow runs Gitleaks on the repository, but it was reporting secrets in git history even when we were using ephemeral credentials (like in the SonarQube setup) so now it's fixed
Also gitleaks badge was red even when no secrets were detected, now is also fixed
Checklist
main