codecov / codecov/codecov-action
[BUG] upload creates files in the project root, leaving the repo dirty
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 260
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 1
Description
Describe the bug
After running codecov/codecov-action@v5, the repository root has three unexpected new untracked files:
codecov, codecov.SHA256SUM, and codecov.SHA256SUM.sig, making some subsequent operations fail.
See https://github.com/fast-pack/FastPFOR-rs/actions/runs/14274678522/job/40015342209 (should be available for the next few days/weeks.
To Reproduce
- create a code coverage report at the
target/llvm-cov/codecov.info - run this code step:
- uses: codecov/codecov-action@v5
with:
token: ${{ secrets.CODECOV_TOKEN }}
files: target/llvm-cov/codecov.info
fail_ci_if_error: true
Expected behavior
no new files
Regression
not certain
Versions
- OS: linux
- Git Host: GitHub
- CI/CD: GitHub Actions
- Uploader:
codecov-action@v5.4.0- 0565863
Commit and CI link
https://github.com/fast-pack/FastPFOR-rs/actions/runs/14274678522/job/40015342209
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the codecov-action@v5.4.0 workflow step and the target/llvm-cov/codecov.info input, but no source file. Start by reproducing the workflow on Linux and inspect the action's upload path for where codecov, codecov.SHA256SUM, and codecov.SHA256SUM.sig are written. Done means the upload succeeds without leaving those files in the repository root.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100