v1.3.0+ scans entire history on push about gitleaks-action

[niall-byrne]

This is totally possible, I believe you can control the number of commits you check out with actions/checkout@v2.

[stone-z]

This is totally possible, I believe you can control the number of commits you check out with actions/checkout@v2.

For sure, I think the question still remains how to determine how many commits to check out. If the commits are known, we could also use the same approach as is used for PRs (with the commit list). But a user could push arbitrarily many commits in a single push, and I haven't yet managed to find a git- or GitHub-native way to see what they are.

[niall-byrne]

https://github.community/t/how-to-get-all-pushed-commit-information/116861/3

[stone-z]

😮 yeah that looks like it should work. I'll cook up a PR. Thanks!

[crazy-matt]

I believe the scan is performed on all branches as the gitleaks action does not allow to pass the --branch parameter to narrow down the scan. Which leads to some issues on the push event when working as a team with multiple feature branches.

[crazy-matt]

☝🏼 potential fix: #38

[zricethezav]

Hi @stone-z as you already know, we released version 2.0 which fixes this problem. Only relevant commits will be scanned.