You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi,
one new collaborator use the --amend command when he commits his changes
gitleaks is set for his repo but he received reject messages from gitleaks but in his conf files there is no secret key token !
can you tell me if the --amend command is a problem with gitleaks ?
we investigate a lot of time but this is the only difference with another collabs for me
to be sure i just want to know if this --amend command can cause issue with gitleaks ?
it is not really a bug and sorry if i am not in the right place.
very thanks a lot
ludo
The text was updated successfully, but these errors were encountered:
hi,
one new collaborator use the --amend command when he commits his changes
gitleaks is set for his repo but he received reject messages from gitleaks but in his conf files there is no secret key token !
can you tell me if the --amend command is a problem with gitleaks ?
we investigate a lot of time but this is the only difference with another collabs for me
to be sure i just want to know if this --amend command can cause issue with gitleaks ?
it is not really a bug and sorry if i am not in the right place.
very thanks a lot
ludo
The text was updated successfully, but these errors were encountered: