gitleaks with the --amend command
- Dominant language
- Go
- Stars
- 29.3k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
Research direction
No files, tests, or reproduction details are provided. Start by reproducing the rejection with a commit made using Git's --amend command and compare it with a normal commit, then trace the relevant scan entry point. Done means determining whether --amend changes Gitleaks' behavior and documenting the result or a specific reproducible bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100