You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
If codecov can't find version control, the code indicates that it's supposed to failover to using walk to generate the file structure. Instead, I'm seeing this in the output:
==> Building file structure
fatal: not a git repository (or any of the parent directories): .git
/bin/sh: hg: not found
It seems like the try/catch statement is potentially failing to catch the error?
The text was updated successfully, but these errors were encountered:
Dear @thomasrockhu I was going to create a similar issue because I think this seems to be a major limitation currently of the codecov. When we build cointainers we want to have them as slim as possible so its easier to build, publish and pull them when running CI tasks or production workloads, in other words adding .git shouldn't be a requirement.
I was going to ask if there is any way to run codecov uploader without having .git in the project directory, there has to be a better documentation for this use case, especially for rather enterprise situations where git history + whats stored in .git can be big.
In other words, documentation needs revamp for codecov uploader without .git case(if decision is to keep -e flag), documentation needs better explanations and examples, and perhaps code/architecture level changes to make this functionality possible because I'm 100% it should be possible given codecov has access to the main related project repository to fetch git related metadata.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If codecov can't find version control, the code indicates that it's supposed to failover to using
walk
to generate the file structure. Instead, I'm seeing this in the output:It seems like the try/catch statement is potentially failing to catch the error?
The text was updated successfully, but these errors were encountered: