jj-git-remote-rename(1)

📦 version 0.46.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

💖 jj-git-remote-rename, but make it make sense

okay so bestie, welcome to the manual page for jj-git-remote-rename(1) — she lives in the General Commands Manual and she is, genuinely, so much simpler than she looks. let's get into it 💅

🌸 NAME

jj-git-remote-rename — rename a Git remote. that's the whole job. that's the vibe. periodt. ✨

🎀 SYNOPSIS

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

🦋 DESCRIPTION

Rename a Git remote.

like. that's it. that's the description. she said what she said and honestly? iconic. 💅

✨ OPTIONS

  • -h, --help — prints the help, and if you want the summary version you can peek at '-h'. lowkey the fastest way to get your bearings 🫶
  • <OLD> — the name of an existing remote. it has to already exist fr fr, you can't rename a ghost.
  • <NEW> — the desired name for old. ie. what you want that remote to be called from now on 👑

👑 GLOBAL OPTIONS

these ones show up everywhere, not just here. main character options, honestly.

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

by default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. so like, she'll go looking up the family tree for you 🧚

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

loading the repository at a specific operation with --at-operation implies --ignore-working-copy.

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

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.

⚠️ note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. so like, don't think she's not gonna push. she's gonna push. 😭
  • --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.

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

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

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. (not me saying "you can, but why" 💀)

  • --debug — enable debug logging. for when you need the tea ☕
  • --color <WHEN> — when to colorize output.

possible values:

  1. always
  2. never
  3. debug
  4. 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. she's quiet, not silent 🤫

  • --no-pager — disable the pager. no scrolling arc for you today, just raw output 🌈
  • --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 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). stack 'em up 🍓
and that's the whole page bestie. no cap, no hidden sections, no secret lore. go rename that remote 💜

kisses from the General Commands Manual, where this page is filed under rename and answers to jj-git-remote-rename(1) — she ate and left no crumbs ✨👑💅

📦 where this page comes from