Public repo loses project coverage, flags and components after transfer to an organization

[KapJI]

Describe the bug
I transferred a public repo from my personal account to a new organization. Nothing else
changed - same codecov.yml, same workflow, repo stayed public.

Since then:

• Project coverage, Flags and Components show "Available with Pro Plan" in Settings.
  All three said "Configured" before.
• The PR comment dropped to two lines and codecov/project stopped posting.
• Member activation shows "1 activated member of 1 available seats". My personal
  account shows 5 seats.

The org has 2 repos, both public, no private ones. Your pricing page lists Developer
as "1 maximum user (unlimited for open source)", so I would not expect a seat limit
or gated features here.

The data is still being computed - the flags and components pages for the PR show
everything. Only the reporting is withheld.

Both symptoms look like one cause: the org is not being treated as open source.

Environment (please complete the following information):

• Repo: https://github.com/cgt-calc/capital-gains-calculator (public, MIT)
• Was: KapJI/capital-gains-calculator (also public)
• Transferred: 2026-08-26 ~12:45 UTC
• GitHub repo ID unchanged: 334744265
• Plan: Developer
• CI: GitHub Actions, codecov-action@v7, 6 parallel uploads

To Reproduce

1. Public repo on a personal account, codecov.yml with components and flags.
   PR comments include project coverage, flags and components.
2. Transfer it to a newly created org. Keep it public. Change nothing else.
3. Open a PR and wait for uploads to finish.
4. PR comment is now two lines. codecov/project never posts, codecov/patch does.
5. Settings shows Project coverage, Flags and Components as Pro-only.
6. The PR /flags and /components pages still show all the data.
7. Member activation shows 1 available seat.

Expected behavior
A public repo keeps project coverage, flags and components after a transfer, and an
org with only public repos is not seat limited.

Screenshots

Additional context
Codecov comment before, under KapJI:
cgt-calc/capital-gains-calculator#988 (comment)

Codecov comment after, under cgt-calc:
cgt-calc/capital-gains-calculator#1019 (comment)

Data still present:
https://app.codecov.io/gh/cgt-calc/capital-gains-calculator/pull/1020/components

The API reports the repo as public:

GET https://api.codecov.io/api/v2/github/cgt-calc/repos/capital-gains-calculator/
{"name": "capital-gains-calculator", "private": false, "active": true}

Other community OSS orgs still get these features on public repos, for example
aio-libs/aiohttp, u-root/u-root and psychopy/psychopy, all within the last day.

The transfer also created a second Codecov project instead of following the rename.
Coverage history stayed under KapJI/capital-gains-calculator (367 commits); the new
one started empty. Deactivating the old project did not help.

Related: #938

Questions

1. Should the open source exemption apply to orgs? Other OSS orgs appear to have it.
2. Does it need provisioning for a newly created org?
3. Can it be enabled for cgt-calc?

[thomasrockhu-codecov]

@KapJI your personal account is on an older grandfathered plan which is why you see that difference

[KapJI]

@thomasrockhu-codecov Does this mean open source organizations are no longer covered?

[thomasrockhu-codecov]

@KapJI yes, unfortunately this has been true for about 2 years for private repos https://about.codecov.io/pricing/. Public repos still will receive flags/components

[KapJI]

@thomasrockhu-codecov But this repo is public?

[KapJI]

@thomasrockhu-codecov this repo is public, and was public before and after
the transfer.

Project coverage, flags, components and the full PR comment all worked on
this same repo, with the same codecov.yml, until I moved it from my personal
account to the org yesterday. The org has no private repos.

Is it possible to restore that functionality for cgt-calc?