Is jj essentially a local-only frontend for git?

[lalinsky]

I was excited when I found out about jj, however the excitement dropped once I realized that all the important bits needed to work with the changes are not stored in git. So I can't work with others based on change IDs. Once I push the bookmark, the changes become regular git commits and are only mapped to change IDs in my local .jj folder, is that correct? Is it intended to be used as a local-only tool?

[jennings]

Jujutsu now writes a header change-id into the commit so if you fetch it into another jj repo, it will have the same change ID. The evolog and operation log are not transferred, though.

It also helps see the divergence if you amend a change and it is also modified on the remote.

[TuringTrails]

I also think it would better to be able to push and pull such that atleast the evolog is preserved, to ensure effective collaboration and backup.

[sohanglal]

Yes this will truly amplify jj based workflows

[lalinsky]

Yep, being able to push the evolog into a branch associated with the change would make this tool vastly more useful.

[bleonard252]

I wonder if i.e. having special support for it in Tangled would be possible?