Uploads rejected "Token required because branch is protected" despite active repo, tokenless org, and valid repository upload token
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- authentication, ci-cd
Research direction
Start with the codecov-action v7/codecov-cli upload flow and compare the failed repository-token requests with the successful tokenless upload for commit 7a4ff64. Review the ingest responses and the repository's activation state; done means the repository token is accepted consistently or the token-requirement cause is explained.
Written by the indexing model from the issue text.
Description
Repo: ra8844/core (public fork of home-assistant/core), branch tailscale-oauth-client-credentials, commit 97076c15672d26773312dea45d889963bcbe3dbb, uploading via codecov-action v7 (codecov-cli), flag full-suite.
Coverage uploads are rejected at ingest with {"message":"Token required because branch is protected"} even though every UI signal says the upload should be accepted:
- The repo shows active (Configuration → General shows the "Deactivate" button in the Danger Zone).
- The org banner says "Your org no longer requires upload tokens. You can upload without a token."
- The upload was made with the repository upload token copied from that same Configuration page, and the CI log confirms it was passed (
upload-coverage -t <redacted>).
What we tried, all on the same run (https://github.com/ra8844/core/actions/runs/30637059898):
- Codecov API access token as the upload token →
{"message":"Repository not found"}(~14:47 UTC 2026-07-31) - Global upload token →
{"message":"Token required because branch is protected"}(~14:55 UTC) - Repository upload token → same "branch is protected" error (~15:03 UTC)
Additional context: a tokenless upload to this same repo/branch succeeded on 2026-07-20 (commit 7a4ff64, still visible on the dashboard — 100% of 194 lines). At some point after that, the repo showed as deactivated; after signing in on 2026-07-31 it shows active again. It looks like the ingest side has stale activation/token-requirement state that disagrees with what the UI reports.
Could you reconcile the repo's activation/token state, or explain what would make the repository's own upload token be rejected with a "token required" error?
- Dominant language
- No language data
- Stars
- 52
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codecov/feedback
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePossibly taken @ChiptenIsCool claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 1-2 days Newbie friendliness 42/100
All issues in codecov/feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
qte77/cc-senses-plugin#163 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
checks: `delegate-call-risk` matches a non-existent `env.try_call` and misses `try_invoke_contract`Openbug checks-crate good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
SorobanGuard/Guard-CLI#1063 ·
-
bug platform-desktop platform-windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Termix-SSH/Termix#1951 · 2 comments ·
Maintainers usually reply within 1 day