jj-abandon(1)

💅 jj-abandon — abandon a revision (yes bestie, we're letting it GO)

okay so this is jj-abandon(1), section 1 of the manual, and it's giving "cut it loose" energy. Let's get into it 🎀

---

✨ NAME ✨

jj-abandon — abandon a revision. that's it. that's the whole vibe. bye boo 👋

---

🌸 SYNOPSIS 🌸

jj abandon [-R|--repository] [--ignore-working-copy]
[--retain-bookmarks] [--no-integrate-operation] [--restore-descendants]
[--ignore-immutable] [--at-operation] [--debug] [--color] [--quiet]
[--no-pager] [--config] [--config-file] [-h|--help] [REVSETS]

---

🦋 DESCRIPTION 🦋

Abandon a revision.

So like, when you abandon a revision, all its descendants get rebased onto its parent(s). The behavior is basically jj restore --changes-in coded but make it a glow-up — the difference is that jj abandon hands you a new change, while jj restore just updates the change you already have. two different girls, two different paths 💫

And if a working-copy commit gets abandoned? it gets given a brand new, empty commit. this is true in general, not just a this-command thing. it's a lifestyle. ✨

---

👑 OPTIONS 👑

• --retain-bookmarks — Do not delete bookmarks pointing to the revisions to abandon

...instead, those bookmarks will be moved to the parent revisions. relocation era 🫶

• --restore-descendants — Do not modify the content of the children of the abandoned commits

like, leave the kids' stuff alone.

• -h, --help — Print help (see a summary with -h)
• [REVSETS] — The revision(s) to abandon (default: @) [aliases: -r]

if you don't say who, it's @. the main character. obviously. 💅

---

🌈 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 goes looking for its home base 🏠

• --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. so it comes free, no cap 💀

• --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. bestie it WILL push. it does not care. 😭

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

• --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. the parallel universes will NOT be reconciled, periodt.

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. (iconic chaos 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.

Warnings and errors will still be printed. those two never shut up, and honestly? they shouldn't. 💜

• --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 — abandon, page jj-abandon(1), waving at you from the bottom of the manpage like the footer it is. stay abandoned-able, mwah 💖🎀🦋