Skip to content

chore(specter): untrack stale .specter-results.json #568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
remyluslosius merged 2 commits into from
Jun 16, 2026
+5 −4,907
Merged

chore(specter): untrack stale .specter-results.json #568

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4863c60
chore(specter): untrack stale .specter-results.json
remyluslosius Jun 16, 2026
75bd801
Merge branch 'main' into chore/untrack-specter-results
remyluslosius Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -947,7 +947,11 @@ Thumbs.db
coverage.html
coverage.txt

# Transient specter run output (frontend); root .specter-results.json is tracked intentionally
# Transient specter run output. CI regenerates these from a real
# go test -json + vitest JUnit run (specter ingest), so a committed copy is
# never consumed by the gate — it only goes stale and produces misleading
# local `specter coverage` reports. Both are ignored.
.specter-results.json
frontend/.specter-results.json

# Local dev bootstrap state (scripts/openwatch.sh)
Expand Down
Loading
Loading