jj-git-remote-remove(1)

✨ NAME ✨

jj-git-remote-remove — the jj git subcommand that removes a Git remote and forgets its bookmarks 👋👑 (yes bestie, the bookmarks go too, it's giving "we don't talk about Bruno")

This page you're reading? It's the jj-git-remote-remove(1) manual page from the General Commands Manual. Pull up a chair 🪑💖

---

✨ SYNOPSIS ✨

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

---

✨ DESCRIPTION ✨

Okay so, literally the whole vibe of this one: remove a Git remote and forget its bookmarks. That's it, that's the girl 💅🌸

---

✨ OPTIONS ✨

• -h, --help — prints the help. Peep the summary with -h 🫶
• <REMOTE> — the remote's name. That's the placeholder you gotta swap for the actual name of the remote you're yeeting 🎀

---

✨ GLOBAL OPTIONS ✨

These ones apply across the board, not just here. Slay.

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

By default, Jujutsu hunts for the closest .jj/ directory in an ancestor of the current working directory. It's giving "I'll find it myself, dw".

• --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 also gets updated 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 see a possibly stale working-copy commit, use --ignore-working-copy. This is lowkey useful e.g. in a command prompt, especially if you've got another process that commits the working copy.

Also important: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. No cap.

• --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. Periodt.

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. The push is gonna push, fr fr 😭

• --ignore-immutable — allow rewriting immutable commits, i.e. breaking the rules on purpose 💀

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. Iconic but unhinged.

This option only affects the check. It does not affect the immutable_heads() revset or the immutable template keyword. Know the difference iykyk.

• --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. The way that --at-op=@ is just different enough? Obsessed.

Use jj op log to find the operation ID you want. Any unambiguous prefix of the operation ID is enough — no need to type the whole thing, queen 🌈

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. Chaos permitted, technically 🌪️

• --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. The main character output stays; the side commentary goes.

Warnings and errors will still be printed. You can't mute the important stuff 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 the 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) 📁

---

So yeah, that's the whole page. The footer down there is just remove on the left and jj-git-remote-remove(1) on the right — no date on this one, so that's literally all the source/version tea we got 🍓 And that's a wrap, go forth and remove those remotes responsibly 💜🦋