[caconym_]

I think people who grasp the basic idea of a commit graph and approach it in terms of "this is how I want to manipulate the graph, what are the tools that will allow me to do this?" find it easy, and people who approach it in terms of building a cookbook of commands that comprise a workflow don't.

[stouset]

I am somebody who deeply cares about my commit graph. I want to maintain clean history, and I want to regularly amend previous commits (until merged) in order to tell a coherent story about development. I want to keep unrelated commits on separate branches, so they can be reviewed and merged independently.

I understand how to do these things, but git’s interaction model makes it tedious at best and hard at worst.

jj’s interaction model makes these things simple, straightforward, and obvious in the overwhelming majority of cases.