Without this, refresh.yml scrapes successfully then commits nothing because git add corpus is a no-op against the gitignore. chroma/ and bm25/ stay ignored (rebuilt by rag.index --rebuild at CI time).
Without this, refresh.yml scrapes successfully then commits nothing because `git add corpus` is a no-op against the gitignore. chroma/ and bm25/ stay ignored (rebuilt by `rag.index --rebuild` at CI time).
PLAN.md's design has corpus/ committed and chroma/+bm25/ regenerated
at CI time. The scaffold's .gitignore over-ignored corpus/, which
meant refresh.yml's `git add bundles.json corpus` silently dropped
the corpus and the changed-detection logic always reported "no
changes — skipping reindex and image build". Net result: refresh
would scrape successfully and then ship nothing.
chroma/ and bm25/ stay ignored — those are rebuilt by
`python -m rag.index --rebuild` before docker build copies them.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
justin
merged commit 21500b1aaa into main2026-05-22 13:38:23 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Without this, refresh.yml scrapes successfully then commits nothing because
git add corpusis a no-op against the gitignore. chroma/ and bm25/ stay ignored (rebuilt byrag.index --rebuildat CI time).