@phishy@sentry@codecov Hi Jeff, Tom from @codecov here. Replying here also in case my original reply gets lost. I'm sorry you've been having trouble getting in contact with us and getting a real response. I've gone ahead and looked at the issue and replied back.
@phishy@sentry@codecov Hi Jeff, Tom from @codecov here. I'm sorry you've been having trouble getting in contact with us and getting a real response. I've gone ahead and looked at the issue and replied back.
@cofonlafaefe@codecov Tom from @codecov here. This should be resolved going forward. You may need to upload coverage on a new commit to the affected branch, sorry for the inconvenience.
@NachoSoto@codecov Tom from @codecov here. Totally agree, you shouldn't get punished with lower coverage for possibly doing cleanup work. We tried to solve this problem with the `removed_code_behavior` setting https://t.co/VpUreHCLOU
@di_codes @btskinn Hi Dustin, Tom from @codecov here. We apologize for the pain this has caused our users and the PyPI team and wrote up a post-mortem here https://t.co/d117SELanX
@ayotycoon@codecov Ahhh, totally get that! Getting that high coverage number is really tough and takes a lot of time. I wish there were easier ways to do it.
@yayale_umi @codecov Awww geez, yeah I don't think that's possible. I think GitHub only allows for all notifications or none on a thread/PR. Maybe someone on the @github team knows better.
@ETazou@codecov Tom from @codecov here. You can add
```
github_checks:
annotations: false
``` to your codecov.yml. See the docs here: https://t.co/dsMTGx3WJA