
# CI is the authoritative writer of the drift/availability history: it runs daily from a
# stable vantage and commits what it observed. Local grade runs overwrite it, which produced a
# rebase conflict every time. Union-merge keeps both sides rather than failing the rebase; CI
# rewrites the file wholesale on its next run regardless.
data/history.json merge=union

# GitHub Actions downloads a source archive for every `uses:` invocation. Keep that archive to
# the Action runtime instead of shipping the curated registry, the cohort files, the captured
# fixtures, and the test suite to every consumer. The published dataset lives on the site; a
# consumer gating their own endpoint has no use for a copy of it.
/* export-ignore
/action -export-ignore
/action.yml -export-ignore
/CODE_OF_CONDUCT.md -export-ignore
/LICENSE -export-ignore
/pyproject.toml -export-ignore
/README.md -export-ignore
/SECURITY.md -export-ignore
/src -export-ignore
# The vendored design system (stylesheets, fonts, icons) exists to build the site. The Action
# runtime a consumer downloads runs `check` and never builds a site, so the 50-odd asset files
# stay out of the archive the same way the dataset does. A checkout has them; the archive is
# the Action runtime, bounded on purpose.
/src/fhir_scorecard/assets export-ignore

# Retained specification pages are evidence: keep their bytes exactly as fetched so the
# SHA-256 values in corpus/SOURCES.json stay true on every checkout. They serve the optional
# narration layer, not the Action runtime, so they stay out of the archive with the dataset.
/corpus/** -text
