-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
chore: allow codecov to detect SHA #28278
Conversation
In our CI, where codecov.sh is called, there's a message from its CLI saying `Issue detecting commit SHA. Please run actions/checkout with fetch-depth > 1 or set to 0`. From my understanding setting depth=2 should allow to resolve this, without having much impact on cloning workload.
We would appreciate it if you could provide us with more info about this issue/pr! Please do not leave the |
Switching to https://github.com/codecov/codecov-action may be the best option, for now we just need to unblock this. Anyone looking at these reports? |
@@ -67,6 +68,9 @@ jobs: | |||
./scripts/python_tests.sh | |||
- name: Upload code coverage | |||
if: steps.check.outputs.python | |||
continue-on-error: true # codecob is not critical and randomly fails at times |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
continue-on-error: true # codecob is not critical and randomly fails at times | |
continue-on-error: true # codecov is not critical and randomly fails at times |
Code on the Cob?! Sign me up!
This still upholds/blocks on the standards (e.g. core packages at 100% coverage) right?
Ok I ended up setting up the official GHA, allowed me to delete that heavy |
In our CI, where codecov.sh is called, there's a message from its CLI saying
Issue detecting commit SHA. Please run actions/checkout with fetch-depth > 1 or set to 0
. From my understanding setting depth=2 should allow to resolve this, without having much impact on cloning workload.