Secret appears to be added in new file and only checked on update

[farmersmurf]

I have added a new file call credTest and put a dummy aws secret in it AKIAIOSFODNN7EXAMPLE.

Doing a commit allowed the file to be committed and only once I updated it to AKIAIOSFODNN8EXAMPLE and tried to commit it again, did it prevent me from doing so.

unless the first one wasn't valid in that case it works :)

[mtdowling]

Is this still an issue with version 1.3.0 of git-secrets?

[sourabhDemo]

Yes, this is still issue. When I run
git secrets --scan
it scans the new file and successfully finds the secrets.
But when I try to run
git commit -m "Commit message"
it does not scan new file, rather commit the new file. Can you please suggest if I am missing anything.

[sparr]

git commit -m "Commit message" will create an empty commit if you have not added any files. Can you try git commit -a -m "Commit message" to automatically add your changed file (or git add in advance) and confirm that it gets scanned?