News for hackers. Stuff that matters.
Re:Jujutsu Primer by dwattttt on Friday November 20, 2026 @03:54AM (#50571973)
I have a good story around these features.

At the start of the day, I resumed working on a feature; there's no staging, so modifications I make are all stored as the current change.

Later that day I realised I needed to actually save the version of the feature that existed at the start of the morning.

So into the evolog I go (`jj evolog`). It's a record of all commits that a change has been; I could scroll back through the recorded changes, find the first change made that day, and then 'jj new' to create a change that represents that work.

It felt magical, to just be able to jump back to a project state that I didn't explicitly record, then save it.

Re:Jujutsu Primer by zaphirplane on Friday November 20, 2026 @06:43AM (#50573360)
[delayed]
Re:Jujutsu Primer by thek3nger on Friday November 20, 2026 @06:58AM (#50573512)
The evolog doesn’t track explicit commits. It is a list of snapshots of the codebase. JJ creates a new snapshot every time you run a command (or edit a file, depending on how you configure it).
Re:Jujutsu Primer by y1n0 on Friday November 20, 2026 @09:46AM (#50575367)
[delayed]
Re:Jujutsu Primer by BeetleB on Friday November 20, 2026 @10:28AM (#50576107)
Yes, but without having to tell it to branch off.

One of the nice things about jj is you don't need to name a branch. You're just working on a graph. When you think you have something consistent and would like to give a name to it, you can do it (before or after the fact). But the lack of friction in creating a temporary new branch is amazing.

If you used VCS before git and loved how easy branching is in git, this is the same feeling in jj, but now with git being the old, tedious way.

Re:Jujutsu Primer by skydhash on Friday November 20, 2026 @10:40AM (#50576354)
> One of the nice things about jj is you don't need to name a branch.

Maybe it's due to different thinking process. But I can't think of doing a branch without knowing why I would need to do it, which also give me a quick indication of how I should name it. Everything is local anyway so I don't complicate stuff.

Re:Jujutsu Primer by steveklabnik on Friday November 20, 2026 @12:24PM (#50578409)
You see the description of changes in your log, and so that's often good enough as a name. No need to give it a second one. Here's an example from a project of mine:

    │ ○  lrvwrmqv [email protected] 2026-09-07 22:13:12 977b1ab7
    │ │  harden running image identity fixtures
    │ ○  vqmsmkup [email protected] 2026-09-07 22:13:12 bcd98591
    ├─╯  add running compiler image identity
    ◆  mxvotmyz [email protected] 2026-09-07 21:53:55 trunk e37a132e
    │  satisfy the byte recovery Clippy gate
It's nicer with color. Anyway, this is an anonymous branch, with two changes on it. "add running compiler image identity" and "harden running image identity fixtures" let me know what that branch is about, without needing to add an extra name onto the branch itself.