Trigger RWX CI and Sandboxes from Jujutsu repos

Last year, RWX became the first CI platform to decouple running CI from making a git commit.

Since then, we've extended this capability to support longer-running sandbox tasks that agents and developers use to bi-directionally sync changes while developing remotely.

We're living through a developer tooling renaissance and increasingly, developers are exploring alternative ways to manage their code.

Today's RWX CLI release 3.27.0 adds support for working with RWX CI and Sandboxes from Jujutsu non-colocated repos - where there only exists a .jj directory:

jj git clone --no-colocate [email protected]:rwx-cloud/rwx.git && cd rwx
git status
fatal: not a git repository (or any of the parent directories): .git
rwx run ci.yml
Included a git patch for uncommitted changes

Run is watchable at https://cloud.rwx.com/rwx/runs/8698514fdb874b688fda1d9283c8b9f5

Use `rwx results --wait 8698514fdb874b688fda1d9283c8b9f5` to wait for this run to complete.

Jujutsu colocated repos - where there continues to exist both a .git and .jj directory - now use a combination of the jj and git binaries for syncing changes to RWX.

And pure git repos - where there only exists a .git directory - continue to only use the git binary.