Codecov: Set API token only appears in public repo or when signed out

[joebowbeer]

I'm noticing some weird behavior with what I think is called the context menu, which may be preventing me from viewing codecov for a private GitHub repo.

If I'm viewing a private repo, the context menu either doesn't display or it shows only the Codecov documentation item. Then when I view a public repo, the menu shows more items, including the Codecov Set API item.

Even at sourcegraph.com, if I'm signed in, then the context menu only shows me one item: Codecov: Documentation and support. Then, if I sign out, the context menu shows me seven items, including Codecov: Set API token.

(By the way, I'm also confused about the connection between my browser extension settings and the ones for my account at sourcegraph.com. What is the connection between my sourcegraph account and my GitHub or Codecov account? This may be related to discussion at #232?)

[sqs]

@chrismwendt Any idea why this is happening?

[chrismwendt]

According to the Codecov Sourcegraph extension's package.json, the "Set API token for private repositories" action will only show up when you're viewing a file. That doesn't explain why when you sign out you see more items in the command palette (this is mysterious).

I double checked that I see Codecov line BG colors on private code, so this should work for you too.

@joebowbeer Could you share repro steps or a video on your Sourcegraph instance, and make sure that the Codecov Sourcegraph extension is enabled when you go to sourcegraph.example.com/extensions ?

[joebowbeer]

Hi Chris, sorry for the late response I'm not running a sourcegraph instance. I was under the impression that sourcegraph.com could be made to work. I did verify that the codecov extension is enabled (at sourcegraph.com/extensions), but navigating to a source view in GitHub still presents me with *Configure Sourcegraph at the top and a context menu on the right (4 horizontal lines) that does not expand. The up/down arrow simple changes direction. I assume the menu is empty.

[chrismwendt]

@joebowbeer Ah, I think this was happening because extensions weren't being run in the context of private repositories. This should be fixed in the browser extension v1.17.0.

[ryan-blunden]

@joebowbeer Is the Codecov extension working on private repositories for you now?