jj-git-remote(1)

💖 jj-git-remote(1) — like, the manual page, but make it make sense 💖

okay bestie, gather round, we're learning jj-git-remote from General Commands Manual and honestly? it's giving main character energy for your remotes. no cap. 🦋

---

✨ NAME ✨

jj-git-remote — manage Git remotes. that's it. that's the whole job. 💅

---

✨ SYNOPSIS ✨

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

look at all those flags. she's got range. 🎀

---

✨ DESCRIPTION ✨

Manage Git remotes. yes queen, manage them. 👑

and here's the lil secret nobody tells you: the Git repo will be a bare git repo stored inside the .jj/ directory. yeah. it lives in there. tucked away. iconic.

---

✨ OPTIONS ✨

• -h, --help — prints the help (or, if you do a lil -h, a summary — cute and short ✨)

---

🌈 GLOBAL OPTIONS 🌈

these ones work basically everywhere, so learn them once and you're set fr fr.

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

by default? Jujutsu just goes hunting for the closest .jj/ directory in an ancestor of wherever you're currently standing. like a lil bloodhound. 🐾

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

so like, normally Jujutsu snapshots the working copy at the beginning of every command. and then at the end of the command it updates the working copy too, but only if the command modified the working-copy commit (@). if you'd rather not snapshot the working copy and instead look at a possibly stale working-copy commit, this is your girl. this may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.

also important: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. the way that's automatic. 💀

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

when you give this option, 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. yes really. it still pushes. bestie. 😭

• --ignore-immutable — allow rewriting immutable commits. bold of you. 🔥

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> — 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 any. (yes, merging divergents. she contains multitudes. 🌸)

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. go off i guess. 🙈

• --debug — enable debug logging. for when you need to see everything. 🐛
• --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. it's giving minimalism.

warnings and errors will still be printed. she's quiet, not silent. 💜

• --no-pager — disable the pager. no scrolling, no drama. ⭐
• --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. so chill of her. ✨

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

---

🦋 SUBCOMMANDS 🦋

pick your fighter:

• jj-git-remote-add(1) — add a Git remote.
• jj-git-remote-list(1) — list Git remotes.
• jj-git-remote-remove(1) — remove a Git remote and forget its bookmarks.
• jj-git-remote-rename(1) — rename a Git remote.
• jj-git-remote-set-url(1) — set the URL of a Git remote.

---

aaaand that's the whole page, bestie. no notes. 💖

this one lives under the source remote for jj-git-remote(1) — that's the version/date corner of the page. k bye, go manage some remotes, you absolute icon. 👑✨