well, you can do jj new <revision>, make your edit, and then do jj squash which will add the changes to the prev revision
replyi do this for example when i want to see a specific edit highlighted in my editor, it's a nice workflow i think
This is exactly how someone explained Git to me 12 years ago or so, and I’ve finally wrapped my head around it. Not changing now.
replyIf I'm understanding the thread correctly, I have a git alias to `git commit --amend --no-edit`, for exactly this workflow. When I'm hacking on something locally and want to just keep amending a commit. I only ever do this if it's HEAD though.
replyYes, one way to think about jj in a sort of low-level way is that every jj command does the equivalent of that, every time.
reply(You can also set up watchman and have that happen on every file change...)
[flagged]
replyI go back and forth between the two approaches, but because of the whole "accidentally made some temporary changes and now it's a pain to separate/undo them because not all changes were temporary", I also usually do a jj new and then jj squash.
replystill use new, and then squash your changes in. that way you can actually see what changes you made
replythen you `new` & `squash` :)
reply