Skip to content

chore: drop a stray vitest reporter output committed in #34 - #35

Merged
ancsingabor merged 1 commit into
mainfrom
chore/drop-stray-vitest-output
Oct 1, 2026
Merged

ancsingabor merged 1 commit into
mainfrom
chore/drop-stray-vitest-output

Conversation

@ancsingabor

Copy link
Copy Markdown
Owner

.vitest/json/output.json (105 KB of generated test-run JSON) landed in #34. I produced it running vitest --reporter=json while re-deriving the lib/corpus/ test count for ADR-023, then staged the docs sweep with git add -A.

It is build output and nobody's input. Removed, and .vitest/ is now in .gitignore so the next reporter run cannot repeat it.

Worth one line of self-criticism: git add -A after a session that ran tooling is how generated files get committed, and a 105 KB blob in an otherwise docs-only diff is exactly the noise ADR-003 keeps the corpus out of the repo to avoid. git status before staging would have shown it.

🤖 Generated with Claude Code

`.vitest/json/output.json` (105 KB) landed in the ADR sweep because I ran
`vitest --reporter=json` while re-deriving a test count and then staged with
`git add -A`. It is build output, it is nobody's input, and a 105 KB generated
blob in a docs-only PR is exactly the kind of diff noise ADR-003 keeps the
corpus out of the repo to avoid.

Removed, and `.vitest/` is now ignored so the next reporter run cannot repeat
it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ancsingabor
ancsingabor merged commit 15d949a into main Oct 1, 2026
2 checks passed
@ancsingabor
ancsingabor deleted the chore/drop-stray-vitest-output branch October 1, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant