jj-bookmark-set(1)

💖 jj-bookmark-set(1) 💖

okay bestie, gather round, because this is the manual page for jj-bookmark-set — aka the little glow-up command that makes new bookmarks or refreshes the ones you already have by name. it lives in the General Commands Manual section, and yes, it's giving main character energy. ✨

---

🌸 NAME 🌸

jj-bookmark-set — Create a new bookmark, or update an existing one by name

no cap, that's the whole vibe.

---

🎀 SYNOPSIS 🎀

jj bookmark set [-r|--revision] [-R|--repository] [-B|--allow-backwards]
[--ignore-working-copy] [--no-integrate-operation] [--ignore-immutable]
[--at-operation] [--debug] [--color] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help] <NAMES>

look at all those flags, she's ✨flexible✨

---

🦋 DESCRIPTION 🦋

Create a new bookmark, or update an existing one by name

and listen — if you're trying to move bookmarks based on where they currently are instead of by their names, that's a whole different serve: use jj bookmark move --from <REVSETS>. iykyk 💅

---

✨ OPTIONS ✨

• -r, --revision <REVSET> — the revision the bookmark should point at. default is @, aka wherever you're standing right now. 🫶
• -B, --allow-backwards — lets the bookmark move backwards or sideways. without this? it's not gonna do that, bestie.
• -h, --help — prints the help. and psst: add -h for the short summary version. 🙈
• <NAMES> — the bookmarks you want to update. that's the actual argument, plural, one or many, your call. 👑

---

🌈 GLOBAL OPTIONS 🌈

these are the big-picture, works-everywhere kinda options. lowkey iconic.

• -R, --repository <REPOSITORY> — the path to the repository you wanna operate on.

by default, Jujutsu goes searching for the closest .jj/ directory in an ancestor of the current working directory. it's literally just looking upward like 👀

• --ignore-working-copy — don't snapshot the working copy, and don't update it.

so here's the tea: by default, Jujutsu snapshots the working copy at the beginning of every command. the working copy also gets updated at the end of the command, if the command modified the working-copy commit (@). if you wanna avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use --ignore-working-copy. this is handy e.g. in a command prompt, especially if you've got another process committing the working copy.

also important: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. sneaky but true.

• --no-integrate-operation — run the command as usual but don't integrate any operations.

when you pass this, the operations still get created like normal, but they don't get integrated into the operation log. and the working copy also won't 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.

⚠️ and like, be careful — this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. fr fr.

• --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. so dramatic of you.

this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. periodt.

• --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. messy but valid.

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, 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 mode unlocked, use wisely.

• --debug — enable debug logging. for when you need to see everything. 🔍
• --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 the "less yapping please" flag. 🤫

warnings and errors will still be printed, obviously. safety first.

• --no-pager — disable the pager. no scrolling, just vibes. 📜
• --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. fancy but flexible ✨

• --config-file <PATH> — additional configuration files (can be repeated). stack 'em up. 🎀

---

and that's the whole page, bestie!! you made it to the end and honestly? slay.

this gorgeous little page came out of the set source, and it's filed under jj-bookmark-set(1) in the General Commands Manual. go forth and bookmark responsibly. 💖🦋🎀