That's great because we don't.
`jj undo` compared to what exactly?
In practice, it isn't. What you're identifying as potentially nightmarish - and no doubt quite tedious in git - are things that JJ enables you to do with a small subset of commands that work exactly how you expect them…
Consider using the table of contents on the left of the page to view "Real World Workflows", "Branching, Merging, and Conflicts", and then "Sharing Your Code with Others" and then evaluate how JJ does things against…
From your "polluted" snapshot, you can run `jj commit -i` and use the TUI to select only what you want.
That's great because we don't.
`jj undo` compared to what exactly?
In practice, it isn't. What you're identifying as potentially nightmarish - and no doubt quite tedious in git - are things that JJ enables you to do with a small subset of commands that work exactly how you expect them…
Consider using the table of contents on the left of the page to view "Real World Workflows", "Branching, Merging, and Conflicts", and then "Sharing Your Code with Others" and then evaluate how JJ does things against…
From your "polluted" snapshot, you can run `jj commit -i` and use the TUI to select only what you want.