jj-bookmark-delete(1)

💅 jj-bookmark-delete — the manual page, bestie edition

okay so bestie, welcome to jj-bookmark-delete(1) from the General Commands Manual 🎀 yes it's a real manual page, yes it lives in section 1, and yes we're gonna read it together like it's a text from your fave 💖

---

✨ NAME ✨

jj-bookmark-delete — delete an existing bookmark and propagate the deletion to remotes on the next push 🗑️✨

---

🦋 SYNOPSIS 🦋

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

---

💖 DESCRIPTION 💖

Delete an existing bookmark and propagate the deletion to remotes on the next push. that's the whole vibe, no cap 🫶

okay but here's the part where you gotta pay attention, because the plot twist is real: revisions referred to by the deleted bookmarks are not abandoned. the bookmark goes, the commits stay. it's giving "i'm breaking up with the label, not the person" 😭

so if you want the revisions gone too, and not just the bookmarks, use jj abandon. for example:

jj abandon main..<bookmark>

that one abandons revisions belonging to the <bookmark> branch (relative to the main branch). periodt. 🔥

and one more thing — if you don't want the deletion of the local bookmark to propagate to any tracked remote bookmarks, use jj bookmark forget instead. different tool, different energy, pick wisely bestie 💅

---

⭐ OPTIONS ⭐

• -h, --help — print help (see a summary with -h) — yes it's a whole summary situation when you go short-form 📖
• <NAMES> — the bookmarks to delete 🗑️

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

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

---

👑 GLOBAL OPTIONS 👑 (these work everywhere, main character energy)

• -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 literally out here hunting for .jj/ like it's looking for its keys 🔍

• --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. so like, stale but unbothered 💅

loading the repository at a specific operation with --at-operation implies --ignore-working-copy. they're a package deal, iykyk.

• --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. so the ops exist, they're just not in the group chat 💀

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. the push is happening bestie, no takebacks 🔥

• --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. the root commit said "not me" 💀

this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. it's just vibes-override for the check, nothing deeper 🧚

• --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. it's time travel but make it version control 🕰️✨

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough. short and sweet ✂️

when loading the repo at an earlier operation, the working copy will be ignored, as if --ignore-working-copy had been specified. told you, package deal.

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. chaotic option, honestly 🔥

• --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. it's giving "i'm here but i'm not narrating" 💅

warnings and errors will still be printed. those ones are loud on purpose 📢

• --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. TOML girlies rise 🙌

• --config-file <PATH> — additional configuration files (can be repeated) 📁

---

and that's the whole page, bestie! this was delete from jj-bookmark-delete(1) — go forth and delete responsibly, and remember: bookmarks can go, but commits don't abandon themselves 🫶💖 bye ily ✨

---