jj-bookmark-untrack(1)

✨ jj-bookmark-untrack(1) ✨

okay bestie so this one lives in the General Commands Manual, it's called jj-bookmark-untrack, and it's giving "let me stop tracking these remote bookmarks, respectfully" 💅 let's get into it

---

🌸 NAME 🌸

jj-bookmark-untrack — stop tracking given remote bookmarks 💖

---

🦋 SYNOPSIS 🦋

jj bookmark untrack [-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 💜

Stop tracking given remote bookmarks. that's the whole job, no cap ✨

so like. an untracked remote bookmark is just a pointer to the last-fetched remote bookmark. that's all it is. it won't get imported as a local bookmark on future pulls — lowkey it just sits there being a memory 🫶

if you wanna forget a local bookmark while ALSO untracking the corresponding remote bookmarks, use jj bookmark forget instead. forget is the one with main character energy for that situation, fr fr 🌈

---

🎀 OPTIONS 🎀

• --remote <REMOTE> — remote names to untrack 👑

by default, the specified pattern matches remote names with glob syntax. you can also use other [string pattern syntax].

if no remote names are given, all remote bookmarks matching the bookmark names will be untracked. (yeah, all of them. periodt.)

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

• -h, --help — print help (see a summary with '-h') 🙈
• <BOOKMARK[@REMOTE]> — bookmark name patterns or remote bookmark symbols to untrack 💖

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

BOOKMARK@REMOTE resolves to a remote bookmark exactly. no guessing, it's that one, slay ✨

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

---

👑 GLOBAL OPTIONS 👑

these are the big-girl options that apply everywhere, not just here 🌟

• -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 hunts it down. iconic behavior.

• --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 (👀 ancient), 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.

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

heads up bestie: note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. 😭 it really will.

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

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

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. 🧚 just so you know.

• --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. (they always find a way 💀)

• --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) 🔁

---

and that's the whole page, bestie, you ate that 🫶✨ this little untrack section of the manual is signed off as untrack over in jj-bookmark-untrack(1) — so like, that's the footer vibe, that's the source/version-and-date moment, and honestly? iconic. go untrack something 💖