Skip to content

Require configured token for uploading coverage#70

Open
glopesdev wants to merge 2 commits intoSainsburyWellcomeCentre:mainfrom
glopesdev:code-coverage-report
Open

Require configured token for uploading coverage#70
glopesdev wants to merge 2 commits intoSainsburyWellcomeCentre:mainfrom
glopesdev:code-coverage-report

Conversation

@glopesdev
Copy link
Contributor

This prevents checks failing on forks. Potentially related to codecov/feedback#301 and codecov/engineering-team#1574.

@glopesdev glopesdev requested a review from lochhh March 5, 2026 13:36
@glopesdev glopesdev added the fix Pull request that fixes an issue label Mar 5, 2026
This prevents checks failing on forks.
@glopesdev glopesdev force-pushed the code-coverage-report branch from 3dcec97 to 7fe7634 Compare March 5, 2026 13:38
@glopesdev
Copy link
Contributor Author

glopesdev commented Mar 5, 2026

@lochhh This currently prevents PRs and contributor forks. Reading through the referenced issues and various other PRs I admit I was left pretty confused about the recommended course of action. Some projects simply disable fail_ci_if_error for codecov and call it a day.

Others seem to go different levels of tortuous routes between configuring the org to accept tokenless uploading of reports (not sure if this is still allowed) to detecting whether secrets are configured or if the CI is running in a fork. I tried to survey a few of these and did not find anything satisfying so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix Pull request that fixes an issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant