jj-file-track(1)

💖 jj-file-track — the manual, but make it make sense 💖

okay bestie, welcome to jj-file-track(1) from the General Commands Manual ✨ this is your girl's guide to telling jj "hey, actually track this file bestie" — let's get into it 💅

---

✨ NAME ✨

jj-file-track — start tracking specified paths in the working copy 🎀

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

So the whole point: you start tracking specified paths in the working copy. Periodt. 💖

If you pass no arguments, literally every path that is not ignored gets tracked. all of them. the whole vibe. ✨

Now here's the plot twist 🫶 by default, new files in the working copy are automatically tracked anyway, so this command has no effect — it's giving "you had one job and the job was already done." 😭

You can configure which paths get auto-tracked by setting snapshot.auto-track (like, say, to "none()" or "glob:**/*.rs"). And files that DON'T match that pattern? Those you can manually track with this very command, iykyk. The default pattern is all(). 👑

---

💅 OPTIONS 💅

• --include-ignored — track paths even if they're ignored or too large. like, by default jj file track will NOT track files that are ignored by .gitignore or that exceed the maximum file size. This flag overrides those restrictions and explicitly tracks the paths you named. she said "rules are a suggestion" 💀✨
• -h, --help — print help (see a summary with -h) 🎀
• <FILESETS> — the paths to track 🫶

---

👑 GLOBAL OPTIONS 👑

these ones work across the board, bestie — they're the main character energy of jj 🔥

• -R, --repository <REPOSITORY> — path to the 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 my people, don't worry" 💜
• --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, and the working copy is also updated at the end of the command if the command modified the working-copy commit (@). So if you want to avoid snapshotting and instead see a possibly stale working-copy commit, use --ignore-working-copy. This is lowkey useful in, like, a command prompt — especially if you've got another process committing the working copy. 🙈

Also, loading the repository at a specific operation with --at-operation implies --ignore-working-copy. no cap. ✨

• --no-integrate-operation — run the command as usual but don't integrate any operations. So the operations still get created like normal, but they do NOT get integrated into the operation log. The working copy also doesn't get updated. 🫶

The command will print the resulting operation ID. You can pass that to, like, 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. the push is still pushing. 💀

• --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. just the check. that's it. that's the tweet. 💜

• --at-operation <AT_OPERATION> — the 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 there are 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. And --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. ⭐

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 while 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. she said "you can, not that you should" 💀

• --debug — enable debug logging 🐛
• --color <WHEN> — when to colorize output. possible values:
  • always
  • never
  • debug
  • auto
• --quiet — silence non-primary command output. Like, 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 tho. 🎀
• --no-pager — disable the pager 🚫
• --config <NAME=VALUE> — additional configuration options (and yeah, it can be repeated 💅). The name should be specified as TOML dotted keys. The value should be specified as a TOML expression. If a string value isn't enclosed by any TOML constructs (like array notation), the quotes can be omitted. 🫶
• --config-file <PATH> — additional configuration files (also repeatable, slay ✨)

---

🧚 quick vibe check recap 🌸

• no args = track everything not ignored
• new files are auto-tracked by default so this command is usually doing nothing
• snapshot.auto-track controls the auto-tracking pattern, default all()
• --include-ignored = overrides the ignore and file-size restrictions

---

and that's the whole page bestie, you ate it, no crumbs left 🍓 stay iconic, stay tracked 💖

this was jj-file-track from the General Commands Manual — the track manual page <rainbow>jj-file-track(1)</rainbow> 🫶✨ periodt. 💅