-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: update codecov-action from v3 to v4 #140
Conversation
0907b75
to
e472bac
Compare
@rst0git the coverage workflow on the main branch succeeds as of now without any problems: https://github.com/checkpoint-restore/checkpointctl/actions/runs/10009967467/job/27670052231 |
@snprajwal The workflow is unable to access the upload token in pull requests (e.g., #141, #140)
|
Right, so it seems GitHub does not allow accessing secrets implicitly in workflows triggered on commits outside the upstream repo: https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow
|
Going by the docs, the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #140 +/- ##
==========================================
+ Coverage 78.73% 80.88% +2.15%
==========================================
Files 11 11
Lines 1260 994 -266
==========================================
- Hits 992 804 -188
+ Misses 201 123 -78
Partials 67 67 ☔ View full report in Codecov by Sentry. |
@snprajwal It looks like tokenless uploading works with PRs: |
@rst0git by the way, reading the issue you linked, it looks like the token is required for PRs coming from the base repo + commits on the base repo itself, and forks can use the tokenless version. If that is indeed the case, we might require another check to decide if the token should be used or not (based on whether the trigger is |
Version 4.4.1 provides a bugfix to correctly detect tokenless upload for PRs from forks: codecov/codecov-action#1437 codecov/codecov-action#1431 Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
@snprajwal This problem seems to be fixed with codecov/codecov-action#1437. |
No description provided.