jj-config-edit(1)

💖 jj-config-edit(1) — manual page, but make it cute 💖

🌸 NAME 🌸

jj-config-edit — start an editor on a jj config file. That's the whole vibe, bestie. 💅

---

✨ SYNOPSIS ✨

jj config edit [-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|--file>

---

🦋 DESCRIPTION 🦋

Start an editor on a jj config file. Iconic behavior, honestly. ✨

It also creates the file if it doesn't already exist, regardless of what the editor does. So yeah — the file will be there. No cap. 💖

---

🎀 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 moment. 🌸
• --file <PATH> — target the config file specified by the given path.

The path must point to a valid configuration file location recognized by Jujutsu (such as a user/repo/workspace config, a file inside a conf.d/ directory, or any file loaded via system configs, $JJ_CONFIG, or --config-file).

Unlike the global --config-file option (which loads an extra config file when running commands), this option specifies which file to inspect, edit, or modify on disk.

If the file does not exist, commands like set and edit will create it and any missing parent directories. So yes, it will manifest the file and the parent dirs. ✨

• -h, --help — print help (see a summary with '-h'). Short and sweet, iykyk. 💅

---

🌍 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 "find the repo parent energy." 🧚

• --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. Important little detail, bestie. 👑

• --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 like… be aware, okay? 💀

• --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. Facts only. ✨

• --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. Chaotic, but possible. 🌈

• --debug — enable debug logging. For when you need the lore. 🔥
• --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. Don't worry, the important stuff still shows up. 💖

• --no-pager — disable the pager. No scrolling era, just output. 🫶
• --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 girlie behavior, honestly. 🎀

• --config-file <PATH> — additional configuration files (can be repeated). Extra config files, loaded in. ✨

---

💜 footer sign-off, bestie: edit · jj-config-edit(1) — that's the footer tag and manual name given on this page; no source/version/date line was present, so I'm not inventing any fake numbers. Periodt. 🫶