chore: untrack results/session-*.json (repo bloat)#2
Draft
cloudygeek wants to merge 1 commit into
Draft
Conversation
Removes 1,450 per-session state dumps from git tracking.
Files stay on disk so the local dashboard fallback continues to work;
future clones will not include them (working-tree-clean after clone).
Before: 1,450 tracked session-*.json files, results/ ~2.5 GB on disk.
After: 0 tracked session-*.json files; adversarial-judge-*.json (43)
and all other results/ files remain tracked.
Session state is Dynamo-backed in production — these files are
local-dev / legacy fallback artefacts with no production value.
The .gitignore rule results/session-*.json is also added here
(it was planned for 2026-05-25 but was missing from the index).
This commit only untracks files; it does NOT rewrite history.
The ~2.5 GB remains in past commits. See Option 2 in the PR description
if history compaction is ever needed.
https://claude.ai/code/session_01Nt16Y181p8uwiWXfc5Q4Mi
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
2 participants
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
Before: 1,450 tracked
results/session-*.jsonfiles;results/folder ~2.5 GB on disk.After: 0 tracked
results/session-*.jsonfiles; all 43results/adversarial-judge-*.jsonresearch files remain tracked and untouched.What this does
git rm --cached results/session-*.json— untracks only, files stay on disk.results/session-*.jsonto.gitignoreso future dumps are never accidentally committed.git clones will get a clean working tree (no session dumps); the local dashboard fallback (results/*.json) continues to work on machines that already have the files.What this does NOT do
results/adversarial-judge-*.json(43 files, deliberate research data).Options for Adrian
Option 1 — This PR (safe, reversible)
Merge this draft when ready. Untracks the 1,450 session dumps, stops future commits from re-adding them. Does not shrink the git history or clone size — the blobs remain reachable from past commits.
Option 2 — History rewrite (DO NOT execute without coordination)
Use
git filter-repoor BFG Repo Cleaner to purge the session-dump blobs from all past commits. This would reclaim the ~2.5 GB from clone size andgit loghistory. Destructive: rewrites all SHAs, requires a coordinated force-push, and every collaborator must re-clone or rebase. Only worth it if clone / CI checkout time is a real pain point. Steps on request.Scheduled maintenance — no functional code changes.
Generated by Claude Code