jj-workspace-forget(1)

💖 jj-workspace-forget 💖

okay bestie, welcome to section 1 of the general commands manual — this is jj-workspace-forget, and it's lowkey a little unhinged (affectionate) about what it does and does not touch. let's get into it 🫶

---

🌸 NAME 🌸

jj-workspace-forget — stop tracking a workspace's working-copy commit in the repo

---

✨ SYNOPSIS ✨

jj workspace forget [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] [WORKSPACES]

---

🦋 DESCRIPTION 🦋

Stop tracking a workspace's working-copy commit in the repo. that's the whole vibe. 💅

real talk: the workspace will not be touched on disk. so you can delete it from disk before or after running this command, whatever order your heart desires. no cap.

---

🎀 OPTIONS 🎀

• -h, --help — print the help, bestie (peep the summary version with just -h)
• [WORKSPACES] — the names of the workspaces you wanna forget. by default it forgets only the current workspace, so if you don't name names, it's coming for the one you're standing in 😭

---

👑 GLOBAL OPTIONS 👑

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

by default, Jujutsu goes hunting for the closest .jj/ directory in an ancestor of the current working directory. it's giving "searching for my roots" 🌈

• --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. and the working copy also gets updated at the end of the command, if the command modified the working-copy commit (@). so if you wanna avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use --ignore-working-copy. this is highkey useful, like, in a command prompt, especially if you've got another process out there committing the working copy. main character multitasking energy ✨

also: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. ikyk the pipeline 🫶

• --no-integrate-operation — run the command as usual but don't integrate any operations

when you pass this, the operations still get created as usual, but they don't get integrated into the operation log. the working copy also doesn't get updated. no integration, no commitment, it's giving situationship 😭

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. so many options, so much power 👑

note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. yeah. the push still happens. fr fr. 💀

• --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. (the root commit said "not today 💅")

this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. important distinction, don't get it twisted 🧚

• --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 there are 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. and --at-op=@ is pretty much the same as the default, except that divergent operations will never be merged. time travel but make it version control ⭐

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough. shortcuts are iconic.

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 allowed, i guess 🙈

• --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. the receipts stay, the commentary dips 🤫

warnings and errors will still be printed. safety first, always.

• --no-pager — disable the pager. no scrolling for you, bestie 💅
• --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 the string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. very flexible, very slay ✨

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

---

okay that's the whole page, drink some water 💧 and here's the lil sign-off: the footer of this page just says forget on the left and jj-workspace-forget(1) on the right — this is the general commands manual, section 1, no date, just vibes 🌈💖 go forth and forget those workspaces (the tracking, not the disk files, remember the disk files stay untouched, periodt 🫶)