Closed TrentSteenholdt-Insight closed 8 months ago
I got the same thing when upgrading a repo to v6 the other week. The error message isn't clear at all for this, but the SHA reference is your commit's SHA, the one that the workflow is running for.
So, see the resolution of another issue today, https://github.com/super-linter/super-linter/issues/5313, it's the same problem.
A similar report here: https://github.com/super-linter/super-linter/issues/5239
Hi! Given the recurrence of this kind of report, we should probably enhance the error message. Thanks for reporting this!
I am getting this error with superlinter 6.8.0, not on my own check-ins or when I merge branches, only when running superlinter against pull-requests.
It's not clear to me what the root cause was or how to resolve this issue? According to this issue it should have been resolved in 6.3.0?
https://github.com/damies13/rfswarm/actions/runs/10193188112/job/28204156573?pr=270
@damies13 it appears that you didn't set the proper fetch depth in the checkout step of your workflow. I suggest having a look at the readme as the error message suggests. If the issue persists, please open a new issue so we can investigate.
Ah ok, I fixed that issue on the main branch the the requestor of the PR might be on the old branch, thatnks, I'll remind him to pull from upstream - Thanks :+1:
Also explains why I didn't get this error when I merged the PR.
Is there an existing issue for this?
Current Behavior
Super Linter v6 on Pull Request pipeline run fails with
2024-02-22 01:35:33 [FATAL] The GITHUB_SHA reference (xxxx) doesn't exist in this Git repository
Expected Behavior
In version v5, the same YAML works fine
Super-Linter version
Relevant log output
Steps To Reproduce
Anything else?
No response