New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve SHA mismatch error message #5315
Comments
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, #5313, it's the same problem. A similar report here: #5239 |
Hi! Given the recurrence of this kind of report, we should probably enhance the error message. Thanks for reporting this! |
Emit a hopefully more helpful error message when the Git ref doesn't exist. The error message is the same we use when getting changed files only: it suggests checking that repository clone is not shallow, and that the full history is available. Additionally, when running on GitHub Actions, it also suggests checking the fetch-depth option of the actions/checkout step. Fix #5315
#5316 should take care of this. |
Emit a hopefully more helpful error message when the Git ref doesn't exist. The error message is the same we use when getting changed files only: it suggests checking that repository clone is not shallow, and that the full history is available. Additionally, when running on GitHub Actions, it also suggests checking the fetch-depth option of the actions/checkout step. Fix #5315
Emit a hopefully more helpful error message when the Git ref doesn't exist. The error message is the same we use when getting changed files only: it suggests checking that repository clone is not shallow, and that the full history is available. Additionally, when running on GitHub Actions, it also suggests checking the fetch-depth option of the actions/checkout step. Fix #5315
Emit a hopefully more helpful error message when the Git ref doesn't exist. The error message is the same we use when getting changed files only: it suggests checking that repository clone is not shallow, and that the full history is available. Additionally, when running on GitHub Actions, it also suggests checking the fetch-depth option of the actions/checkout step. Fix #5315
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
The text was updated successfully, but these errors were encountered: