jj-util-in...l-man-pages(1)

💖 jj-util-install-man-pages — the manpage-installing era 💖

okay bestie, so this is part of the General Commands Manual situation, and it's literally the jj-util-install-man-pages page. It does one thing and it does it iconically: it installs Jujutsu's manpages to the path you give it. no cap. 🎀

✨ NAME ✨

jj-util-install-man-pages — Install Jujutsu's manpages to the provided path 🫶

🌸 SYNOPSIS 🌸

jj util install-man-pages [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <PATH>

🦋 DESCRIPTION 🦋

Install Jujutsu's manpages to the provided path. that's it, that's the whole gig, and honestly? she ate. 💅

---

💜 OPTIONS 💜

• -h, --help — Print help (see a summary with -h). the tiny version, lowkey snack-sized 🍓
• <PATH> — The path where manpages will installed. An example path might be /usr/share/man. The provided path will be appended with man1, etc., as appropriate. so like, she's not dumping everything straight into your folder, she's building out the little man1 subfolders and stuff as needed. structured. organized. main character energy. 👑

🌈 GLOBAL OPTIONS 🌈

these ones travel with basically every jj command, and they are not optional reading, okay? they're the whole vibe check of the CLI. 💖

• -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 out here sniffing around your folders like a little bloodhound. 🔥

• --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, they're linked, it comes free with the other one. 🙈

• --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. ⚠️ like it says — the push still happens fr fr, this is not a "stop everything" button.

• --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 don't go thinking it changes those, it's just the bouncer stepping aside. 💀

• --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. so like... you can, it's just giving chaos gremlin. 🧚

• --debug — Enable debug logging. get all up in the logs, bestie. 🔍
• --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. she's quiet, not silent. important distinction. 💅

• --no-pager — Disable the pager. no scrolling situation, the output just comes straight at you. 📄
• --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. yes you can stack these, repeat away, she's not judging. 🎀

• --config-file <PATH> — Additional configuration files (can be repeated). also stackable, also iconic. ✨

---

and that's the whole page, bestie!! 🫶 go install those manpages, you absolute legend. 💖

mwah 💋 — this was install-man-pages from the jj-util-in...l-man-pages(1) set, served fresh from the Jujutsu docs. no date on the tin, just vibes and version tags. byeeee!! 👑🌈