jj-unsign(1)

💅 jj-unsign — bestie, we're dropping a cryptographic signature 💅

okay so this is the manual for jj-unsign, which lives in the General Commands Manual as jj-unsign(1). And yes, before you ask, it's exactly what it sounds like: this is the command that removes a commit signature. slay. let's get into it ✨

---

✨ NAME ✨

jj-unsign — drop a cryptographic signature 🫶

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

Drop a cryptographic signature. that's it, that's the job, she's a one-trick icon 👑

Also, for the full lore, go check out the [commit signing] docs, iykyk:

[commit signing]: https://docs.jj-vcs.dev/latest/config/#commit-signing

---

💖 OPTIONS 💖

• -r, --revision <REVSETS> — which revision(s) we're unsigning, bestie 🎀
• -h, --help — print the help, obviously. (want the short & sweet version? use just -h) 💅

---

👑 GLOBAL OPTIONS 👑

these ones are the shared amenities, everyone gets them 🌈

• -R, --repository <REPOSITORY> — path to the repository to operate on.

by default, Jujutsu goes hunting for the closest .jj/ directory in an ancestor of your current working directory. it's giving "searching the whole family tree for your repo" 🔍

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

so by default, 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 (@). But if you want to skip the snapshotting and instead see a possibly stale working-copy commit, you can use --ignore-working-copy. this is lowkey useful, like in a command prompt, especially if you've got another process committing the working copy for you 🙈

and heads up: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. package deal, no cap.

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

when you pass this, the operations still get created as usual, but they won't 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 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. options, options, options ✨

note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. scary but true 🫣

• --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. root said "not me" 🚫

this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. stay in your lane, option 💅

• --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 there are 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 way that time travel just works here 🕰️

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. chaotic, but possible 😭

• --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. she's just not gossiping anymore 🤫

warnings and errors will still be printed though. safety first, 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 a string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. fancy ✨

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

---

aaaand that's the whole vibe check, babe. this page is unsign from the jj-unsign(1) General Commands Manual, so like, that's the source and the whole identity right there 💜 go unsign something slay, mwah 🎀💖