chore(specter): untrack stale .specter-results.json#568
Merged
Conversation
CI regenerates the results file from a real go test -json + vitest JUnit run (specter ingest -> sync), so the committed copy is never consumed by the gate. It only drifts and produces misleading local `specter coverage` reports (it showed a bogus 60%/NONE picture because it predated a full ingest). Remove it from tracking and gitignore it alongside the frontend one; scripts/check-go-spec-coverage.sh already runs without it.
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.
Split out of #563 so the backlog-docs changes and this repo-hygiene chore review independently.
.specter-results.jsonwas committed but nothing consumes the committed copy — CI regenerates it from a realgo test -json+ vitest JUnit run (specter ingest→sync) and uploads the fresh one as an artifact;scripts/check-go-spec-coverage.shruns without it. The committed snapshot only drifts and produces misleading localspecter coveragereports (it's what showed a bogus 60%/NONEpicture in a recent session).This
git rm --cacheds it and gitignores it alongside the already-ignoredfrontend/.specter-results.json. The "tracked intentionally" comment had no actual consumer behind it.