[BUG] Tokenless upload rejected for a public fork PR

オープン
#1,978 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, python
領域
ci-cd, devops

調査の方向性

Start by comparing the failing codecov-action@v4 GitHub Actions job with the successful authenticated main run, then inspect how the action and CLI handle fork metadata and tokenless uploads. Reproduce against a public fork PR and determine whether the rejection comes from the client workflow or Codecov authentication or repository synchronization; done means the cause is established and a fix or actionable configuration guidance is verified.

索引モデルが issue の本文から書いたものです。

説明

Describe the bug

The Codecov upload for public fork PR #189 in jsoizo/kotlin-csv failed with:

HTTP 400: Token required - not valid tokenless upload

The original GitHub Actions job uses codecov/codecov-action@v4 and CLI
11.3.2. It detects the fork and supplies a colon-prefixed branch.
Authenticated main uploads succeed.

The cause is not established. An earlier version of this report emphasized
repository synchronization too strongly; that is only an unconfirmed
possibility based on similar reports.

Observed failure

PR: https://github.com/jsoizo/kotlin-csv/pull/189

Failing job:
https://github.com/jsoizo/kotlin-csv/actions/runs/41361427049/job/128587373730

Metadata in the original job:

  • Repository slug: jsoizo/kotlin-csv
  • Branch: Alox1d:bugfix/utf8-surrogate-pairs
  • Commit: d0029f4f349c2c00b0272e4a1a105da30a926179
  • Pull request: 189
  • Git service: github

Additional investigation and limits

Local CLI 11.3.2 replays with this metadata also returned HTTP 400 for
create-commit and upload-coverage. The latter used a real Kover report
generated from the exact commit after all 258 JVM tests passed.

These were local CLI runs, not a validation of the current v7 Action in a
GitHub fork PR. We have not established whether upgrading the Action fixes
the original workflow.

The Codecov public API reports private: false, active: true,
activated: true, and author jsoizo:

https://api.codecov.io/api/v2/github/jsoizo/repos/kotlin-csv/

Successful authenticated main run:
https://github.com/jsoizo/kotlin-csv/actions/runs/42434464353

The repository was previously doyaaaaaken/kotlin-csv, with GitHub repository
ID 200859123. We do not know whether the ownership change is relevant.

Expected behavior

Coverage uploads from public fork PRs succeed without exposing the upstream
repository token.

Environment

  • Git host: GitHub
  • CI: GitHub Actions
  • Original runner: Ubuntu 24.04
  • Action in the failing job: codecov/codecov-action@v4
  • CLI: 11.3.2

What would you recommend checking to distinguish a client/workflow issue
from a Codecov-side authentication or repository synchronization issue?

Repository tracking issue:
https://github.com/jsoizo/kotlin-csv/issues/193

主要言語
Python
スター
1.7k
フォーク
260
PR マージ指標
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codecov/codecov-action のほかの issue

codecov/codecov-action の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。