Feedback about setting up your repo

[codecovdesign]

Thanks for dropping by! 👋

We've been working on improving the repo configuration and set up..

• How was your experience setting up your repo?
• Did you experience any challenges?
• What did you think about the documentation?
• What would improve the set up process?
• Any general thoughts you'd like to share!

We greatly appreciate your time and thoughts - looking forward to hearing from you ❤

Codecov team

This issue is intended to share and collect feedback about the tool. If you have support needs or questions, please see our support page.

[chrisxaustin]

The repo setup page includes this note:

*Not required if your repo is using GitHub Actions, Travic CI, CIrcle CI, AppVeyor, or Azure Pipelines.

The codecov-action says this though:

If you have a private repository, this Action also requires you to [provide an upload token](https://docs.codecov.io/docs/frequently-asked-questions#section-where-is-the-repository-upload-token-found-) from [codecov.io](https://www.codecov.io/) (

I tried it without the token and it did not work, so I'm going to follow the instructions under the codecov-action instead of the setup repo instructions.

[chrisxaustin]

The setup for multi-module maven projects with jacoco isn't as intuitive as I'd like, so some more documentation would reduce friction when adding new projects. The basic upload works well, but I'd also like to capture cross-module coverage for cases where module A uses module B heavily in the tests. The current behaviour seems to only consider same-module coverage in the final report, which is often appropriate, but is misleading in my case.

[femd1ngu5]

too hard i dont need Ci bruh

[suiyun39]

Some repo is deleted and never upload. It always display on my Dashboard.
I want delete it in settings, but always route to /new.

[mossyblog]

Spelling mistake:
Once you've committed your changes in step 2 and ran your CI/CD pipeline. In tour pull request, you should see two status checks:

I assume "Tour" is "Your"

As for Documentation. Its quite vague and unclear on expectations on how for example you want the users to publish their code coverage along side Codecov. May I suggest you take the time to publish some example simple "Actions.yml" / examples for people to view and make use of.

[SpotlightForBugs]

Worked great.

[cloudshiftchris]

omg. that is the worst setup experience.

1. The 'GitHub public repos' link to sign up requires full access to all repos, and lists all the private repos;
2. Disjointed documentation & steps to hook up GitHub to CodeCov.

[dogederp]

"Step 3: add Codecov to your GitHub Actions workflow" okay, how?

[albanh]

"Step 3: add Codecov to your GitHub Actions workflow" okay, how?

It would be good to know where in the workflow this should be added, or does it not matter?

[codecovdesign]

@dogederp @albanh thank you for the feedback. We investigated this and realized the anchor of "GitHub Actions" was going to the wrong page (it's been fixed). Further, based on you're feedback we'll plan to add more subtext for where/how to add to actions.
Thank you again 🙏

[jayber]

The documentation refers to "pull request" in step 4

What pull request? I've just created repo and pushed stuff directly to the trunk, there are no pull requests. Do there need to be?
How do I tell if coverage was generated for a repo?

I've completed all the steps in the GitHub actions successfully I think, but the repo list still says "not yet enabled". How do I debug this?

Step 4 says "Once you've committed your changes in Step 2". I don't think anything is committed is it? You just setup and enable the app . Does something need to be committed in the repo?

This page https://docs.codecov.com/docs/quick-start specifically shows something different for step 3:

- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v3

vs

- name: Upload coverage reports to Codecov
      run: |
        # Replace `linux` below with the appropriate OS
        # Options are `alpine`, `linux`, `macos`, `windows`
        curl -Os https://uploader.codecov.io/latest/linux/codecov
        chmod +x codecov
        ./codecov -t ${CODECOV_TOKEN}

Which is right?

[codecovdesign]

@jayber sorry for my delay, just noticing this. Thanks for the feedback.

What pull request? there are no pull requests. Do there need to be?

No, it doesn't require a pull request. However, commonly configuration would be done with a PR workflow, but it sounds like you committed directly to the head. We mention the PR in step 4 is because there is a PR comment coverage report and status check.

How do I tell if coverage was generated for a repo?

If you go to your action and look at workflow, you may see the following:

Could you send the output of the CI step where you're uploading the coverage?

This page https://docs.codecov.com/docs/quick-start specifically shows something different for step 3:

Sorry for the confusion here. The reason there is a diff is because the first one is more specific to GitHub actions CI and the other is generic CI. The Codecov GitHub action is a wrapper for the same instructions in the quick start guide. We will be following up to update our docs to be more clear about this. Thanks for the feedback 🙏

[philgyford]

I've got codecov working fine with several public repositories but I can't get it working with one private repo - I always get the same error. I have done:

1. Added the CODECOV_TOKEN as a repository secret
2. Allowed access to the repo in the Codecov app that I installed in my GitHub account
3. Have this in my GitHub Action (the same as I have in my working public repos, except with the addition of the with section):

     - name: Upload Coverage to Codecov
       uses: codecov/codecov-action@v3
       with:
         token: ${{ secrets.CODECOV_TOKEN }}

But running that step results in this (I've only replaced the name of the repo with myrepo):

Run codecov/codecov-action@v3
==> linux OS detected
https://uploader.codecov.io/latest/linux/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (02b055414cc124203ab061ffc45f5497ca39ede5e63a06717a6981c32d7b425f  codecov)
==> Running version latest
==> Running version v0.5.0
/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov -n  -Q github-action-3.1.3
[2023-05-15T11:55:18.421Z] ['info'] 
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.5.0
[2023-05-15T11:55:18.432Z] ['info'] => Project root located at: /home/runner/work/myrepo/myrepo
[2023-05-15T11:55:18.433Z] ['info'] -> No token specified or token is empty
[2023-05-15T11:55:18.614Z] ['info'] Running coverage xml...
[2023-05-15T11:55:19.482Z] ['info'] Searching for coverage files...
[2023-05-15T11:55:19.572Z] ['info'] Warning: Some files located via search were excluded from upload.
[2023-05-15T11:55:19.572Z] ['info'] If Codecov did not locate your files, please review https://docs.codecov.com/docs/supported-report-formats
[2023-05-15T11:55:19.573Z] ['info'] => Found 1 possible coverage files:
  coverage.xml
[2023-05-15T11:55:19.573Z] ['info'] Processing /home/runner/work/myrepo/myrepo/coverage.xml...
[2023-05-15T11:55:19.579Z] ['info'] Detected GitHub Actions as the CI provider.
[2023-05-15T11:55:19.846Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.3-uploader-0.5.0&token=*******&branch=main&build=4980002434&build_url=https%3A%2F%2Fgit.luolix.top%2Fphilgyford%2F myrepo%2Factions%2Fruns%2F4980002434&commit=b1b59b59a1fedc21b8ca307e00180de555b6f9fd&job=test-and-deploy&pr=&service=github-actions&slug=philgyford%2F myrepo&name=&tag=&flags=&parent=
[2023-05-15T11:55:20.203Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

[gregorywilliams]

Thanks @philgyford I also needed to add:

    with:
      token: ${{ secrets.CODECOV_TOKEN }}

to my GitHub Action. Before adding that I was getting:

[2023-05-17T11:49:49.686Z] ['info'] -> No token specified or token is empty
...
[2023-05-17T11:49:50.234Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.5.0&  [rest redacted]
[2023-05-17T11:49:50.481Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

Now it succeeds:

[2023-05-17T11:56:14.465Z] ['info'] ->  Token found by environment variables
...
[2023-05-17T11:56:15.052Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.5.0&  [rest redacted]
[2023-05-17T11:56:15.419Z] ['info'] Uploading...
[2023-05-17T11:56:15.640Z] ['info'] {"status":"success","resultURL":"https://app.codecov.io/github/  [ rest redacted ]

And I can now see the analysis over on the codecov.io website.

The instructions for GitHub Actions should be amended to also state the with block

[philgyford]

Thanks @gregorywilliams but I already had that in the example of my code I showed, or do you mean it needs to go somewhere else?

  - name: Upload Coverage to Codecov
    uses: codecov/codecov-action@v3
    with:
      token: ${{ secrets.CODECOV_TOKEN }}

[gregorywilliams]

@philgyford I was agreeing that I'd also needed to add the same and thanking you for mentioning it.

When I set up Codecov against my repo their instructions neglected to mention the with block. It's those instructions that I think that Codecov should modify, such that others aren't also caught out. I included the before / after output that I had such that others reading this thread may recognise the signs and thus the resolution.

[philgyford]

@gregorywilliams Unfortunately it's not the resolution for me, because I have the with block and I'm getting the error I displayed.

[codecovdesign]

with:
token: ${{ secrets.CODECOV_TOKEN }}

@gregorywilliams that's right, and we'll be adding this input to the repo guide page ✅

@philgyford I'm unsure what the issue is based on your post. Could you reach out to our support team ?

[enraiha0307]

Hi, As a beginner while setting up code coverage for my project, I faced the following issue:

In step2 when I copy the code and paste it into my Github Actions yaml file,

for this line:

env: CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

I get the following error, and my build fails:

Nested mappings are not allowed in compact mappings YAML

Solution:
we need to add it under env:

      - name: Upload coverage to codecov.io
        uses: codecov/codecov-action@v3
        env: 
         CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

Please update this part in the Setup for GitHub Actions.

[cameron]

As a member of an org that had just passed its seat limit, I could not get a new repo to show up in the dashboard list, although initiating the request to add the repo to codecov's permissioned set showed no errors. It took an admin (CTO) digging into the codecov dashboard to discover I had an "inactive" status, which, perhaps was causing the permission update to fail? Not sure, but nothing in my UI indicated that anything was amiss.

Better error/status reporting to make it clear what we needed to do would have saved some c-suite guesswork!

[JohannLai]

I also found this problem.

[larryaasen]

I also found this problem.

I also have this problem now. Here is the correct syntax:

- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v3
  env:
    CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

[codecovdesign]

@larryaasen @JohannLai @enraiha0307 thank you for raising the syntax error. The fix in live:

[Aerendir]

Hello dear team, I think you should mention two things clearly:

1. The action (as what I understand) will run the tests again with code coverage (is this correct? It is not clear)
2. There are other config options for the action

Now my question (to which I'm trying to find an answer) is: Where does the action get the coverage files to upload? I think the answer is in the docs of the action itself, but I'm still investigating (spending time in something that should have clarified since the start by the docs).

[philgyford]

I'm still confused about how to specify the token required for private repositories.

The codecov-action README says:

    - name: Upload coverage to Codecov
      uses: codecov/codecov-action@v3
      with:
        token: ${{ secrets.CODECOV_TOKEN }}

The example in the website docs is like:

    - name: Upload coverage reports to Codecov
      run: |
        # Replace `linux` below with the appropriate OS
        # Options are `alpine`, `linux`, `macos`, `windows`
        curl -Os https://uploader.codecov.io/latest/linux/codecov
        chmod +x codecov
        ./codecov -t ${CODECOV_TOKEN}

The examples in the above comments – including a screenshot of a correct version from @codecovdesign – are like this (I don't know which docs the screenshot is taken from):

- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v3
  env:
    CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN  }}

Are all of these correct? Or two of them? Or only one of them? If the latter, could they all be kept in sync?

[codecovdesign]

@Aerendir thank you for your feedback! Based on it, I'm creating some updates to the copy to be more clear in the documentation / setup guide 🙏 .

The action (as what I understand) will run the tests again with code coverage (is this correct? It is not clear)

The action does not run the test, rather after running tests in the CI and generating coverage reports, it upload coverage data to Codecov.

Now my question (to which I'm trying to find an answer) is: Where does the action get the coverage files to upload?

It will get the reports from the CI test run. If the CI isn't configured to output coverage reports, you'll need to configure this in your testing tool.

[codecovdesign]

@philgyford that is confusing and thanks for raising 🙏 .
For the 1st and 3rd examples that is specific to GitHub actions and the 2nd input is generic for other CIs. My takeaway actions here are 1) update copy to be clear about input diff in documentation, 2) sync/align 1&3 to be consistent across docs.

[philgyford]

@codecovdesign Thanks. One thing though – you say "the 2nd input is generic for other CIs" but it's introduced with "An example of a workflow using the uploader with GitHub Actions is shown below." Which would make me think that's how to set things up with GitHub Actions?

[njbbaer]

@AlexsJones Use v3 or v4-beta. See codecov/codecov-action#1089.

[admercs]

How can I use codecov on my repo without creating a new branch?

[MusicalNinjaDad]

I'd suggest updating the GitHub setup instructions to no longer require a secret:

but rather to use the app integration instead:

This is both more secure and easier to do & get right

[rodrigodesalvobraz]

I am finding the setup experience confusing.
When signing up for Codecov for my project, I am immediately directed to a page telling me to do Step 1: set up the Codecov token and Step 2, add the yaml file to .github/workflows:

- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v3
  env:
    CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

and then it leaves it at that as if that's all the setup that's needed, but this does not seem to be enough, because it does not generate coverage information, does not set up badges, etc.

[IanHoar]

This has been an arduous slog to get setup. I am using CircleCI, Orb v4.0.0 and (still) attempting to get the results piped to github.

Issues I've run into:

• Documentation recommends codecov/codecov@3.2.4 when 4.0.0 is the latest.
• When using 3.2.4, ARM is not supported (which has forced me to use 4.0.0
• I needed to remove all the spaces from the folder names in my xcode project. I was getting failures on the scanning step
• I needed to add a step to my CI to create the ~/.gnupg folder. The upload script was failing without that
• I am still facing an issue where the upload is failing with the error Upload failed: {"flags":{"0":["This field may not be blank."]}} see issue -> Upload fails with error "flags": "This field may not be blank." #246

Not sure if there will be more issues when I can actually get a report uploaded but I'm very close to ditching Codecov and choosing another solution

[thomasrockhu-codecov]

Hi @IanHoar,

1. Thanks for this, that was my mistake. This has been updated here.
2. Has the ARM version been working for you now?
3. That's an awful experience, are you able to link the CI build or share the logs?
4. Are you able to run gpg --version? We've been noticing a lot of difference between gpg versions and have been trying to correct for it. Again, any logs would be most useful..
5. This has been patched in 4.0.1 that released a few moments ago. Sorry again for this issue.

Is there anything else you are running into that I can help you with?

[ErikBjare]

The current step for GitHub Actions is wrong:

Screenshot

That env: should be with:

[codecovdesign]

Thanks your @ErikBjare for the report 🙏 . I created a bug issues to investigate and fix: codecov/engineering-team#1171

[PinkieSwirl]

I get a "There is an error processing the coverage reports." and "unusable report" when trying to upload a jacoco test report (xml).

It is completely unclear for me, why this report is unusable (works locally).

[codecovdesign]

@PinkieSwirl thank you for sharing and sorry to hear about the issue. Could you link a screenshot of the error? It will help me investigate the issue further 🙏 (codecov/engineering-team#1187)

[jberkenbilt]

I am setting up a C++ project (cmake) with GitHub actions. The documentation says to add this to actions:

- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v4.0.1
  env:
    token: ${{ secrets.CODECOV_TOKEN }}
    slug: qpdf/qpdf

• I think token and slug should be under with, not env, and for this open source repo at least, slug doesn't seem to be needed.
• I think it would be better to just do @v4 rather than @v4.0.1.
• Before the first upload, the repo showed in settings as "deactivated", but I think it probably could have set something indicating that there was no data. I manually activated it, but I think I didn't have to.

[codecovdesign]

@jberkenbilt thank you for the feedback 🙏

think token and slug should be under with
This has been updated^

would be better to just do @v4 rather than @v4.0.1

Noted. cc'ing @rohan-at-sentry wdyt^ would this be any breaking changes? If not, we can open a polish issue.

Before the first upload, the repo showed in settings as "deactivated"

@jberkenbilt did you previous deactivate the repo in settings? It sounds like that wasn't the case, but wanted to confirm ahead of debugging why it showed that way.

[jberkenbilt]

@jberkenbilt did you previous deactivate the repo in settings? It sounds like that wasn't the case, but wanted to confirm ahead of debugging why it showed that way.

@codecovdesign No, I didn't deactivate it. I was just poking around and noticed it said it was deactivated, then activated. Then it occurred to me that I should have left it to see whether it would activate on its own.

[maheshj01]

Github actions build succeeds but I don't see lcov file uploading here's the actions
https://github.com/maheshmnj/searchfield/actions

Edit: I have been able to setup flutter test coverage reports
use this workflow https://github.com/maheshmnj/searchfield/blob/master/.github/workflows/workflow.yml

[eigenein]

Codecov is right away complaining about unknown token:

[2024-04-10T19:00:33.081Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Could not find a repository associated with upload token ***', code='not_found')}

Without the token, it couldn't fetch the build:

[2024-04-10T18:28:32.899Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

Update

Apparently, there are 2 different tokens: the one from «Let's get your repor covered» does not work. The one from the «Settings» tab does

[renews]

Cant make it work for my private repo...

[renews]

Cant make it work for my private repo...

For some reason the repo was deactivated on codecov, after activating it, and installing the codecov app on my repo I started getting the error
error - 2024-05-22 13:47:42,980 -- Report creating failed: {"detail":"You do not have permission to perform this action."}

Double checked all data, everything seems to be in place.

[dalakatt]

Once merged to your default branch, subsequent pull requests will have Codecov checks and comments. Additionally, you’ll find your repo coverage dashboard here. If you have merged try reloading the page.Once merged to your default branch, subsequent pull requests will have Codecov checks and comments. Additionally, you’ll find your repo coverage dashboard here. If you have merged try reloading the page.

[rofrano]

Codecov 4.1.0 doesn't work but 3.1.4 does

Setup following your latest instructions does not work when running GitHub Actions in a python:3.11-slim container.

I do all of my development, testing, and deployments in a Docker python:3.11-slim container. Codecov v3.1.4 has been, and continues to work flawlessly. However, when I try and use v4.0.1 or greater with GitHub Actions, it fails with the error logs below.

Steps to reproduce

If you want to reproduce this just fork my repo: nyu-devops/lab-github-actions and uncomment the Codecov step at the bottom of .github/workflows/workflow.yaml to see for yourself. I teach students to use Codecov in my DevOps and Agile Methodologies graduate course at New York University (NYU) and I hate to tell them they have to use an older version because the new versions don't work. I would rather teach them how to get the latest version working.

You can also probably recreate this yourself by using a python:3.11-slim docker image as your runner like this:

jobs:
  build:
    runs-on: ubuntu-latest
    container: python:3.11-slim

Question

Can you please document what Codecov 4.0.1 needs in the Linux environment that 3.1.4 doesn't so that I can install those Linux components before running Codecov. From the logs it looks like it needs: gpg, xcrun, gcov and some config file that it can't find. What else is needed to get Codecov v4.0.1 to work that v3.1.4 didn't need?

BTW, v4.5.0 looks even worse. It looks like it is expecting git and NodeJS to be installed in my Python environment? It would be great if you could document your dependencies instead of just assuming they exist in the environment.

Logs from Codecov 4.1.0

Run codecov/codecov-action@v4.0.1
  with:
    token: ***
/usr/bin/docker exec  141e22d99f361cf08cffc7d9748af04dec2fc1ea595a4fb4b01f7f9a51231a11 sh -c "cat /etc/*release | grep ^ID"
==> linux OS detected
https://cli.codecov.io/latest/linux/codecov.SHA256SUM
==> Running version latest
Warning: Codecov: Error importing pgp key
undefined
Warning: Codecov: Error importing pgp key
undefined
==> Uploader SHASUM verified (86acfa1f84214ed6d58467a7837369da526e469846af917c89407208a4cb52f8  codecov)
==> Running version v0.7.1
==> Running command '/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov create-commit'
/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov create-commit -C 0e2531f538f4f59c8bb1b937c5d4872324ab7b8a
info - 2024-06-27 00:27:17,177 -- ci service found: github-actions
warning - 2024-06-27 00:27:17,178 -- No config file could be found. Ignoring config.
info - 2024-06-27 00:27:17,294 -- Process Commit creating complete
error - 2024-06-27 00:27:17,295 -- Commit creating failed: ["Service not found: none"]
==> Running command '/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov create-report'
/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov create-report -C 0e2531f538f4f59c8bb1b937c5d4872324ab7b8a
info - 2024-06-27 00:27:18,099 -- ci service found: github-actions
warning - 2024-06-27 00:27:18,099 -- No config file could be found. Ignoring config.
info - 2024-06-27 00:27:18,199 -- Process Report creating complete
error - 2024-06-27 00:27:18,200 -- Report creating failed: ["Service not found: none"]
==> Running command '/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov do-upload'
/__w/_actions/codecov/codecov-action/v4.0.1/dist/codecov do-upload -C 0e2531f538f4f59c8bb1b937c5d4872324ab7b8a
info - 2024-06-27 00:27:18,999 -- ci service found: github-actions
warning - 2024-06-27 00:27:18,999 -- No config file could be found. Ignoring config.
warning - 2024-06-27 00:27:19,002 -- xcrun is not installed or can't be found.
warning - 2024-06-27 00:27:19,002 -- gcov is not installed or can't be found.
info - 2024-06-27 00:27:19,002 -- Generating coverage.xml report in /__w/lab-github-actions/lab-github-actions
info - 2024-06-27 00:27:19,131 -- Wrote XML report to ./coverage.xml
info - 2024-06-27 00:27:19,138 -- Found 1 coverage files to report
info - 2024-06-27 00:27:19,138 -- > /__w/lab-github-actions/lab-github-actions/coverage.xml
info - 2024-06-27 00:27:19,203 -- Process Upload complete
error - 2024-06-27 00:27:19,204 -- Upload failed: ["Service not found: none"]

Logs from Codecov 4.5.0

Run codecov/codecov-action@v4.5.0
  with:
    token: ***
/usr/bin/docker exec  75e624aa3a992fc00ec0c88edcfe9753f60839a01c33d408c2594d1f731cbe50 sh -c "cat /etc/*release | grep ^ID"
evenName: pull_request
baseRef: rofrano:master | headRef: rofrano:rofrano-patch-1
evenName: pull_request
baseRef: rofrano:master | headRef: rofrano:rofrano-patch-1
evenName: pull_request
baseRef: rofrano:master | headRef: rofrano:rofrano-patch-1
==> linux OS detected
https://cli.codecov.io/latest/linux/codecov.SHA256SUM
/bin/sh: 1: gpg: not found
Warning: Codecov: Error importing gpg key: Command failed: gpg --logger-fd 1 --no-default-keyring --import /__w/_actions/codecov/codecov-action/v4.5.0/dist/pgp_keys.asc
/bin/sh: 1: gpg: not found
Warning: Codecov: Error verifying gpg signature: Command failed: gpg --logger-fd 1 --verify /__w/_actions/codecov/codecov-action/v4.5.0/dist/codecov.SHA256SUM.sig /__w/_actions/codecov/codecov-action/v4.5.0/dist/codecov.SHA256SUM
==> Uploader SHASUM verified (86acfa1f84214ed6d58467a7837369da526e469846af917c89407208a4cb52f8  codecov)
==> Running version latest
==> Running version v0.7.1
==> Running git config --global --add safe.directory /__w/lab-github-actions/lab-github-actions

/__w/_actions/codecov/codecov-action/v4.5.0/node_modules/@actions/io/lib/io.js:213
                    throw new Error(`Unable to locate executable file: ${tool}. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.`);
^
Error: Unable to locate executable file: git. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
    at Object.<anonymous> (/__w/_actions/codecov/codecov-action/v4.5.0/node_modules/@actions/io/lib/io.js:213:1)
    at Generator.next (<anonymous>)
    at fulfilled (/__w/_actions/codecov/codecov-action/v4.5.0/node_modules/@actions/io/lib/io.js:24:1)