jj-git-remote-list(1)

💖 NAME 💖

jj-git-remote-list — bestie, it literally just lists your Git remotes 🌸

---

✨ SYNOPSIS ✨

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

---

🎀 DESCRIPTION 🎀

List Git remotes. That's the whole vibe, no notes, she just shows you the remotes 💅

---

🌸 OPTIONS 🌸

• -h, --help — prints the help, and if you want the short-and-sweet version instead of the whole essay, hit -h 👑

---

🦋 GLOBAL OPTIONS 🦋

These ones are the everywhere-options, the ones that follow you to every command like a loyal group chat 🫶

• -R, --repository <REPOSITORY> — which repo you wanna operate on. By default Jujutsu goes hunting for the closest .jj/ directory in an ancestor of wherever you're standing right now (your current working directory) 🔍
• --ignore-working-copy — don't snapshot the working copy, and don't update it. Okay so normally Jujutsu snapshots the working copy at the beginning of every single command, no cap. And the working copy also gets updated at the end of the command, but only if the command modified the working-copy commit (that's @, the main character). If you'd rather not snapshot and instead peek at a possibly stale working-copy commit, this is your flag. It's lowkey iconic for stuff like a command prompt — especially if you've got another process committing the working copy behind your back 😭

Loading the repository at a specific operation with --at-operation implies --ignore-working-copy, periodt.

• --no-integrate-operation — run the command as usual but don't integrate any operations. When you pass this, the operations still get created as usual, but they do not get integrated into the operation log. The working copy also doesn't get updated, fr fr.

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… be aware, bestie 💀

• --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. Ngl that's a lot of power 🙈

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. 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. (Chaotic energy, honestly 🌀)

• --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. Warnings and errors will still be printed though — you can't escape those 💅
• --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 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) 📂

---

okay that's the whole page bestie, you ate that 🫶 stay hydrated, go list some remotes, mwah 💖

this lil' cutie lives under the name list inside the jj-git-remote-list(1) manual — iconic behavior, no notes 👑