jj-gerrit(1)

💖 jj-gerrit(1) — the manual page but make it a group chat 💖

okay bestie, so this is jj-gerrit, a.k.a. the jj subcommand that lets you vibe with Gerrit Code Review. yes, the manual name is literally jj-gerrit(1). iconic. let's get into it 🫶

---

✨ NAME ✨

jj-gerrit — Interact with Gerrit Code Review

no like. that's the whole name section. it's giving minimalism 💅

---

🌸 SYNOPSIS 🌸

jj gerrit [-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. it's a whole wardrobe 👑

---

🦋 DESCRIPTION 🦋

Interact with Gerrit Code Review

(that's it. that's the description. short queen energy. the subcommands do the heavy lifting, iykyk)

---

⭐ OPTIONS ⭐

• -h, --help — Print help (see a summary with -h). note that: the full help is the default, and -h gives you the lil summary version. two flavors of knowing things 💜

---

💅 GLOBAL OPTIONS 💅

• -R, --repository <REPOSITORY> — Path to repository to operate on.

By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. so it's like, walking up the family tree looking for the .jj/ folder 🧚

• --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. yes bestie, that one comes for free, 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.

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. the operation log doesn't get it, but the internet DOES. 💀

• --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. so, like, the vibe of immutability is intact, you're just sneaking past the bouncer 🙈

• --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. yes you can just type the first few characters, she's flexible like that ✨

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. (the manual is being so real for admitting that 🫶)

• --debug — Enable debug logging. for when you gotta see everything 👀
• --color <WHEN> — When to colorize output.

Possible values:

• always
• never
• debug
• auto

pick your aesthetic 🌈

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

• --no-pager — Disable the pager. straight to the terminal, no scroll queen behavior 💅
• --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. so like, you can be lazy with the quotes and it'll still get it 🎀

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

---

👑 SUBCOMMANDS 👑

• jj-gerrit-upload(1) — Upload changes to Gerrit for code review, or update existing changes. (there's a whole other manual page for this, go read it, it's the main character of the gerrit saga 🔥)

---

that's the whole vibe check, bestie. go forth and review some code. periodt. 💖

this page came from the gerrit source and it's the jj-gerrit(1) manual — mwah, sending you the biggest rebase-free smooch, bye!! 🎀✨🦋💜