Design to support Jujutsu as a Gerrit client

[Edwin Kempin]

Hi,

The Jujutsu project agreed with GitButler to standardize on storing change ID's as a Git commit header called change-id where the change ID is a 32 character reverse-hex ID (e.g. `mlqnqnkrxpuvuuxzlzoltostwlwyskpx`). The change ID's are reverse-hex ID's so that they can be easily distinguished from commit SHA1's. The Jujutsu team reached out to us, the Gerrit Code Review project, to see whether we can support these kind of change ID's too.

The result of the discussions that happened on Discord were summarized in a design doc that outlines how we can support Jujutsu as a Gerrit client (see https://gerrit-review.googlesource.com/c/homepage/+/464287 and follow-up changes in https://gerrit-review.googlesource.com/c/homepage/+/465461).

If the design gets accepted, the Gerrit team at Google considers implementing this in Q3. I'm sharing this here for broader visibility. Please raise any concerns by commenting on the changes.

Jujutsu is a version control system that allows to track and publish changes to the code. The workflows to craft changes in Jujutsu look very compatible with Gerrit (e.g check this video tutorial). In particular, they identify changes and reviews by a change ID, which looks conceptually similar to the Gerrit Change-Id. Supporting Jujutsu change ID's can eliminate the need to install the commit-msg hook which is a constant source of confusion, at least for new Gerrit users.

Jujutsu is gaining traction and support from developers, hence it makes sense for Gerrit to support Jujutsu as a client. Long-term Jujutsu may become the primary (command-line) client for Gerrit, as it seems easier to use than native Git.

Edwin

[Daniele Sassoli]

Hi Edwin,

On Monday, 7 April 2025 at 14:24:02 UTC+1 eke...@google.com wrote:

Hi,

The Jujutsu project agreed with GitButler to standardize on storing change ID's as a Git commit header called change-id where the change ID is a 32 character reverse-hex ID (e.g. `mlqnqnkrxpuvuuxzlzoltostwlwyskpx`). The change ID's are reverse-hex ID's so that they can be easily distinguished from commit SHA1's. The Jujutsu team reached out to us, the Gerrit Code Review project, to see whether we can support these kind of change ID's too.

The result of the discussions that happened on Discord were summarized in a design doc that outlines how we can support Jujutsu as a Gerrit client (see https://gerrit-review.googlesource.com/c/homepage/+/464287 and follow-up changes in https://gerrit-review.googlesource.com/c/homepage/+/465461).

If the design gets accepted, the Gerrit team at Google considers implementing this in Q3. I'm sharing this here for broader visibility. Please raise any concerns by commenting on the changes.

 

Exciting times, would be great if Gerrit supported JuJutsu natively.