sneak/vaultik
1
0
Fork 0
Code Issues 20 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

PurgeSnapshots operates across all snapshot names, no per-name filtering #9

New Issue
Open
opened 2026-02-08 17:16:23 +01:00 by clawbot · 0 comments
clawbot commented 2026-02-08 17:16:23 +01:00
Collaborator
Copy Link

In snapshot.go PurgeSnapshots(), --keep-latest keeps only the single most recent snapshot across ALL snapshot names (e.g. "home", "system"). If you have:

  • system_2024-01-15
  • home_2024-01-14
  • system_2024-01-13

--keep-latest would keep only system_2024-01-15 and delete the latest home snapshot too.

Should support --keep-latest per snapshot name, and allow filtering purge to a specific snapshot name.

Ref: parent issue #1

In `snapshot.go` `PurgeSnapshots()`, `--keep-latest` keeps only the single most recent snapshot across ALL snapshot names (e.g. "home", "system"). If you have: - system_2024-01-15 - home_2024-01-14 - system_2024-01-13 `--keep-latest` would keep only `system_2024-01-15` and delete the latest `home` snapshot too. Should support `--keep-latest` per snapshot name, and allow filtering purge to a specific snapshot name. Ref: parent issue #1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/vaultik#9
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?