jj-bookmark-rename(1)

💖 jj-bookmark-rename — the glow-up your bookmark deserves 💖

okay bestie, this is jj-bookmark-rename(1) from the General Commands Manual, and it's literally just "give your bookmark a new name" energy. no cap.

---

✨ NAME ✨

jj-bookmark-rename — Rename old bookmark name to new bookmark name

---

🎀 SYNOPSIS 🎀

jj bookmark rename [--overwrite-existing] [-R|--repository]
[--ignore-working-copy] [--no-integrate-operation] [--ignore-immutable]
[--at-operation] [--debug] [--color] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help] <OLD> <NEW>

---

🌸 DESCRIPTION 🌸

Rename old bookmark name to new bookmark name. that's it, that's the whole job. 💅

and here's the part that actually matters, bestie: the new bookmark name points at the same commit as the old bookmark name. same commit, new name, no move, no rebase, no drama. it's giving "changed my name, kept my whole personality." 🦋

---

👑 OPTIONS 👑

• --overwrite-existing — lets you do the rename even if the new bookmark name already exists. normally that'd be a collision, but with this flag you're allowed to just... take over. slay, i guess. 💀
• -h, --help — prints the help. and note: with just -h you get a summary, not the whole thing. iykyk.
• <OLD> — the old name of the bookmark (the one you're retiring 🥲)
• <NEW> — the new name of the bookmark (the glow-up name ✨)

---

🌈 GLOBAL OPTIONS 🌈

these ones are the shared, repo-wide, everybody-gets-them options. they apply across commands, so come get your plate. 🍓

• -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 like, it'll walk up the tree looking for home. 🫶

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

default behavior check: Jujutsu snapshots the working copy at the beginning of every command, and the working copy also gets updated at the end of the command if the command modified the working-copy commit (@). if you want to skip the snapshotting and instead see a possibly stale working-copy commit, this is your flag. lowkey useful 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. periodt.

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

when this one's on, the operations still get created like normal, but they will not be integrated into the operation log. 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 hand 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. no takebacks, bestie. 💀

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

heads up though — this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. it's just the bouncer, not the guest list. 🧚

• --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 to type the whole thing. 👑

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

and yes — 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. main character chaos energy, honestly. 🔥

• --debug — Enable debug logging. 🐛 (not a bug, it's a feature — it's about the bugs)
• --color <WHEN> — When to colorize output.

Possible values:

1. always
2. never
3. debug
4. 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. silent but still serving. 💅

Warnings and errors will still be printed, obviously. we're quiet, not reckless.

• --no-pager — Disable the pager. no more less jumpscare. 😭
• --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). stack 'em up. 🌸

---

🫶 a little sign-off 🫶

this was jj-bookmark-rename(1) — the rename page out of the Jujutsu manual set, sitting pretty in the General Commands Manual section. go forth, rename responsibly, and remember: same commit, new name, always. bye bestie, mwah 💖✨🎀