jj-gerrit

jj gerrit command [options]jj gerrit upload [options]

jj gerrit talks to a Gerrit Code Review instance over a Git remote. The only subcommand is upload, which creates one Gerrit change for each selected revision (and its mutable ancestors). Re-uploading a revision that already carries the same Change-Id adds a new patch set instead of opening a new change.Jujutsu tracks a stable change identity across rewrites, and Gerrit tracks the same logical change through the Change-Id trailer. The two identifiers are not natively the same; jj gerrit upload bridges them by adding a Gerrit-style Change-Id derived from the Jujutsu change ID when the commit has none. That trailer is added only on the uploaded commit, so the Gerrit commit ID can differ from the local one.After review feedback, edit the revisions and run jj gerrit upload again with the same revsets. Keep the original Jujutsu change (and its Change-Id) when splitting or squashing so Gerrit continues to update the existing review.

upload

Upload changes to Gerrit for code review, or update existing changes that share the same Change-Id.

Revisions to upload. All mutable ancestors of the specified revisions are also pushed, so -r foo is equivalent to -r `mutable()::foo`. If omitted, @ is uploaded when it has a description, otherwise @-.

Destination branch on the Gerrit remote. Default: gerrit.default-remote-branch.

Git remote or full SSH URL to push to. Default: gerrit.default-remote, otherwise a remote named gerrit.

Show what would change on the remote without pushing.

Add this address as a reviewer (repeatable).

CC this address on the change (repeatable).

Set a Gerrit label (repeatable). A suffix such as +2 sets the value; default is +1. Gerrit silently ignores labels that are not configured on the host.

Group the change under a Gerrit topic. Gerrit can be configured to submit every change in a topic together.

Attach a freeform hashtag (repeatable). Unlike topics, hashtags are informational only.

Description for the uploaded patch set.

Push as a change edit on an existing Gerrit change. Edits must be published from the web UI; a new edit replaces the previous one.

Mark the change as work in progress.

Mark the change as ready for review.

Mark or unmark the change as private.

Publish or withhold draft comments. --no-publish-comments is useful when the account is configured to publish comments by default.

Who receives email: none, owner, owner-reviewers, or all (default).

Submit the changes immediately, bypassing code review.

With --submit, skip Gerrit validations.

Create a new change even if the change has already been merged.

Do not modify the Gerrit attention set.

Abort the push after this deadline.

Send a custom keyed value to Gerrit (repeatable).

Pass a `git push -o` option (repeatable).

Enable Gerrit upload tracing for debugging.

Set the default remote and destination branch in user or repo config:

$ [gerrit]
default-remote = "gerrit"
default-remote-branch = "main"

$ [templates]
commit_trailers = '''
if(
  !trailers.contains_key("Change-Id"),
  format_gerrit_change_id_trailer(self)
)
'''

Subcommand of jj. The Gerrit remote must already exist (`jj git remote add`, clone, or `jj git init` in a Git repo that already has one). If gerrit.default-remote is unset and no remote named gerrit exists, the upload fails until you pass --remote or set the default.Because auto-generated Change-Id trailers live only on the uploaded commit, fetching a merged change can produce a divergent local revision. Abandon the local change or rebase onto trunk with `jj rebase --skip-emptied ...`. Configuring commit_trailers as above avoids that mismatch. Duplicate Change-Id values across different changes are rejected by Gerrit (or can overwrite an existing change if uploaded separately).

jj gerrit is part of Jujutsu. Gerrit and Jujutsu share a change-identity model (Gerrit's Change-Id vs jj's change ID), which is why upload maps each jj change onto a single Gerrit review.

jj(1), jj-git(1), jj-git-push(1), jj-git-remote(1), git-push(1)

Source code · Homepage · Documentation