jj-tag-list(1)

📦
version 0.46.0 · 3 versions
, in arch rolling, nixpkgs unstable

✨ NAME ✨

jj-tag-list(1) — List tags and their targets 💖

okay so this is the glow-up of jj-tag-list(1) from the General Commands Manual, and it's literally here to help you see tags and what they point at. bestie, it's giving "small command, very useful receipts." 🎀

🌸 SYNOPSIS 🌸

jj tag list [-a|--all-remotes] [-R|--repository] [--ignore-working-copy]
[--remote] [--no-integrate-operation] [-t|--tracked] [-c|--conflicted]
[--ignore-immutable] [--at-operation] [-r|--revision] [--debug]
[-T|--template] [--color] [--sort] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help] [NAMES]

🦋 DESCRIPTION 🦋

okay so the whole point: list tags and their targets. no cap, that's the main-character job. 💅

Default behavior, bestie:

  • By default, a tracked remote tag will be included only if its target is different from the local tag.
  • An untracked remote tag won't be listed.
  • For a conflicted tag (both local and remote), old target revisions are preceded by a - and new target revisions are preceded by a +.

The -r flag combined with revset expressions can be used for filtering. For example:

  • jj tag list -r 'REV::' shows tags whose targets are descendants of REV (similar to git tag --contains REV).
  • jj tag list -r '::REV' shows tags whose targets are ancestors of REV (similar to git tag --merged REV).

💅 OPTIONS 💅

  • -a, --all-remotes — Show all tracked and untracked remote tags including the ones whose targets are synchronized with the local tags. ✨
  • --remote <REMOTE> — Show all tracked and untracked remote tags belonging to this remote.
    • Can be combined with --tracked or --conflicted to filter the tags shown (can be repeated.)
    • By default, the specified pattern matches remote names with glob syntax. You can also use other [string pattern syntax].
    • [string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns
  • -t, --tracked — Show tracked remote tags only.
    • This omits local Git-tracking tags by default.
  • -c, --conflicted — Show conflicted tags only. 🫶
  • -r, --revision <REVSETS> — Show tags whose local targets are in the given revisions.
    • Note that -r deleted_tag will not work since deleted_tag wouldn't have a local target.
  • -T, --template <TEMPLATE> — Render each tag using the given template.
  • --sort <SORT_KEY> — Sort tags based on the given key (or multiple keys).
    • Suffix the key with - to sort in descending order of the value (e.g. --sort name-). Note that when using multiple keys, the first key is the most significant.
    • This defaults to the ui.tag-list-sort-keys setting.
    • Possible values:
      • name
      • name-
      • author-name
      • author-name-
      • author-email
      • author-email-
      • author-date
      • author-date-
      • committer-name
      • committer-name-
      • committer-email
      • committer-email-
      • committer-date
      • committer-date-
  • -h, --help — Print help (see a summary with '-h'). 🎀
  • [NAMES] — Show tags whose local name matches.

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

later, bestie — source says list, page is jj-tag-list(1), and the original footer has no date so I'm not inventing one 🫶✨

📦 where this page comes from