jj-bookmark-advance(1)

📦 version 0.46.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

💖 jj-bookmark-advance(1) 💖

okay bestie, welcome to the jj bookmark advance manual page — General Commands Manual vibes, main character energy, bookmark-glow-up edition ✨

🌸 NAME 🌸

jj-bookmark-advance — advance the closest bookmarks to a target revision 🫶

✨ SYNOPSIS ✨

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

💅 DESCRIPTION 💅

Advance the closest bookmarks to a target revision ✨

The target --to defaults to revsets.bookmark-advance-to (which defaults to @). like, out of the box it just goes to @, the working-copy commit, iconic behaviour honestly.

The bookmarks to advance are determined by revsets.bookmark-advance-from (which defaults to heads(::to & bookmarks())). 👑

🎀 heads up: the from revset has access to to. yes ma'am, it can literally see it.

Positional bookmark name arguments can target specific bookmarks to advance to the target — and in this case the default from revset is ignored. so like, you take the wheel, bestie 🚗💨

Example:

jj bookmark advance --to x - Does the equivalent of jj bookmark move --from 'heads(::x & bookmarks())' --to x.

🔥 OPTIONS 🔥

  • -t, --to <REVSET> — move bookmarks to this revision 💖 Defaults to revsets.bookmark-advance-to.
  • -h, --help — print help (see a summary with '-h') 📖
  • [NAMES] — move bookmarks matching the given name patterns 🌸 By default, the specified pattern matches bookmark names with glob syntax. You can also use other [string pattern syntax]. The [string pattern syntax] link lives at: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

🌈 GLOBAL OPTIONS 🌈

  • -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 giving "it'll find your repo for you, don't stress".
  • --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.

😭 Loading the repository at a specific operation with --at-operation implies --ignore-working-copy. it just comes with it, no notes.
  • --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.

⚠️ note that this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. fr fr, the push still happens.
  • --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.

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.

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. slay, abbreviations are valid 💅

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. okay but why would you 🔥 it's possible though!

  • --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. those are not getting silenced, bestie.

  • --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) 🗂️

anyway that's the whole thing, you're SO ready 🦋💖 this was advance — jj-bookmark-advance(1) — go advance some bookmarks and be the icon you are, mwah 👑✨

📦 where this page comes from