# Unable to remove codecov report for a single commit

**URL:** <https://community.codecov.com/t/unable-to-remove-codecov-report-for-a-single-commit/4392>\
**Category:** Support\
**Created:** [June 30, 2023, 11:48am UTC](https://community.codecov.com/t/unable-to-remove-codecov-report-for-a-single-commit/4392 "2023-06-30T11:48:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![finiteL00p](https://avatars.discourse-cdn.com/v4/letter/f/9d8465/32.png) [@finiteL00p](https://community.codecov.com/u/finiteL00p)\
**Post date:** [June 30, 2023, 11:48am UTC](https://community.codecov.com/t/unable-to-remove-codecov-report-for-a-single-commit/4392/1 "2023-06-30T11:48:48Z")

</div>

### Description

I have been using codecov for a while now and all the reports for the respective commits are uploaded properly in codecov portal. Now, there is one particular commit where by mistake the code coverage was reported as over 96% and that got uploaded to codecov portal.

Because of this, the graph in ocdecov portal is showing an abnormal spike. Is there a way that particular commit with the wrong code coverage can be removed from the codecov portal?

### CI/CD URL

NA

### Codecov Output

NA

### Expected Results

The abnormal spike should be normalized by removing or ignoring the wrongly uploaded codecov report.

### Actual Results

 ![CleanShot 2023-06-30 at 17.22.50](https://canada1.discourse-cdn.com/flex029/uploads/codecov/original/2X/6/6708579edf547cd23a0c4b886ba7fcb9a73de1f8.png)

### Additional Information

NA

---

<div class="post-metadata">

**Author:** ![tom](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tom/32/8_2.png) [@tom](https://community.codecov.com/u/tom)\
**Post date:** [July 23, 2023, 11:40pm UTC](https://community.codecov.com/t/unable-to-remove-codecov-report-for-a-single-commit/4392/2 "2023-07-23T23:40:55Z")

</div>

@finiteL00p oh geez, that’s probably annoying. There’s no way to do this, but I would open a [feedback topic](https://app.codecov.io/gh/feedback) to allow for removing reports in the UI.
