Codecov not tracking repo, "Missing base report" and "Unable to find commit in GitHub"


I attempted to integrate codecov into our repo about 3 months ago and ran into issues that appeared to be related to the branch structure of the repository. A sprint branch was created from the master branch, then my feature branch was created from that. When my feature branch was merged into the sprint branch, when the sprint went into master, and every commit since then all that has shown on the codecov site is a greyed out commit with the error messages above. The commits always show as “unable to find commit in GitHub”, however the “missing base report” message goes away sometimes and I still haven’t figured out what causes that.

Commit SHAs



CI/CD or Build URL


GitHub Actions

Codecov Output

==> linux OS detected
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (330066ecce62f2cdcfd2fe1845095475f51bbad9649dce81ac7b663dc884bbef codecov)
==> Running version latest
==> Running version v0.1.15
/home/runner/work/actions/codecov/codecov-action/v2/dist/codecov -n -Q github-action-2.1.0 -Z -C b66b0ca9b9bf4a9e080a6e8a10ae5795508d7fd5
[2022-01-27T00:07:36.272Z] [‘info’]
_____ _
/ | | |
| | ___ __| | ___ ___ _____ __
| | / _ \ / ` |/ _ / / _ \ \ / /
| |
| (
) | (
| | __/ (
| (
) \ V /
____/ _,|_|____/ _/

Codecov report uploader 0.1.15
[2022-01-27T00:07:36.282Z] [‘info’] => Project root located at: /home/runner/work/fafSite/fafSite
[2022-01-27T00:07:36.283Z] [‘info’] → Token found by environment variables
[2022-01-27T00:07:36.290Z] [‘info’] Searching for coverage files…
[2022-01-27T00:07:36.384Z] [‘info’] Warning: Some files located via search were excluded from upload.
[2022-01-27T00:07:36.384Z] [‘info’] If Codecov did not locate your files, please review Supported Coverage Report Formats
[2022-01-27T00:07:36.385Z] [‘info’] => Found 1 possible coverage files:
[2022-01-27T00:07:36.385Z] [‘info’] Processing /home/runner/work/fafSite/fafSite/coverage.xml…
[2022-01-27T00:07:36.399Z] [‘info’] Using manual override from args.
[2022-01-27T00:07:36.399Z] [‘info’] Detected GitHub Actions as the CI provider.
[2022-01-27T00:07:36.400Z] [‘info’] Pinging Codecov:*******&branch=waterbury-73-release&build=1753623348&
[2022-01-27T00:07:36.601Z] [‘info’] Uploading…
[2022-01-27T00:07:36.943Z] [‘info’] {“status”:“success”,“resultURL”:“”}

Expected Results

The coverage report would be generated and the results would be available on the codecov website.

Actual Results

The coverage report was generated, but the link that was generated is a deadend and codecov can’t display the commit properly.

Additional Information


@mpurnell1 there are a few things going on here, so I’d like to tackle them one at a time and see what happens to resolve them. Can you add the GitHub app integration to the repository? This should fix the unable to find commit issue.

I requested access from the owner of the repository. When he approved it, I triggered another run of the codecov report and it still showed as unable to find commit and missing base report, although it does now show a CI Passed badge uner the unable to find commit message.

@tom Adding the GitHub app integration to the repository doesn’t seem to have helped. Did you have any other fixes to try?

1 Like

@mpurnell1 this is really strange. What happens when you go to that commit in GitHub? Also, how do you typically merge PRs and commits, via merging or rebasing or something else?

What happens when you go to that commit in GitHub?

That link only works for me when I change the “FarmAfield” to “farmafield-labs”, which made me realize that I had connected the github app integration through the company’s organization instead of the company account that owns the repo. I just integrated it again using the company account and I got it closer to working. I’m now able to see the commits at, but only with the company account, the other authorized contributors for the repo can’t see the coverage reports, just an “Unauthorized: User not activated” error.

Also, how do you typically merge PRs and commits, via merging or rebasing or something else?

After making our commits locally in the command line, we make PRs and merge them online on github.

@mpurnell1 looks like there was a blip earlier tonight as we were fixing a DNS issue. How is it now?

The report uploads and PR comments are working fine now. I can even see the commits at with the company account. The only issue I have remaining is that when I try to view the codecov overview with my account instead of the company account, all I see is this 403 error

However, when I change the url slightly to look at the user instead of the repo, it seems like I should be able to access that repository.

I can access both a contributor account and the owner account so technically I can survive the way it is now, but there are other contributors and it would be ideal if they could also view the codecov overview.

@mpurnell1 you mentioned contributor account. I wanted to confirm this not a member account? When you log into the owner account, do you see the contributor account in the user management section under settings?

I’m not certain I know what you mean, as I can’t find any user management section, but in the settings of the repo as the owner, I see an access section with a collaborators tab, and there I am able to see the account I was trying to access the reports from, listed as a collaborator. I have also since noticed that I am able to see some information at, further confirming that I do have access to the repo from my collaborator account, but when I click on most of the links on that page it redirects to and I am shown the unauthorized page posted above.

@mpurnell1 sorry for the inconsistency, but app. is the correct behavior, and we are working to get it fixed on

You will need an admin to go to the settings page and activate you as a user.

On that settings page, this is all I can see that mentions other users being able to access Codecov.

I’m considering moving the repo over to an organization instead of being owned by a single user. Would that improve the behavior for multiple users accessing the codecov dashboard?

@mpurnell1 I would recommend moving over to an organization. I will say that we are planning to work on improvements for outside collaborators, but generally, we recommend making them members if possible.