Post

jj is cool, but the base CLI seems more like a "workflow development kit" than an actual workflow people use. it is great for this - it exposes very powerful primitives! I just don't see it becoming the industry standard without more established bright line workflows

0 reposts5 likes

primitives like changes as documents, automatic rebasing, good options for manual rebasing, conflict management. all good stuff, and I will continue using it.

this is based on my limited experience using it for a classic GitHub pull request workflow with named bookmarks, so ymmv. please tell me what I'm missing / cool stuff that will change my experience with it!

- Create tracked bookmark in one command - Commit and update bookmark - Rebase children of updated bookmark (maintain my cthulu merge commit) Basically I want bookmarks to act more like a bundle of changes. Granted, I'm coming at this with git brain

`jj next` feels like mercurial and makes it much easier to tinker/amend a chain of commits as they're reviewed need I say more about `jj undo`