From 3bfa07fc5d9f61594c2f39d57d0d586089215686 Mon Sep 17 00:00:00 2001 From: kshitijk4poor <82637225+kshitijk4poor@users.noreply.github.com> Date: Thu, 3 Sep 2026 00:46:57 +0530 Subject: [PATCH] docs(curator): carry over the #91449 growth rationale for the .git exclusion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Folds the incident explanation from #91458 (@liuhao1024) into the comment on _EXCLUDE_TOP_LEVEL so the reason .git is excluded — compounding snapshot growth, not just rollback safety — survives next to the set. Co-authored-by: liuhao1024 --- agent/curator_backup.py | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/agent/curator_backup.py b/agent/curator_backup.py index 9a1c0d81a9..bd98ebb451 100644 --- a/agent/curator_backup.py +++ b/agent/curator_backup.py @@ -61,7 +61,12 @@ DEFAULT_KEEP = 5 # Entries under skills/ that should NEVER be rolled up into a snapshot. # .hub/ is managed by the skills hub; rolling it back would break lockfile # invariants. .curator_backups is the backup dir itself — recursion bomb. -# .git is repository metadata — rolling it back would break git tracking. +# .git is repository metadata — rolling it back would break git tracking, +# and snapshots that include it grow with the full history: once backups +# are committed back, the history contains prior backups, so each snapshot +# is bigger than the last (observed: 38MB of skills inflating to 24GB in +# weeks, #91449). ``_tar_filter`` below applies the same set to nested +# paths, so a ``.git`` inside an individual skill dir is skipped too. _EXCLUDE_TOP_LEVEL = {".curator_backups", ".hub", ".git"} # Snapshot id regex: UTC ISO with colons replaced by dashes so the filename