codecov / codecov/codecov-action
[BUG] Use of codecov-action action leaves git repository in dirty state
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
Apparently execution of the actions created these untracked files inside the project directory, so git will report dirty state.
codecov
codecov.SHA256SUM
codecov.SHA256SUM.sig
This breaks the CI pipelines for users that do check that does not reports untracked files after test execution, which is a very good practice.
A workaround is to add these files to project .gitignore but that should NOT be needed.
To Reproduce
Run git status after running the action.
Expected behavior
No untracked files are created. Any temporary files used by the action should not be created inside the project directory (use temp instead).
Commit and CI link
Provide the commit SHA and CI link. If applicable, provide the entire Codecov output from CI.
Additional context
Add any other context about the problem here.
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
Start by running the action and checking git status for the reported codecov, codecov.SHA256SUM, and codecov.SHA256SUM.sig files. Trace where the action downloads or creates these files, then verify that the action completes without leaving untracked files in the project directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100