OSTREE-PRUNE(1)

okay bestie, this is the ostree prune page from the OSTREE PRUNE(1) manual, and it’s giving “cleanup era” energy 🧹✨

✨ NAME ✨

ostree-prune — Search for unreachable objects 💅

✨ SYNOPSIS ✨

ostree prune [OPTIONS...]

✨ DESCRIPTION ✨

So what this does is it searches for unreachable objects in the current repository. If unreachable objects are found, the command delete them to free space 😭 — yes, it deletes them. If you invoke the --no-prune option, the command will just print unreachable objects and recommend deleting them. Look-but-don’t-touch mode, no cap 🫶

✨ OPTIONS ✨

• --no-prune — Only display unreachable objects; don't delete. It’s the “I’m just looking” option 📸
• --refs-only — Only compute reachability via refs. That’s the whole vibe.
• --delete-commit=COMMIT — Specify a COMMIT to delete. Bye bestie 👋
• --keep-younger-than=DATE — All commits older than DATE will be pruned. The format of DATE is the same as that accepted by the GNU date utility — for more information see info date 📅
• --keep-unreferenced-younger-than=DATE — Keep otherwise unreferenced commits newer than DATE. This is useful when commits may be created concurrently with pruning. The format of DATE is the same as that accepted by the GNU date utility — for more information see info date. Commits timestamped exactly at DATE are kept. So yes, exactly-at-DATE commits get to stay 😌
• --depth=DEPTH — Only traverse DEPTH (integer) parents for each commit (default: -1=infinite). Infinite is the default, no cap, main character energy ♾️
• --static-deltas-only=DEPTH — This option may currently only be used in combination with --delete-commit. Previous versions of ostree silently accepted the option without that, and ignored it. However, there are desired use cases for pruning just static deltas (while retaining the commits), and it’s likely that at some point this option will be supported for use cases outside of just --delete-commit. So rn: pair it with --delete-commit, bestie 🫡
• --commit-only — Only traverse and delete commit objects. This leaves orphaned meta and content objects, which can be cleaned up with another prune invocation. One may want to use this option to cheaply delete multiple commits, and then clean up with a more expensive prune at the end. Cheap now, expensive cleanup later — strategic 💸✨

✨ EXAMPLE ✨

       $ ostree prune

                   Total objects: 25627
                   No unreachable objects

okay bestie, that’s the whole page 💖 it’s from the OSTree source/version — manual page OSTREE PRUNE(1) — and there’s no date in the footer to report, so this is the cute sign-off, periodt 🌈✨