←back to thread

I see a future in jj

(steveklabnik.com)
325 points steveklabnik | 1 comments | 22 Oct 25 17:21 UTC | HN request time: 0s | source
Show context
mh9r ◴[22 Oct 25 20:40 UTC] No.45674870[source]▶
I tried Jujutsu in the last day and was going through your tutorial. I really liked the experience and can see some potential. I also got the feeling that there is a missing puzzle piece. For example, do I get any benefit from the change id if I push to GitHub for PR review?

I guess you benefit from some of the good parts only with the Google internal Piper backend, at the moment. So I’m curious about the ideas and plans you have at ERSC.

But what I’m also really yearning for is having a distributed asynchronous/offline-first code review flow built right in. The distributed nature of git somehow got lost with PRs or MRs in GitHub & Co.

replies(2): >>45674962 #>>45678405 #
1. CGamesPlay ◴[23 Oct 25 05:22 UTC] No.45678405[source]▶
One thing to note is that the actual commit objects you make through jj do include a `change-id` header which means that even though Github is unaware of jj, peers using jj will still be able to keep track of the rebases.

Demo: run `git cat-file -p HEAD` in any jj repository that you've made a change to.