mirror of
https://github.com/ZmnSCPxj/clboss.git
synced 2026-08-13 12:33:20 +02:00
b70308d5bd
CLBOSS has had Codecov uploads in CI for a while but no codecov.yml in-tree, so the per-PR (patch) coverage check has been running on Codecov's default 70% target. Most CLBOSS modules -- including the ones touched by the in-flight v26.06 compatibility stack -- have no unit tests at all, so PRs to those modules fail CI regardless of whether the change is correct. Make the policy explicit: - Project: target=auto, threshold=1%. Codecov still fails status if overall coverage drops more than 1% from baseline, guarding against bulk regression. - Patch: informational=true. Codecov reports patch coverage as a PR comment but never fails the check. Suits a codebase where coverage grows module-by-module rather than being gated per-PR. Improving overall coverage remains a worthwhile ongoing project; this just stops the per-PR check from blocking work in modules that currently have no test infrastructure.
22 lines
674 B
YAML
22 lines
674 B
YAML
# Codecov configuration for CLBOSS.
|
|
#
|
|
# Project-level: still guards against bulk coverage regression
|
|
# (overall coverage may not drop more than 1% from the master
|
|
# baseline).
|
|
#
|
|
# Patch-level: informational only. Most CLBOSS modules predate
|
|
# the unit-test infrastructure and have no existing tests, so
|
|
# requiring a fixed minimum patch coverage on every PR would
|
|
# block work in those modules regardless of correctness.
|
|
# Codecov still reports the per-PR coverage delta as a comment;
|
|
# it just does not fail the status check.
|
|
|
|
coverage:
|
|
status:
|
|
project:
|
|
default:
|
|
target: auto
|
|
threshold: 1%
|
|
patch:
|
|
default:
|
|
informational: true
|