The absorb command will do a lot of this for you by identifying which downstream mutable commit each line or hunk of your current commit belong in and automatically squashing them down for you. I. Did. Not. Know. This. I have been using this today because I have a Claude Skill I'm building and a feature upon which I'm testing it. Using the jj new <feature-change> <skill-change> I can make this "megamerge" commit, and all day I've been working on that change and jj absorb has magically pushed all the changes to the skill to the right tree and all the changes to the feature to it's tree. Another example! I'm working on a blog rewrite, and I'm keeping the "posts" from the old blog out of it for a bit, but I have a change where I've imported them all. Before, I'd work like this: I'd keep a change with all the posts, develop on top, use jj arrange to place it behind the to-be-abandoned post change, and then advance the bookmark. ❯ jj @ ykrxvkkm evantravers@gmail.com 2026-04-22 09:08:32…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.