jj-file-untrack(1)

📦 version 0.46.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

💖 jj-file-untrack — the "okay bestie, we're done here" command 💖

Hey hi hello, this is the manual page for jj-file-untrack, a little member of the jj family (that's Jujutsu, the version control system, and yes she is that girl). This is section 1 of the General Commands Manual, and we're about to make untracking files make sense. 🦋

✨ NAME ✨

jj-file-untrack — stop tracking specified paths in the working copy.

Like, you know how you have files in your working copy that jj is keeping an eye on? This is the "okay actually no, we're not doing that anymore" button. Bye bestie 👋

🌸 SYNOPSIS 🌸

jj file untrack [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <FILESETS>

That's the whole shape of it, no cap. You give it some filesets and it stops tracking them. 🎀

💅 DESCRIPTION 💅

Stop tracking specified paths in the working copy.

That's the entire vibe. Paths you hand over stop being tracked. Periodt.

👑 OPTIONS 👑

  • -h, --help — Print help (see a summary with -h). Short version with -h, full lore dump without it. iykyk.
  • <FILESETS> — The paths to untrack. They must already be ignored — this is the key detail, don't skip it. 🙈

The paths could be ignored via a .gitignore or .git/info/exclude (in colocated workspaces).

🌈 GLOBAL OPTIONS 🌈

These are the big-league options that apply across the whole jj world. All of them are iconic in their own way. ✨

  • -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. It's giving "I'll find it myself, thanks". 🔍

  • --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. (Sneaky little implication, love that for it.)

  • --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.

Note that this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. 💀 So like, don't think this is a universal pause button, because it is not.
  • --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.

  • --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. (No need to type the whole thing, queen. 💅)

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. Live your truth I guess. 🧚

  • --debug — Enable debug logging. For when you need the receipts. 🔥
  • --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 stay loud, always. 😭)

  • --no-pager — Disable the pager. Straight to your terminal, no detour. 🚀
  • --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). Stack 'em up, bestie. 🌸

🫶 SEE ALSO 🫶

Nothing extra listed here, just the jj family energy. Go off. ⭐

Okay that's the whole page! This one's written by the jj crew and it's untrack business, dated and versioned as part of the Jujutsu manual pages — General Commands Manual, page jj-file-untrack(1). 💖 Go untrack something responsibly, bestie. 🎀

📦 where this page comes from