Description
Relatively minor, and I think it's something to do with the merge queue's autobranches.
The codecov landing page for this project should show the coverage at the "latest" commit on main. Which it claims is 9598eeb
However, that was the middle of last week. There don't seem to be any relevant changes after or around this commit in our history (the next PR to be merged into main was #146 which doesn't touch the coverage or the ci).
Note that all commits' builds on main actually have sent coverage reports to codecov. They are coming from the merge queue's auto-generated branches and when the build reruns on main, it seems somehow that the gh-readonly-queue/ branch is given precedence.
Not sure if this can be fixed with a setting in codecov. Possibly we could skip coverage upload by hacking our CI yml with something like:
- name: Upload coverage report (skip if this is a merge queue build)
if: ${{ !contains(github.ref, 'gh-readonly-queue/') }}
uses: codecov/codecov-action@v2For the coverage step. Assuming that it reruns the build as on main.
Unsure if related, but (since I'm digging in the codecov uploads) we have encountered codecov/3954 a few times. They recommend using a codecov upload token even if the repo is public.