I see. For now, I'd use github actions, or a vm manager like UTM. We usually don't need to generate other-platform binaries as often as local builds. Certainly, it's not as easy as with Go or Zig, but I do it all the time.
Oh and one more thing I forgot: in git a lot of operations require you to have a clean checkout. Otherwise you have to stash your changes first before doing that operation. With jujutsu’s model, there is no stashing. Every edit is already part of a commit. Therefore you can totally do rebases even when you are in the middle of some other unrelated change.
You can turn that off (I do). In your config file:
[snapshot]
auto-track = "none()"
Auto-tracking could be a great default in certain projects, and a terrible one in others. jj doesn't require it at all and is still awesome without it.
Bonus tips:
# show help by default, as the subcommands do
[ui]
default-command = "-h"
# more readable log (also affects jjui)
[templates]
log = 'builtin_log_oneline'
Mine do. The phone's lightning connector socket has become "flaky" (from age, or lint..), and at this point I must hold the phone in hand rather than in pocket while walking, for uninterrupted playback.
Why is that ?
reply