That said, Codecov exists – but it doesn’t load. That’s an issue I first reported a couple years ago, but I’ve given up hope for it to be resolved (I was told by Codecov staff that we produce too much coverage data, apparently the Codecov tooling can’t deal with that).
I’m also using the GitHub marketplace app (just reinstalled it to the organization today), and it doesn’t seem to be updating commit statuses. It is able to post the coverage comment just fine, but it is not able to add a failing commit status when coverage decreases.
Another update (sorry for the spam), the status checks never showed up, but they appeared as valid options in the branch protection rules, so I made them required and they’re showing up now.
However, now my other statuses are broken
This is starting to look like an issue on GitHub’s end.
I’m also pretty confused. My other checks are coming from GitHub actions, which test / lint some JavaScript and C# code.
When I look at the branch protection rules for master, all of the checks (my GitHub actions and CodeCov) are there.
When I require that my GitHub actions checks pass, they show up in the PR, but the CodeCov checks do now.
When I require the CodeCov checks, they show up, but my GitHub actions checks do not.
When I require both, only the CodeCov checks show up.
I am not sure why those checks are being assigned to a merge commit, but regardless, this is really looking like an issue on GitHub’s end. No combination I try allows me to use all of the checks.
I appreciate your help, I’m going to attempt to escalate this with our GitHub support rep.
Yes that is really strange, running git log locally does not show this as a merge commit. The shas are different as well. I’ll attempt to look into this too.
@tom sorry for missing this earlier. yes, i’m using the github app, but i haven’t changed anything about this repo or the app being installed on my user account. Must i completely uninstall and reinstall it to fix the issues, or is there a URL i can use to force regathering permissions?
I’ve solved it in all our repos in Github. We have about 54 repos, all using Codecov installed as a Github app in our org, and we also use Travis CI.
We used codecov - npm version 3.7.0 (latest) and that showed in the build log that the report was sent after a successful Travis CI build, and gave a link. However, the link showed there was an error (but couldn’t give anything more). The codecov status in our PRs remained unchanged (‘waiting’).
Switching the use of this npm module to the Bash uploader [Deprecating] Bash Uploader fixed everything. Now all codecov statuses are reported properly.
I was concerned that this would not work in our our Windows builds in our Travis CI build matrix because it was a bash script, but Travis CI uses git-bash on Windows so it’s all good.