clj-commons 2024-05-01 | Slack Archive

lread01:05:49

Blech. I use http://codecov.io on rewrite-clj and I think (maybe?) http://codecov.io might require me to use a token now... I don't have administrator access to the clj-commons GitHub org, so I can't generate my own token. I did request rewrite-clj access via codecov, so clj-commons GitHub org admins might see a request from me? And that might let me generate a token?

seancorfield04:05:10

I approved it for the whole org...

seancorfield04:05:49

...oh, maybe someone else did earlier? I see coverage stats for rewrite-clj...

seancorfield04:05:31

LMK if you need anything else at this point...

lread10:05:43

Thanks Sean, I’ll try to figure out what steps I need to ask you to take

lread15:05:19

Ok, @U04V70XH6, thanks for your patience, I think I know what I need now. I need the "repository upload token" described in the first screenshot on this page: https://docs.codecov.com/docs/adding-the-codecov-token. To get to that page, you would click on rewrite-clj from your screenshot above and then "settings". (I don't have enough privs to see "settings" at all). I have setup a CODECOV_TOKEN secret for the rewrite-clj Github repo (https://github.com/clj-commons/rewrite-clj/settings/secrets/actions), could you edit then paste in the token from above for me? Another option is to give me admin privs to clj-commons github org, and I can do the above myself.

seancorfield16:05:50

That's done. LMK if it works. I used a global token so we can have one token for the whole clj-commons org.

lread16:05:14

Thanks @U04V70XH6 it seems to have worked like a charm! As an admin, it's up to you, but I'd recommend generating tokens at the github repo rather than the github org level. This way, you can revoke/regen tokens at the repo level should there be any security issues.

seancorfield16:05:23

Yeah, if we start to see more maintainers wanting to link in http://codecov.io, that would be a better approach. You're the first.

👍 1

2024-05-01

Channels