Hi all,
I'm using latest release in a Mac and scan-history works well (both in bash and zsh), but if I run the same in other environments (a RHEL 7.5 vm, but even in some Docker containers like CentOS) the exit code is 0 but the command terminates immediately without doing anythins ... very strange.
I get 'git-secrets' from a git clone so this happens on latest code ... but same issue if I do a ceckout back to latest release (1.2.1).
There is something that I can do to enable DEBUG and understand what's happening (to help fix) ?
Note: in an Alpine (latest release) Docker container when run I had an error on a wrong -w flag used in grep, but only there.
I'm testing it with a sample test repository with committed some passwords, AWS_ACCESS_KEY, etc added and deleted, in different branches.
Hi all, I'm using latest release in a Mac and scan-history works well (both in bash and zsh), but if I run the same in other environments (a RHEL 7.5 vm, but even in some Docker containers like CentOS) the exit code is 0 but the command terminates immediately without doing anythins ... very strange. I get 'git-secrets' from a git clone so this happens on latest code ... but same issue if I do a ceckout back to latest release (1.2.1). There is something that I can do to enable DEBUG and understand what's happening (to help fix) ?
Note: in an Alpine (latest release) Docker container when run I had an error on a wrong -w flag used in grep, but only there.
I'm testing it with a sample test repository with committed some passwords, AWS_ACCESS_KEY, etc added and deleted, in different branches.
Thanks a lot for the help. Regards, Sandro