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

Tyler Mandry

@tmandry.dev

14 Aug

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

Tyler Mandry

@tmandry.dev

14 Aug

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!

david barsky

@davidbarsky.com

14 Aug

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

Tyler Mandry

@tmandry.dev

14 Aug

- 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

Tyler Mandry

@tmandry.dev

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

14/8/26, 10:56 pm0 reposts1 like

Tyler Mandry

@tmandry.dev

15 Aug

In short, I want `jj git push` to ignore trailing empty commits and push the parent instead. I would make this the recommended way to use named branch workflows with multiple commits in a PR Adding a change to a branch becomes `jj new -B branchname`

Tyler Mandry

@tmandry.dev

14 Aug

Like, if empty changes are The Way (or at least A Way), why does my workflow now involve managing a bunch of off-by-one errors?