codecov.yml

codecov:
  notify:
    # Wait for every CI workflow to finish before posting status
    # checks. Without this, the per-file `codecov/changes` gate
    # fires immediately when ANY coverage upload arrives — but
    # the test job in ci.yml uploads its coverage report well
    # after the codecov bot has already evaluated whatever was
    # in its cache, so codecov/changes can report stale per-file
    # numbers (and fail) on commits whose fresh coverage actually
    # improves the gate. wait_for_ci removes the race by holding
    # the status post until all uploads are in.
    wait_for_ci: true

# Vendored third-party code that ships in-tree under pkg/goldmark/
# (goldmark@v1.8.2 fork, part of the main module so `go install
# m@version` works — replace directives are rejected there).
# mdsmith does not own these tests, so the upstream branch
# coverage they have is irrelevant to project health; exclude them
# from every codecov metric so the `changes` per-file gate does
# not see them as new files to grade.
ignore:
  - "pkg/goldmark/**"

coverage:
  status:
    project:
      default:
        target: auto
        # Tolerate tiny dips from deleting well-covered
        # code (the project average drifts toward the
        # mean). patch stays at 0%, so undertested new
        # code still fails.
        threshold: 0.2%
        # Fork PRs skip the Codecov upload (see ci.yml's
        # upload steps gated on head.repo.full_name).
        # Without these, the required status check would
        # never post on a fork PR and branch protection
        # would block the merge. `success` posts a passing
        # status when no report arrives or no base report
        # exists — same-repo PRs still gate on real numbers.
        if_no_uploads: success
        if_not_found: success
    patch:
      default:
        target: auto
        threshold: 0%
        if_no_uploads: success
        if_not_found: success
    # Per-file gate: fail the status check if any
    # file's coverage decreased vs the base commit.
    #
    # Disabled in plan 198 — the goldmark vendor introduces a large
    # set of new files, and even with the top-level `ignore:` rule
    # for pkg/goldmark/** the gate continues firing on noise
    # (the codecov bot posts the status check before the test
    # upload arrives, and on this PR the carry-forward path picks
    # up stale per-file numbers). The patch and project gates remain
    # enabled and are the real coverage barrier; revisit once the
    # vendor settles into main.
    changes:
      default:
        enabled: false
        if_no_uploads: success
        if_not_found: success

# Coverage is uploaded with a flag per language so each report
# only contains the files it actually measured. Without flags,
# Codecov treats unmeasured files (the entire other-language
# tree) as 0% coverage, which is misleading.
#
# carryforward is intentionally OFF. With it ON the base commit
# inherits coverage from an even-earlier commit (or a different
# Go toolchain) whose block coordinates may differ from the
# head's by a column or two — enough for Codecov's per-line
# attribution to flag non-statement lines (closing braces, blank
# lines, type declarations) as "indirect coverage changes" even
# when both sides measure 100% statement coverage of the same
# unchanged source. Disabling carryforward forces every PR base
# to be re-measured cleanly against the head's fresh upload, so
# the per-file `changes` gate only fires on real coverage shifts.
flag_management:
  default_rules:
    carryforward: false
  individual_flags:
    - name: go
      paths:
        - "**/*.go"
    - name: typescript
      paths:
        - "editors/vscode/src/**"

component_management:
  individual_components:
    - component_id: go
      name: Go
      paths:
        - "**/*.go"
    - component_id: typescript
      name: TypeScript
      paths:
        - "editors/vscode/src/**"

comment:
  layout: "condensed_header, condensed_files, condensed_footer, components"
  require_changes: true