this post was submitted on 02 Aug 2025
29 points (87.2% liked)

Programming

21924 readers
648 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

“Jujutsu (jj) is a version control system with a significantly simplified mental model and command-line interface compared to Git, without sacrificing expressibility or power (in fact, you could argue Jujutsu is more powerful). Stacked-diff workflows, seamless rebases, and ephemeral revisions are all natural with jj [...]”

Part 2 of the series is out and is here.

you are viewing a single comment's thread
view the rest of the comments
[–] HaraldvonBlauzahn@feddit.org 0 points 10 hours ago* (last edited 10 hours ago)

I can see that - but that's a "less frequent" task than me switching between branches.

My observation is that one happens to edit the commit graph much more often because it is so effortless.

And the analogous thing to switching a branch is:

jj

to get the log. And then, with say "qx" being the abbreviated commit id I want to append the next change to:

jj new qx

and now I am already working at the right series of changes.

Because I like a lot to focus on one single thing, the next thing I do is often

 jj desc

which opens $EDITOR with the commit description and lets me write down what I am going to add or change.

That commit description also shows up in the log command, so I know always what the change is about.