jj-config-path(1)

💖 NAME 💖

jj-config-path — print the paths to the config files. Bestie, this is the jj-config-path(1) page from the General Commands Manual, and we are keeping every single flag, okay? No cap. 🫶

---

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

Okay so: print the paths to the config files. That's the whole main-character job. ✨

A config file at that path may or may not exist. Lowkey important: the path existing and the file existing are two different vibes.

If --repo or --workspace is specified and the config file does not exist, jj will generate a new config directory for this repo/workspace and print the path to the config file in that directory. So yes, it can manifest a directory for you. Slay. 💅

See jj config edit if you'd like to immediately edit a file. That's your "okay now I actually want to touch it" move.

---

💅 OPTIONS 💅

• --user — target the user-level config. Your personal config era. 🎀
• --repo — target the repo-level config. This repo's config, specifically. 💜
• --workspace — target the workspace-level config. Workspace config, right where it belongs. 🧚
• -h, --help — print help (see a summary with -h). The little -h gives you the short version, bestie.

---

🌈 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. It's giving "climb the tree until you find the repo." 🌳

• --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. So that's automatic, iykyk. 🌀

• --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. So yeah, the operation-log part is chillin' separately, but the push is still pushing. 😭

• --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 too, bestie. 🔥

• --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. Iconic little chaos option, honestly. 💀

• --debug — enable debug logging. For when you want the lore. 🔍
• --color <WHEN> — when to colorize output.

Possible values:

• always
• never
• debug
• auto

Pick your color vibe, bestie. 🌈

• --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. So it's quiet, not silent silent. 🍓

• --no-pager — disable the pager. No pager, just output. Periodt.
• --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. TOML girlies rise. 💜

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

---

Okay bestie, that's the whole page. Footer sign-off: the source/version line says path, the manual is jj-config-path(1), and there's no date shown on this page — so no date vibes, ngl. Slay and stay configed. 💅✨🫶