jj-tag(1)

💖 jj-tag(1) 💖

okay bestie, welcome to the General Commands Manual era, this is jj-tag and she is HERE to manage your tags 💅

---

✨ NAME ✨

jj-tag — manage tags 🏷️

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

Manage tags. that's it, that's the whole vibe 🎀

---

💅 OPTIONS 💅

• -h, --help — prints the help. and if you want the short version, hit -h and she'll give you a lil summary instead of the whole essay 🫶

---

👑 GLOBAL OPTIONS 👑

these ones are universal, they work everywhere, main character energy fr fr 🌈

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

by default, Jujutsu goes hunting for the closest .jj/ directory in an ancestor of wherever you're currently standing (your cwd). so like, it'll find it for you, no stress 💖

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

so normally, Jujutsu snapshots the working copy at the start of every single command. and then at the end of the command, it updates it too — but only if the command actually modified the working-copy commit (@). if you wanna skip the snapshotting and just look at a possibly stale working-copy commit instead, this is your flag. lowkey useful in a command prompt, especially if you've got another process committing the working copy behind your back 😭

heads up: loading the repo at a specific operation with --at-operation implies --ignore-working-copy. it's automatic bestie ✨

• --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 — they just don't get integrated into the operation log. the working copy also doesn't get updated.

the command will print out the resulting operation ID. you can feed that to like jj --at-op to peek at the resulting repo state, or hand 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.

⚠️ important: this does not stop side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. no cap, the push is happening 🔥

• --ignore-immutable — allow rewriting immutable commits, we're breaking the rules today 😈

by default, Jujutsu prevents rewriting commits in the configured set of immutable commits. this option disables that check and lets you rewrite any commit except the root commit.

note: this option only affects the check itself. it does not affect the immutable_heads() revset or the immutable template keyword. those stay exactly as they are 💅

• --at-operation <AT_OPERATION> — the 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 get merged.

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough, don't stress about typing the whole thing ✨

when you're loading the repo at an earlier operation, the working copy gets 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 behavior, honestly 🌀

• --debug — enable debug logging 🐛
• --color <WHEN> — when to colorize the 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 are not getting silenced, periodt 📢

• --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), the quotes can be omitted.

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

---

🎀 SUBCOMMANDS 🎀

the whole squad, here they are 🫶

• jj-tag-delete(1) — delete existing tags 🗑️
• jj-tag-list(1) — list tags and their targets 📋
• jj-tag-set(1) — create or update tags ✏️
• jj-tag-track(1) — start tracking given remote tags 👀
• jj-tag-untrack(1) — stop tracking given remote tags 🚫

---

and that's the page bestie!! source is tag, version/footer situation is jj-tag(1) — she's iconic, she's giving manual page, and she ate 💖✨ no notes. go forth and manage those tags 👑🌸