fetch-depth question

[y-nk]

I've set fetch-depth to ${{ github.event.pull_request.commits }} to avoid fetching my whole repo. The action executes like this:

So then i would expect to have 12 commits (11 + the merge commit) in the rev-list, but i get much more than this.

not sure why. could somebody tell me if it's normal?

[davhdavh]

The default is to only download the files specifically for the commit you are building, ie fetch-depth:1 is what you want.

[y-nk]

i would like to add that i do not use the /merge in ref, so fetch: 1 does not match. i'd like to checkout consistently [github.event.before, ..., github.event.pull_request.head.sha]

[gofr]

Yes, this is normal.

fetch-depth: 3, for example, means that Git fetches the HEAD commit (depth=1), all its parents (depth=2) and all its grandparents (depth=3).

So with a Git history like this:

a - b --------- e
      \       /
        c - d

that will give you commits e (HEAD), b and d (both of its parents), and a and c (all of their parents). That's 5 commits, not 3 like you might've expected.