jj-util-gc(1)

💅 jj-util-gc — ok bestie, let's talk trash (collection) 💅

So this is a page from the General Commands Manual, about a little command called jj-util-gc(1). Grab a snack, we're cleaning up. 🧹✨

---

🌸 NAME 🌸

jj-util-gc — Run backend-dependent garbage collection

---

✨ SYNOPSIS ✨

jj util gc [--expire] [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help]

---

🧚 DESCRIPTION 🧚

Run backend-dependent garbage collection.

Okay so real talk, if you want to garbage-collect old operations and the commits/objects they reference, you gotta run jj op abandon ..<some old operation> before jj util gc. Do it in that order, bestie, that's the whole vibe. 🫶

---

🎀 OPTIONS 🎀

• --expire <EXPIRE> — the time threshold ⏳ By default, only obsolete objects and operations older than 2 weeks are pruned.

Only the string "now" can be passed to this parameter. Fr fr, that's it. Support for arbitrary absolute and relative timestamps will come in a subsequent release. (We're manifesting it. 🙏)

• -h, --help — Print help (see a summary with -h) 📖

---

👑 GLOBAL OPTIONS 👑

These ones work everywhere, they're the main characters of the CLI.

• -R, --repository <REPOSITORY> — Path to repository to operate on 📁 By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. So it's like, going up the family tree looking for its home. 🌳
• --ignore-working-copy — Don't snapshot the working copy, and don't update it 🙈 By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (@). If you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use --ignore-working-copy. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.

Loading the repository at a specific operation with --at-operation implies --ignore-working-copy. It's giving package deal. 🎁

• --no-integrate-operation — Run the command as usual but don't integrate any operations 🚫 When this option is given, the operations will still be created as usual but they will not be integrated to the operation log. The working copy will also not be updated.

The command will print the resulting operation ID. You can pass that to e.g. jj --at-op to inspect the resulting repo state, or you can pass it to jj op restore to restore the repo to that state. You can also pass the ID to jj op integrate to integrate the operation. So many options, so much power. 💅

Note that this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. Read that one again, bestie. 😭

• --ignore-immutable — Allow rewriting immutable commits 🔓 By default, Jujutsu prevents rewriting commits in the configured set of immutable commits. This option disables that check and lets you rewrite any commit but the root commit.

This option only affects the check. It does not affect the immutable_heads() revset or the immutable template keyword. Don't come for those, they did nothing wrong. 🫶

• --at-operation <AT_OPERATION> — Operation to load the repo at ⏪ Operation to load the repo at. By default, Jujutsu loads the repo at the most recent operation, or at the merge of the divergent operations if any.

You can use --at-op=<operation ID> to see what the repo looked like at an earlier operation. For example jj --at-op=<operation ID> st will show you what jj st would have shown you when the given operation had just finished. --at-op=@ is pretty much the same as the default except that divergent operations will never be merged.

Use jj op log to find the operation ID you want. Any unambiguous prefix of the operation ID is enough. Short queen ID, we love to see it. 👑

When loading the repo at an earlier operation, the working copy will be ignored, as if --ignore-working-copy had been specified.

It is possible to run mutating commands when loading the repo at an earlier operation. Doing that is equivalent to having run concurrent commands starting at the earlier operation. There's rarely a reason to do that, but it is possible. Chaos is an option, not a requirement. 🌈

• --debug — Enable debug logging 🐛
• --color <WHEN> — When to colorize output 🌈 Possible values:
  • always
  • never
  • debug
  • auto
• --quiet — Silence non-primary command output 🤫 For example, jj file list will still list files, but it won't tell you if the working copy was snapshotted or if descendants were rebased.

Warnings and errors will still be printed. Those are non-negotiable. 💀

• --no-pager — Disable the pager 📄
• --config <NAME=VALUE> — Additional configuration options (can be repeated) ⚙️ The name should be specified as TOML dotted keys. The value should be specified as a TOML expression. If string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted.
• --config-file <PATH> — Additional configuration files (can be repeated) 🗂️

---

You can repeat --config and --config-file as many times as you want, bestie. Stack 'em. 🥞

---

💖 k, bye bestie 💖

That's the whole page! This one lives in the gc source, filed under manual jj-util-gc(1) — and ngl there's no date on this one, so we're just going off the source and the manual name. Stay clean out there, slay, and don't forget to jj op abandon first. Periodt. 💅✨🦋