jj-tag-track(1)

πŸ“¦ version 0.46.0, in arch rolling, nixpkgs unstable, ubuntu stonking

✨ NAME ✨

okay so bestie, welcome to jj-tag-track (that's jj-tag-track(1) in full manual-page format, mwah) β€” this is the one that starts tracking given remote tags. that's the whole vibe. let's get into it 🫢


🌸 SYNOPSIS 🌸

jj tag track [-R|--repository] [--remote] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <TAG[@REMOTE]>

like yes, that's a lot of brackets. it's giving options girlie. we'll go through every single one, don't even worry πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

Start tracking given remote tags. that's it, that's the job ✨

here's the tea tho: a tracked remote tag will be imported as a local tag of the same name. and then β€” and this is the good part β€” changes to it will propagate to the existing local tag on future pulls. so it stays in sync. iconic behaviour honestly πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • --remote <REMOTE> β€” remote names to track πŸ’…

by default, the specified pattern matches remote names with glob syntax. but you're not locked in, bestie β€” you can also use other [string pattern syntax].

and if you give no remote names at all, then all remote tags matching the tag names will be tracked. generous queen 🌈

[string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

  • -h, --help β€” prints help, but if you pass just -h you get the summary version. the full thing is for the girlies who want the whole story πŸ“–
  • <TAG[@REMOTE]> β€” tag name patterns or remote tag symbols to track ⭐

TAG matches tag names using glob syntax by default, and yep, you can also use other [string pattern syntax].

TAG@REMOTE β€” this one resolves to a remote tag exactly. no globbing, no guessing, just precision πŸ’…

[string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

these are the big-league ones, the ones that work across jj. buckle up 🧚

  • -R, --repository <REPOSITORY> β€” path to the repository to operate on 🌸

by default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. so it just... finds your repo for you. main character energy tbh.

  • --ignore-working-copy β€” don't snapshot the working copy, and don't update it πŸ™ˆ

so normally 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 (@).

but if you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you use --ignore-working-copy. this may be useful like, e.g. in a command prompt β€” especially if you have another process that commits the working copy. so like, multi-process girlies, this one's for you πŸ’œ

also important: 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. so many doors opened for you fr fr πŸšͺ✨

⚠️ note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. no cap, that push is happening.
  • --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.

and listen carefully: this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. so 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 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.

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.

also: 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. so like... you can, but why would you 😭

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

warnings and errors will still be printed. safety first 🫢

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

  • --config-file <PATH> β€” additional configuration files (can be repeated) πŸ”

and that's the whole page, bestie!! you officially know jj-tag-track inside and out and i'm so proud of you πŸ₯ΉπŸ’–

this was brought to you by the track section of the manual, jj-tag-track(1). go forth and track those tags, queen πŸ‘‘πŸ’…βœ¨
πŸ“¦ where this page comes from