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!

Alyssa the Kate

@alyssa.codes

`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`

14/8/26, 9:26 pm0 reposts2 likes

Tyler Mandry

@tmandry.dev

14 Aug

Maybe my problem is I never used mercurial? I'd missed `jj next` (and `jj prev`); thanks for that!

Alyssa the Kate

@alyssa.codes

14 Aug

You're welcome! Fig at Google (a mercurial wrapper around Piper) really changed how I think about VCS and chains of commits. `hg evolve` and everything around it (like prev/next) is just...so much better than fixup commits and interactive rebase