jj-config-get(1)

💖 NAME 💖

jj-config-get — bestie, this is the command that grabs you the value of a given config option. that's literally its whole thing. slay.

---

🦋 SYNOPSIS 🦋

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

---

🌸 DESCRIPTION 🌸

okay so, jj config get gets you the value of a given config option. that's it, that's the assignment, no notes. 💅

here's the part that's genuinely iconic though: unlike jj config list, the result of jj config get comes out without any extra formatting, which means it's actually usable in scripts. it's giving clean output, main character energy, no crumbs. for example:

$ jj config list user.name
user.name="Martin von Zweigbergk"
$ jj config get user.name
Martin von Zweigbergk

see how list wrapped it in quotes and the key name and all that, and get just handed you the raw value? yeah. that's the difference. iykyk. ✨

---

🎀 OPTIONS 🎀

• -h, --help — prints the help. (you get a summary if you use -h.)
• <NAME> — the name of the config option you're asking about, bestie. it's the one argument you're passing in.

---

👑 GLOBAL OPTIONS 👑

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

by default, Jujutsu goes hunting for the closest .jj/ directory in an ancestor of your current working directory. it's like a little scavenger hunt but for repos. 🦋

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

by default, Jujutsu snapshots the working copy at the beginning of every command. the working copy also gets 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 is highkey useful e.g. in a command prompt, especially if you've got another process committing the working copy.

heads up: 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 you pass this, the operations still get created like normal, but they will not be integrated into the operation log. the working copy also won't 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 bestie, the push still happens. 💀

• --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. no need to type the whole thing, queen. 👑

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. (chaos is an option, apparently. 🙈)

• --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, don't worry. 🫶

• --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 a string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. fancy, but make it convenient. 💅

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

---

and that's the whole page, bestie! this was jj-config-get(1) from the General Commands Manual, and the page/section tag down at the bottom is just get next to jj-config-get(1). go forth and get those config values. periodt. 💖✨🎀🦋🌸