jj-metaedit(1)

📦 version 0.46.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

💅 NAME 💅

jj-metaedit — change up a revision's metadata without touching its content. fr fr, that's the whole gig.

✨ SYNOPSIS ✨

jj metaedit [-R|--repository] [--ignore-working-copy]
[--update-change-id] [-m|--message] [--no-integrate-operation]
[--ignore-immutable] [--update-author-timestamp] [--at-operation]
[--update-author] [--author] [--debug] [--author-timestamp] [--color]
[--force-rewrite] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] [REVSETS]

🦋 DESCRIPTION 🦋

Modify the metadata of a revision without changing its content. like, glow-up the labels only, leave the actual work alone bestie 💖

Whenever any metadata gets updated, the committer name, email, and timestamp also get updated for all rebased commits. The name and email may come from the JJ_USER and JJ_EMAIL environment variables, as well as by passing --config user.name and --config user.email. so many ways to say who you are, iconic tbh ✨

🎀 OPTIONS 🎀

  • --update-change-id — Generate a new change-id.

This generates a new change-id for the revision. new identity, who dis 🙈

  • -m, --message <MESSAGE> — Update the change description.

This updates the change description, without opening the editor. no editor jumpscare, just vibes.

Use jj describe if you want to use an editor. (yes, the editor girlies have their own command 💅)

  • --update-author-timestamp — Update the author timestamp.

This updates the author date to the current time, without modifying the author. the author stays the same, only the clock moves ⏰

  • --update-author — Update the author to the configured user.

This updates the author name and email. The author timestamp is not modified — use --update-author-timestamp to update the author timestamp.

You can use it in combination with the JJ_USER and JJ_EMAIL environment variables to set a different author:

$ JJ_USER='Foo Bar' JJ_EMAIL=foo@bar.com jj metaedit
--update-author
  • --author <AUTHOR> — Set author to the provided string.

This changes author name and email while retaining author timestamp for non-discardable commits.

$ jj metaedit --author "Foo Bar <foo@bar.com>"
  • --author-timestamp <AUTHOR_TIMESTAMP> — Set the author date to the given date.

The date can either be human readable ([RFC2822], eg 'Sun, 23 Jan 2000 01:23:45 PST') or a time stamp ([RFC3339], eg '2000-01-23T01:23:45-08:00').

[RFC2822]: https://datatracker.ietf.org/doc/html/rfc2822

[RFC3339]: https://datatracker.ietf.org/doc/html/rfc3339

  • --force-rewrite — Rewrite the commit, even if no other metadata changed.

This updates the committer timestamp to the current time, as well as the committer name and email.

Even if this option is not passed, the committer name, email, and timestamp will be updated if other metadata is updated. This option just forces every commit to be rewritten whether or not there are other changes.

You can use it in combination with the JJ_USER and JJ_EMAIL environment variables to set a different committer:

$ JJ_USER='Foo Bar' JJ_EMAIL=foo@bar.com jj metaedit
--force-rewrite
  • -h, --help — Print help (see a summary with '-h'). the tiny version hits different 👑
  • [REVSETS] — The revision(s) to modify (default: @) [aliases: -r]. yep, default is just you, the main character @ 😌

🌈 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 "look upward till you find home" 🏠

  • --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. so like… it's still gonna push bestie, don't be fooled 😭
  • --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. lowkey chaotic, but possible 💀

  • --debug — Enable debug logging. the receipts, if you will 📝
  • --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. the important drama always makes it through 📢

  • --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's manual section 1, jj-metaedit(1), out of the metaedit command docs, brought to you by the Jujutsu crew in this General Commands Manual era — that footer said metaedit on the left and jj-metaedit(1) on the right, and now you know it by heart. slay, stay rebased, periodt 💖✨

📦 where this page comes from