git rev-list bug

[lengrongfu]

This is the result of GitHub workflow execution.

This is the result of my local execution.

[lengrongfu]

https://stackoverflow.com/questions/63284060/git-rev-list-not-working-inside-github-action

[vbatts]

@lengrongfu thanks for the report!
what's cat /etc/os-release and git --version of your local system?

[vbatts]

and guessing from the image, the repo you're working from is distribution/distribution?

[lengrongfu]

@lengrongfu thanks for the report!
what's cat /etc/os-release and git --version of your local system?

git --version: git version 2.30.1 (Apple Git-130)
os system: Mac 11.3.1

[lengrongfu]

and guessing from the image, the repo you're working from is distribution/distribution?

yes

[lengrongfu]

Would you like to help me look at this problem?
https://github.com/lengrongfu/distribution/runs/3413200873?check_suite_focus=true

[vbatts]

It's odd that it just began failing. It doesn't look like the workflow config related to this changed. I wonder if the actual @checkout workflow stopped fetching the depth?

…

On Tue, Aug 24, 2021 at 12:22 PM lengrongfu ***@***.***> wrote: Would you like to help me look at this problem? https://github.com/lengrongfu/distribution/runs/3413200873?check_suite_focus=true — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQL2KWCA5HQTHWFGP7MMDT6PBLXANCNFSM5CXENANA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[lengrongfu]

[lengrongfu]

I was thinking, is it because my git submission is not standardized, which causes it to run wrong? Can you describe what is the main purpose of using the git rev-list command for verification?

[vbatts]

the purpose of the `rev-list` is to collect what commits are in the range to be checked. I think this will need to be rethought, if Github Actions are pruning the depth. Perhaps there is an environment variable that indicates which commits are even present in the cloned repo?