tiennm99/thptqg2017

mirror of https://github.com/tiennm99/thptqg2017.git synced 2026-08-30 16:20:45 +00:00

Files

T

History

tiennm99 c5ef1f58ff docs(ci): say what the database cache key does, not what it means

The key is hashFiles over data/**, parser/** and datasets.json, so it
invalidates by path. Both the guide and the workflow comment described it by
intent instead — "a web or docs change restores the databases" — which the
previous commit disproved by paying for a full 348 MB rebuild to fix a comment
in datasets.json and a sentence in parser/README.md.

Over-invalidating is the safe direction, and narrowing the globs would mean
remembering to extend them for every future path that can change a database.
Record the trade rather than making it.

2026-08-15 17:58:28 +07:00

data-pipeline.md

docs: describe the design the code has, not the two before it

2026-08-15 17:35:09 +07:00

deployment-guide.md

docs(ci): say what the database cache key does, not what it means

2026-08-15 17:58:28 +07:00

project-overview.md

docs: describe the design the code has, not the two before it

2026-08-15 17:35:09 +07:00

README.md

docs: describe the design the code has, not the two before it

2026-08-15 17:35:09 +07:00

system-architecture.md

docs: describe the design the code has, not the two before it

2026-08-15 17:35:09 +07:00

README.md

Docs

project-overview.md — goal, scope, constraints, the datasets, history
system-architecture.md — data flow, the download and how it is kept, canonical schema, routing, how one frontend serves both exam years
data-pipeline.md — Excel parse quirks, per-dataset formats, overflow-sheet gotcha, expected row counts, verifying a rebuild
deployment-guide.md — GitHub Pages workflow, what the databases publish as, adding a dataset, rollback, troubleshooting