Fix fetching git history + fallback to unshallow repo

[dorny]

Fetching git history did not worked in all cases.
As described in #71 - either deepening the history or counting the commits didn't worked as expected.
This PR uses combination of --depth on initial fetch and later --deepen is used to extend history
Commits are now counted on all branches git rev-list --count --all.
It also increases default value of initial-fetch-depth to 100.
For most cases it should only do a single fetch.

As a last fallback try - whole history is fetched by turning shallow repo into full clone using git fetch --unshallow

closes #71

[micgro42]

This PR caused our CI to consistently fail. Going back to 2.9.0 resolved the issue.

The error message in the logs:

Run dorny/paths-filter@v2
  with:
    filters: visual:
    - 'tokens/**'
    - 'vue-components/**'
  behavioral:
    - 'vue-components/**'

    token: ***
    list-files: none
    initial-fetch-depth: 100
Changes will be detected against the branch master
Searching for merge-base master...QuantityInput
  /usr/bin/git rev-list --count --all
  640
  /usr/bin/git merge-base master QuantityInput
  fatal: Not a valid object name master
  /usr/bin/git fetch --depth=1280 origin master:master QuantityInput
  From wmde/wikit
   * [new branch]      master     -> master
   * branch            QuantityInput -> FETCH_HEAD
  /usr/bin/git rev-list --count --all
  640
  No more commits were fetched
  Last attempt will be to fetch full history
  /usr/bin/git fetch --unshallow
  fatal: --unshallow on a complete repository does not make sense
Error: The process '/usr/bin/git' failed with exit code 128

[dorny]

Thanks for reporting the issue. I rolled back v2 so it points to 2.9.0 until it's fixed.
It's strange that your repository is not shallow but at the same time there's no master branch.
Is there anything unusual in your workflow that could help me figuring out what happened?

[dorny]

I think I know what happened.
You had full repository clone (actions/checkout@v2 with fetch-depth: 0 ?) but master was only a remote branch while this action did a check against local branch with that name. Following fetch didn't add any commit so it tries to unshallow repo which failed because it wasn't shallow repo. Quite unfortunate mistake on mi side.

I will fix it soon

[dorny]

@micgro42
I released the fix as v2.9.2 and point v2 to it.
I've already tested it on fork of your repo.

[micgro42]

Thank you for the quick fix 🙏