Gitleaks action fails when creating PR in new repo

[lawndoc]

On this line, the command passed to gitleaks for PRs compares with ^.. which will reference the previous commit on the base branch. This causes Gitleaks to reference a commit that doesn't exist when running on a PR for a repo with only one commit in the base branch.

Is there a reason this isn't .. instead? Would it cause any issues to change this?

Not a widely impactful bug, but I just want to understand what the intended behavior is in case I'm missing something.

[lawndoc]

@DariuszPorowski just checking in. Is including ^ before .. important to the functionality of the tool when comparing pull requests? It seems to me like it wouldn't be an issue to remove the ^, but I just want to make sure I'm not missing something before I create a PR.

[lawndoc]

I'll test this while I'm working on #61

[lawndoc]

Looks like using ... instead of ^.. in the git log args will fix the issue with no negative side effects.

Brand new repo with ^.. for git log arg:

Same new repo with ... for git log arg:

Existing repo with ... for git log arg:

I'll include this fix in my merge along with the fix for #61