jj-edit(1)

πŸ“¦
version 0.46.0 Β· 2 versions
, in arch rolling, nixpkgs unstable

πŸ‘‘ jj-edit β€” like, the manual page, but make it make sense πŸ’…

okay so bestie, you found it: jj-edit(1), straight out of the General Commands Manual. this is the page for jj edit, and I'm gonna walk you through every single flag like we're texting at 2am. no cap, nothing gets skipped. 🫢


✨ NAME ✨

jj-edit β€” sets the specified revision as the working-copy revision. that's the whole vibe. that's what it does. πŸŽ€


🌸 SYNOPSIS 🌸

jj edit [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <REVSET|-r>

yes the line wrapping is like that. it's giving "the man page author ran out of room", but we respect it. πŸ’œ


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the whole entire point: it sets the specified revision as the working-copy revision. literally that's it. that's the function. ✨

⚠️ but bestie, listen β€” there's a note, and it is important: it is [generally recommended] to instead use jj new and jj squash. so like... this command exists, but the docs are politely side-eyeing it. πŸ™ˆ

and the reference link, because we don't gatekeep:

[generally recommended]:
https://docs.jj-vcs.dev/latest/FAQ#how-do-i-resume-working-on-an-existing-change

πŸ’… OPTIONS πŸ’…

  • -h, --help β€” print help. and yeah, it's the full help β€” if you want the summary, hit it with -h. cute, right? (see a summary with '-h') 😭
  • [REVSET] β€” the commit to edit. that's the main character argument right there. also has the alias -r. slay. 🌟

🌈 GLOBAL OPTIONS 🌈

these are the big ones, the ones that apply everywhere. buckle up, we're going through all of them, fr fr. πŸ”₯

  • -R, --repository <REPOSITORY> β€” path to the repository to operate on. πŸ—‚οΈ

by default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. so it just... walks up the tree until it finds .jj/. iconic behavior honestly. 🧚

  • --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 (@). but 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. lowkey sounds like a specific person's problem, but okay. πŸ™ˆ

and note: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. ✨

  • --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. very "here's the receipt, do what you want with it" energy. 🧾

⚠️ 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, don't think this is a safety bubble, bestie. it is not. 😭
  • --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.

and this is a narrow option, okay: this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. so don't go thinking it changes those too. 🎯

  • --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. time travel but make it version control. πŸ•°οΈ

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough. so you do not have to type the whole thing, you're welcome. πŸ’–

when loading the repo at an earlier operation, the working copy will be ignored, as if --ignore-working-copy had been specified. see? it all connects. πŸ¦‹

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. so like... it's legal, just chaotic. πŸ™ˆ

  • --debug β€” enable debug logging. that's it. that's the option. go off, little logger. πŸ›
  • --color <WHEN> β€” when to colorize output. 🎨

possible values:

  • always
  • never
  • debug
  • auto

pick your fighter. 🌈

  • --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. so like, the main event stays, the narration goes.

warnings and errors will still be printed. thank goodness, because we still need to know when things go sideways. ⚠️

  • --no-pager β€” disable the pager. no pager, no problem. πŸ“„
  • --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. TOML girlies rise. πŸ“

  • --config-file <PATH> β€” additional configuration files (can be repeated). πŸ“

repeatable, just like --config. bring a friend. bring several. πŸ’œ


πŸŽ€ and that's the whole page! every option, every default, every warning β€” all accounted for. nothing dropped, nothing invented. iykyk. 🫢

jj-edit(1) β€” General Commands Manual β€” page edit, dated jj-edit(1) β€” that's the footer energy, bestie, and we are not skipping it. periodt. πŸ‘‘

πŸ“¦ where this page comes from