Follow-up to #63. The coverage workflow was modernized (ubuntu + setup-r-dependencies + covr::to_cobertura + codecov-action@v4, codecov.yml with 90% gate, badge fixed) and merged in non-blocking mode (fail_ci_if_error: false), so CI stays green.
Blocker: codecov-action@v4 needs a CODECOV_TOKEN secret, and getting the token requires the Codecov GitHub App on the fastverse org (or access to app.codecov.io → fastverse/kit → Settings). Repo maintainer rights are not enough to approve the app — needs an org admin. An install request for the app on kit is already pending approval.
Ask for @SebKrantz: either (a) approve/install the Codecov app on the org (github.com/apps/codecov → Configure → fastverse/kit), after which the token can be copied and stored as the CODECOV_TOKEN repo secret, or (b) paste the existing repo upload token so it can be stored (Settings → Secrets and variables → Actions → New repository secret).
After the secret exists: flip fail_ci_if_error back to true in test-coverage.yaml and confirm the badge leaves “unknown”. Until then, no action needed — current state is intentionally green.
Follow-up to #63. The coverage workflow was modernized (ubuntu + setup-r-dependencies + covr::to_cobertura + codecov-action@v4, codecov.yml with 90% gate, badge fixed) and merged in non-blocking mode (fail_ci_if_error: false), so CI stays green.
Blocker: codecov-action@v4 needs a CODECOV_TOKEN secret, and getting the token requires the Codecov GitHub App on the fastverse org (or access to app.codecov.io → fastverse/kit → Settings). Repo maintainer rights are not enough to approve the app — needs an org admin. An install request for the app on kit is already pending approval.
Ask for @SebKrantz: either (a) approve/install the Codecov app on the org (github.com/apps/codecov → Configure → fastverse/kit), after which the token can be copied and stored as the CODECOV_TOKEN repo secret, or (b) paste the existing repo upload token so it can be stored (Settings → Secrets and variables → Actions → New repository secret).
After the secret exists: flip fail_ci_if_error back to true in test-coverage.yaml and confirm the badge leaves “unknown”. Until then, no action needed — current state is intentionally green.