jj-bookmark-track(1)

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

okay bestie, gather round, because jj bookmark track is about to become your new fave. this is from the General Commands Manual, and it's literally the command for starting to track remote bookmarks. periodt.

---

✨ NAME ✨

jj-bookmark-track — start tracking given remote bookmarks 🦋

---

✨ SYNOPSIS ✨

jj bookmark track [-R|--repository] [--remote] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <BOOKMARK[@REMOTE]>

---

✨ DESCRIPTION ✨

Start tracking given remote bookmarks. that's it, that's the vibe 💅

so here's the tea: a tracked remote bookmark gets imported as a local bookmark with the same name. and then any changes to it propagate to the existing local bookmark on future pulls. so like, you track it once and it just keeps up with you. iconic behaviour honestly 🌸

---

✨ OPTIONS ✨

• --remote <REMOTE> — remote names to track 🌈

by default, the pattern you give matches remote names with glob syntax. and yes bestie, you can also use other [string pattern syntax] if glob isn't your moment.

if you give no remote names at all, then all remote bookmarks matching the bookmark names will be tracked. easy.

[string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

• -h, --help — print help 👑 (and if you want the short version, that's what '-h' gives you — see a summary with '-h')
• <BOOKMARK[@REMOTE]> — bookmark name patterns or remote bookmark symbols to track 🎀

BOOKMARK matches bookmark names using glob syntax by default. you can also use other [string pattern syntax], go off.

BOOKMARK@REMOTE resolves to a remote bookmark exactly. no globbing, no games, just that one. 💯

[string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

---

✨ GLOBAL OPTIONS ✨

these ones apply everywhere, so they're like the group chat rules of jj 📱

• -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 just finds it for you, like a good friend.

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

heads up: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. so that one comes along for the ride whether you asked or not 💀

• --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 doors open, honestly.

note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. scary but true 😭

• --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. main character energy, but for commits.

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 for the whole thing, we're not monsters.

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 💀

• --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. so, quiet but not that quiet.

• --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 a 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) 📁

---

and that's the whole thing, bestie! you ate that. no cap, tracking remote bookmarks is lowkey one of the most satisfying jj rituals once it clicks 🦋✨

this page is track, from jj-bookmark-track(1). mwah, sending you off with a 💋 and a reminder to read your manual pages.