codecov / codecov/codecov-action

`env_vars` input has no visible effect on Codecov UI

Open
#1,828 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug codecov/codecov-action
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

According to the README, the env_vars input is described as:

Environment variables to tag the upload with (e.g. PYTHON | OS,PYTHON)

However, after uploading coverage reports with env_vars set, I can’t find these variables reflected anywhere on the Codecov UI. It seems like setting env_vars has no effect.

Here is an example coverage report where I configured env_vars:
🔗 https://app.codecov.io/github/vivodi/Flexget/commit/ff609bf951cbd68f710a02de2f9dab299f0674fe

Image

- name: Upload coverage to Codecov
  uses: codecov/codecov-action@ad3126e916f78f00edff4ed0317cf185271ccc2d  # v5
  with:
    env_vars: OS,PYTHON
    fail_ci_if_error: true
    token: ${{ secrets.CODECOV_TOKEN }}

You can find the full GitHub Actions workflow here:
https://github.com/vivodi/Flexget/actions/runs/15089429373/workflow?pr=13

Could you tell me what the purpose of setting env_vars is?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README description of the env_vars input and the provided GitHub Actions workflow, then compare the configured upload with the linked Codecov report. Determine whether the variables should appear in the Codecov UI and document or correct the behavior so the purpose and expected result are clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.