Our code coverage fluctuates, meaning that CI is often shown as failed
even on no-op operations
This is bad for our developer experience: we can't trust CI status to
be reporting correctly, and this slows fixing actual issues
So, we mark codecov as 'informational' so only 'real' CI failures are
shown to users
> If `true` is specified the resulting status will pass no matter what
> the coverage is or what other settings are specified. Informational
> mode is great to use if you want to expose codecov information to
> other developers in your pull request without necessarily gating PRs
> on that information.
https://docs.codecov.com/docs/commit-status#informational
Related issue: 12227 - fixing the flakiness in other ways
Most PRs had annotations added on each branch which did not have
coverage
This added more noise to the PR, and was not helpful, as we aren't yet
going for 100% coverage, it made reviews harder, and probably
alienated new contributors
https://docs.codecov.io/docs/github-checks-betaFixes#8296