inconsistent coverage reports after migrating repos to new GitHub and codecov orgs

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
github, github-actions
領域
ci-cd, testing

調査の方向性

The report is about the hosted Codecov service's per-organization behaviour, so the repo's own code is only the upload side: start with the global YAML in the issue body and the codecov/project and PR-comment outputs it is supposed to produce. The linked codecov/worker writers.py lines show the comment conditional the reporter suspects. Done would mean a maintainer confirming the cause, since the fix probably lives in the Codecov service rather than in this action.

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

説明

bug

Describe the bug

After transferring public repositories from LizardByte to other GitHub organizations, Codecov behaves differently despite the same global YAML configuration.

All three destination organizations are using the Free plan.

Organization Repository codecov/project PR report
Themerr Themerr Missing Short, patch-only report
KokoStreamTV Koko Missing Short, patch-only report
SunshineStream Sunshine Present Full coverage comparison

One potentially relevant difference: SunshineStream has existed for a long time but was unused until these migrations. Themerr and KokoStreamTV are newly created organizations.

To Reproduce

  1. Transfer public repositories from LizardByte to the destination organizations.

  2. Configure each destination Codecov organization with the same global YAML:

    ---
    codecov:
      max_report_age: off
    
    coverage:
      status:
        project:
          default:
            target: auto
            threshold: 10%
    
    comment:
      layout: "header, reach, diff, flags, files, footer"
      behavior: default
      require_changes: false
    
    ignore:
      - "tests"
      - "third-party"
    
  3. Run GitHub Actions to upload coverage for the default branch and a pull request.

  4. Compare the resulting checks and comments:

The commit-level resolved YAML includes the configured project status and comment layout in all three repositories. No repository Codecov YAML files override the global configuration. Base and head coverage reports are available.

Expected behavior

Each public repository should receive:

  • A codecov/project check using the configured target and threshold.
  • A full PR report containing the project coverage comparison and configured layout.

Regression

The affected repositories received project coverage checks and full reports under LizardByte. The discrepancy appeared after transferring them to the newly created organizations.

Sunshine continues working after transfer to the older SunshineStream organization.

Screenshots

The linked GitHub comments show the affected and working reports.

Product Area

Coverage: GitHub status checks and pull request comments.

Versions

  • Git Host: GitHub.com
  • CI/CD: GitHub Actions
  • Codecov: Hosted service
  • Plan: Free in all three destination organizations

Commit and CI link

Affected example: Themerr PR #724

Additional context

I also tried explicitly adding this under comment:

hide_project_coverage: false

The resolved YAML confirms that this setting was applied.

On Themerr, it removed the “All tests successful. No failed tests found.” message without restoring project coverage details or the missing project check. On Sunshine, it produced no visible change; the full report already worked.

The disappearing test-success message appears consistent with this conditional in Codecov's published comment renderer:
https://github.com/codecov/worker/blob/main/services/notification/notifiers/mixins/message/writers.py#L53-L61

However, all three organizations show Free, so I am not assuming this indicates a Team subscription.

Could different defaults or internal reporting state for older versus newly created organizations explain this behavior? Is there anything that needs to be reset or corrected after the repository transfers?

Potentially related: https://github.com/codecov/codecov-action/issues/1979

That issue reports successful coverage uploads and an available codecov/patch result, while codecov/project remains running.

My situation differs: codecov/project is absent entirely, and the PR comment also omits the project coverage comparison. I’m unsure whether these share an underlying cause, but wanted to mention the similar recent report.

主要言語
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 を短くまとめたダイジェスト。