jj-absorb(1)

💖 jj-absorb 💖

okay so bestie, buckle up, this is jj-absorb(1) from the jj girlies, and it is genuinely one of the cutest little commands in the whole suite. it moves your changes around like a librarian reshelving books but make it ✨magic✨. let's get into it.

---

✨ NAME ✨

jj-absorb — move changes from a revision into the stack of mutable revisions 🫶

---

🌸 SYNOPSIS 🌸

jj absorb [-f|--from] [-R|--repository] [--ignore-working-copy]
[-t|--into] [-i|--interactive] [--no-integrate-operation]
[--ignore-immutable] [--tool] [--at-operation] [--debug] [--color]
[--quiet] [--no-pager] [--config] [--config-file] [-h|--help] [FILESETS]

---

💅 DESCRIPTION 💅

Move changes from a revision into the stack of mutable revisions. slay.

Here's the tea: this command splits the changes in the source revision, and then it moves each individual change to the closest mutable ancestor where the corresponding lines were modified last. it's like the changes are finding their way home to the commit that actually owns those lines 🏠✨ If the destination revision can't be figured out unambiguously? the change just stays put in the source revision. no drama, no guessing, lowkey respectful of boundaries.

With the --interactive option, only the changes you selected get considered for absorption. that means you can pick specific hunks to absorb (and those hunks might then get distributed across multiple ancestors, iconic behaviour honestly). You can also use the --tool option to select a different diff editor if the default one isn't giving what it needs to give.

The source revision gets abandoned if all the changes are absorbed into the destination revisions, and if the source revision has no description. like, if it's empty and undescribed? it's gone. gone girl. 💀

And bestie, you can always review the modification that jj absorb made by running jj op show -p. always check your work, it's giving responsible queen 👑

---

🎀 OPTIONS 🎀

• -f, --from <REVSET> — source revision to absorb from. default is @ 💖
• -t, --into <REVSETS> — destination revisions to absorb into. default is mutable().

Only ancestors of the source revision will be considered. so like, you can't absorb into something that comes after the source, that's not how this works, bestie 🙈

• -i, --interactive — interactively choose which parts to absorb. you're the main character, you decide. 👑
• --tool <NAME> — specify diff editor to be used. heads up: this implies --interactive, so you're getting the interactive treatment whether you were ready or not ✨
• -h, --help — print help (see a summary with -h). short version for the girlies on the go.
• [FILESETS] — move only changes to these paths (instead of all paths). like a filter but for files 🍓

---

🌈 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 like it's sniffing around for home 🐾

• --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 extra charge 💅

• --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. so like, the push is still pushing 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. the root commit said "not me" and honestly same.

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.

Use jj op log to find the operation ID you want. Any unambiguous prefix of the operation ID is enough. short king behaviour, we love a prefix.

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. like, you can, it's just kinda unhinged 🫠

• --debug — enable debug logging. for when you need to see everything bestie 🔍
• --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 "just the facts ma'am" ✨

Warnings and errors will still be printed though. important stuff never gets muted 💖

• --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 string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. yep it's TOML, she's fancy 🎀

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

---

ok that's the whole page, no cap, every flag present and accounted for 💯

and for the cute sign-off: this lil masterpiece comes out of the absorb source, living under the name jj-absorb(1) in your friendly neighbourhood General Commands Manual 💜 go absorb something, bestie, and remember to jj op show -p afterwards because we always check the receipts 👑✨🦋