You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
We've been having a problem uploading coverage data for different branches. It all started when we noticed we have different coverage in our badges for the same code and opened this issue in our repo: boostorg/url#128
It turns out what was happening is the commit to master was being associated with develop because codecov had already seen that commit hash in develop. So the only commit codecov associated with master was two years ago, where this didn't happen by chance (some code that didn't go through develop first).
Is there some way around this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
We've been having a problem uploading coverage data for different branches. It all started when we noticed we have different coverage in our badges for the same code and opened this issue in our repo: boostorg/url#128
It turns out what was happening is the commit to
master
was being associated withdevelop
because codecov had already seen that commit hash indevelop
. So the only commit codecov associated withmaster
was two years ago, where this didn't happen by chance (some code that didn't go through develop first).Is there some way around this?
The text was updated successfully, but these errors were encountered: