fix(test): gitignore README_AI under char_graphbuffer fixture (#135) - #136
Merged
Conversation
scan-all (root config includes tests/) generated README_AI.md inside tests/fixtures/char_graphbuffer/ — the #101 characterization fixture that must stay byte-identical. The files weren't gitignored, so `git add -A` committed them, drifted the baseline goldens, and broke test_structural_readmes / test_enrich_prompts_and_frozen_ai_readmes on CI (caught in PR #134 after push). Ignore ONLY char_graphbuffer — other fixture READMEs (cli_parse/, graph_export/) are legit tracked navigation assets and stay committable. Verified: char_graphbuffer READMEs now ignored, legit ones still trackable, and a simulated scan-all regen no longer leaks into `git status`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 15, 2026
dreamlx
added a commit
that referenced
this pull request
Aug 15, 2026
…135 residual) (#170) Repo-root scan-all generates README_AI.md inside tests/fixtures/ char_graphbuffer/ (gitignored by #136, but still on local disk). The characterization copytree carried them into the scan; GH #38's enrichment-preserve logic kept the stale '<!-- enrichment: ok -->' markers across the structural rewrite and drifted the goldens. CI was green (clean checkout has no untracked files) while local runs failed permanently. ignore_patterns in the fixture copy makes the test own its pristine-input guarantee.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root-fix for #135 — the scan-all fixture-pollution landmine that broke CI in
PR #134.
codeindex scan-all(root configinclude: tests/) walks test fixtures andgenerated
README_AI.mdinsidetests/fixtures/char_graphbuffer/— the #101characterization fixture that must stay byte-identical. The generated files
weren't gitignored, so
git add -Acommitted them → baseline goldens drifted →test_structural_readmes/test_enrich_prompts_and_frozen_ai_readmesred onCI (local stayed green because the polluted files matched what scan-all
produced — the classic "works on my disk" gap).
Fix
.gitignorenow blockstests/fixtures/char_graphbuffer/**/README_AI.mdspecifically. Scoped — other fixture READMEs (
cli_parse/,graph_export/) are legit tracked navigation assets and stay committable.Verification
char_graphbuffer/**/README_AI.md→ now ignored ✓cli_parse/README_AI.md,graph_export/project/README_AI.md→ stilltrackable ✓ (not over-broad)
git status(sogit add -Acan't re-commit it) ✓scan-all hook ran clean — no char_graphbuffer pollution
Why not the other options
.codeindex.yamlis gitignored, so alocal exclude never reaches CI.
.noindexsentinel: needs scan-all logic changes, out of scope.Closes #135.
🤖 Generated with Claude Code