jj-tag-delete(1)

💖 jj-tag-delete 💖

okay so bestie, welcome to the jj-tag-delete manual page — that's a General Commands Manual situation, section 1, and it's giving "we're about to yeet some tags". pull up a chair, we're doing this together. 🎀

---

✨ NAME ✨

jj-tag-delete — delete existing tags. bye babes 💅

---

🦋 SYNOPSIS 🦋

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

---

🌸 DESCRIPTION 🌸

Delete existing tags. that's the whole job, no notes. 🗑️

but wait, important lore: Revisions referred to by the deleted tags are not abandoned. so like, the tags get deleted but the commits they were pointing at are still thriving, they're fine, they're still in the repo. no casualties. 🫶

---

👑 OPTIONS 👑

• -h, --help — print help! (see a summary if you just do -h, the long version is the full read) 💖
• <NAMES> — the tag names you wanna delete, boo.

By default, the specified pattern matches tag names with glob syntax. You can also use other [string pattern syntax]. 🌈

[string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

---

🧚 GLOBAL OPTIONS 🧚

these ones are the everywhere-flags, the ones that follow you to every command. iconic behavior honestly.

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

By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. so it just goes climbing up the folder tree like a lil detective. 🔍

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

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. 💀

heads up: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. it's automatic, you don't gotta do anything. ✨

• --no-integrate-operation — run the command as usual but don't integrate any operations. the operation says "I'm not like other 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. so many doors opened by one lil ID, obsessed. 🎀

note: this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. the push is happening bestie, that one's out of scope. 😭

• --ignore-immutable — allow rewriting immutable commits. rebel mode unlocked. 🔥

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.

This option only affects the check. It does not affect the immutable_heads() revset or the immutable template keyword. those stay exactly as they are, periodt.

• --at-operation <AT_OPERATION> — operation to load the repo at. time travel but make it version control. ⏳

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. (prefix girlies, you're valid ✨)

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. not me telling you it's possible but also gently suggesting you probably shouldn't 💀

• --debug — enable debug logging. for when you need to see everything all at once. 🔍
• --color <WHEN> — when to colorize output. the aesthetic settings, we love to see it. 🌈

Possible values:

• always
• never
• debug
• auto

• --quiet — silence non-primary command output. shhh, only the main character speaks. 🤫

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 never get quiet, they're too important. 👑

• --no-pager — disable the pager. straight to the terminal, no scrolling middleman. 💅
• --config <NAME=VALUE> — additional configuration options (can be repeated). stack 'em up. 🍓

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.

• --config-file <PATH> — additional configuration files (can be repeated). yes bestie, another one, bring all your config files to the party. 🎀

---

that's the whole page fr fr — every flag, every default, every warning, all of it, no skips. 🫶

💌 cute sign-off time: this was jj-tag-delete(1), filed under delete, and if you ever forget any of it, the jj-tag-delete(1) manual will be right there waiting for you like a loyal bestie. mwah. 💖✨