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

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!

it’s possible jj is missing stuff! what higher-level workflows do feel yourself wanting?

- 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

What's weird is it feels so *close* to working well. If you set the bookmark to an empty change at the end of a branch, and you could do something like `jj new --before bookmark-name`, cthulu workflow works automatically But `jj git push` refuses to push the bookmark pointing at an empty change