jj-sparse-list(1)

✨ jj-sparse-list ✨

okay bestie, welcome to jj-sparse-list(1) — yes that's the manual page name, and yes you're gonna be fluent in it by the time we're done 💅

---

🌸 NAME 🌸

jj-sparse-list — lists the patterns that are currently present in the working copy 🫶

---

📜 SYNOPSIS 📜

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

---

💖 DESCRIPTION 💖

So like. It lists the patterns that are currently present in the working copy. That's the whole gig. That's her job. 👑

By default, a newly cloned or initialized repo will have a pattern matching all files from the repo root. And that pattern gets rendered as . — literally just a single period. nobody panic. it's correct. 🌈

---

🎀 OPTIONS 🎀

• -h, --help — print help (and if you want the lil summary version, hit -h) ✨

---

👑 GLOBAL OPTIONS 👑

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

By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. she goes looking for her people.

• --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 that's automatic, no you don't have to do anything.

• --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. 💀

• --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 does not, periodt.

• --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. shortcuts are iconic, we love them.

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. (possible ≠ advisable, iykyk 🌸)

• --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. those ones are not getting silenced, nope.

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

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

---

and that's the whole page, bestie!! this one came from the list source, filed under the jj-sparse-list(1) manual — go forth and list your sparse patterns, you absolute main character 💜🦋✨