Can't reactivate repo that was automatically deactivated when I made it public

Support
1

Before submitting a topic, please confirm the following

I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
~ I have validated my codecov.yaml configuration file.~ Using GH actions.
I have filled out the below sections to the best of my ability.

Description

After publishing a private GH repo, it shows up as “deactivated” but I can’t find how to reactivate from the UI (i.e., it seems active). Also, uploads fail with:

[ErrorDetail(string='This repository has been deactivated. To resume uploading to it, please activate the repository in the codecov UI: https://app.codecov.io/github/dreamtimecircles/bftbench/settings', code='invalid')]

Re-generating and setting up again CODECOV_TOKEN didn’t help, nor API v1.

CI/CD URL

Codecov Output

[ErrorDetail(string='This repository has been deactivated. To resume uploading to it, please activate the repository in the codecov UI: https://app.codecov.io/github/dreamtimecircles/bftbench/settings', code='invalid')]

Expected Results

Not sure why the repository was deactivated in the first place after being published, but I expected Codecov to keep working.

Actual Results

See “Codecov output” above.

Additional Information

None that I can think of.

2

Yikes, thanks @circlespainter. This looks like a bug, we’ll push a fix for it ASAP.

1 Like
3

Thanks @tom! Are there any workarounds available?

4

@circlespainter I made a request manually on your behalf, but I’m not sure which will happen first. The request is processed or the bug is fixed. Unfortunately, that’s all I got for you right now.

1 Like
5

I’ll add that revoking auths and re-authorizing didn’t help either. Deleting and recreating the account is also an option for me, since this is my first relevant usage; does that have any chance of working?

6

@circlespainter I’ll be honest, I’m not sure if that will resolve the issue. But I don’t think it would hurt to try.

1 Like
7

Nope, it didn’t help. Thanks anyway, then I’ll wait for a resolution.

1 Like
8

@circlespainter ok, you should be good now!

1 Like
9

Wow, that was fast… Thanks!

1 Like