jj-tag-set(1)

✨ NAME ✨

jj-tag-set — the lil glow-up command that creates or updates tags 💖 (yes literally, that's the whole job, and she does it flawlessly)

---

🌸 SYNOPSIS 🌸

jj tag set [-r|--revision] [-R|--repository] [--allow-move]
[--ignore-working-copy] [--no-integrate-operation] [--ignore-immutable]
[--at-operation] [--debug] [--color] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help] <NAMES>

---

🎀 DESCRIPTION 🎀

Create or update tags. That's it, that's the vibe. Bestie said "I need a tag" and this command said "say less" 💅

---

💅 OPTIONS 💅

• -r, --revision <REVSET> [default: @] — the target revision you want your tag to point at. default is @, no cap.
• --allow-move — lets you move tags that already exist. without it, moving is giving 🚫 energy.
• -h, --help — print help (or a summary version with just -h)
• <NAMES> — the tag names you wanna create or update 👑

---

🌈 GLOBAL OPTIONS 🌈

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

fr fr by default, Jujutsu hunts down the closest .jj/ directory in an ancestor of wherever your current working directory is. it's giving "I'll find it myself" 🕵️

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

okay so by default, Jujutsu snapshots the working copy at the beginning of every command. it also updates the working copy at the end of the command, if the command modified the working-copy commit (@). so if you wanna avoid snapshotting the working copy and instead look at a possibly stale working-copy commit, --ignore-working-copy is your girl. lowkey useful in a command prompt, especially if you've got another process committing the working copy 👀

also important: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. periodt.

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

when you pass this, the operations still get created like normal, but they won't be integrated into the operation log. the working copy also won't be updated. wild, I know.

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 🫶

heads up bestie: this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. no takebacks on that one 😭

• --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. main character energy only 💀

this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. stay informed, queen.

• --at-operation <AT_OPERATION> — the 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 ✨

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough, slay.

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. iykyk 🦋

• --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. peace and quiet, honestly iconic 🤫

warnings and errors will still be printed. safety first 💖

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

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

---

🧚 and that's the whole page, bestie! go forth and tag responsibly 💜

this has been jj-tag-set, from the set source, in the jj-tag-set(1) manual — mwah, kisses, see you in the next manpage 😘👑