Skip to content

Conversation

@sloede
Copy link
Collaborator

@sloede sloede commented Feb 1, 2024

Supersedes #921.

TODO:

  • Repo admins: please verify that an appropriate codecov token is set as the repository secret named CODECOV_TOKEN before merging.

@IanButterworth
Copy link
Member

I'm not an admin so can't see repo settings, I'm afraid

@DilumAluthge
Copy link
Member

I can set up the token. But why do we need to upgrade to v4 of the action? Can't we just stay on v3 (which supports tokenless uploads)?

@sloede
Copy link
Collaborator Author

sloede commented Feb 1, 2024

I can set up the token. But why do we need to upgrade to v4 of the action? Can't we just stay on v3 (which supports tokenless uploads)?

In my experience, the codecov-action has been somewhat brittle in the past (but YMMV). Therefore, in my other repos we try to stick to the latest support version. Also, all the docs are by now referring to v4-specific details, making it slightly more confusing when sticking with v3. Tokenless uploads are still supported for PRs from forks, so that should still work.

Having said that, I have no strong feelings either way here 🤷‍♂️

@codecov
Copy link

codecov bot commented Feb 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8cd96a1) 84.62% compared to head (fefaab9) 84.62%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #922   +/-   ##
=======================================
  Coverage   84.62%   84.62%           
=======================================
  Files           3        3           
  Lines         826      826           
=======================================
  Hits          699      699           
  Misses        127      127           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@DilumAluthge
Copy link
Member

Alright, I grabbed the token from the Codecov settings1 and I added it to this repo as a GitHub Actions Secret2 named CODECOV_TOKEN.

I'll defer to @KristofferC and @IanButterworth on the question of upgrading to v4 versus staying on v3.

Footnotes

  1. https://app.codecov.io/gh/JuliaLang/PackageCompiler.jl/settings

  2. https://github.com/JuliaLang/PackageCompiler.jl/settings/secrets/actions

@sjkelly
Copy link
Collaborator

sjkelly commented Apr 3, 2024

A token-based auth seems better than whatever was done before. The coverage results appear to upload correctly, so merging this. Thanks!

@sjkelly sjkelly merged commit 41ef30d into JuliaLang:master Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants