Jujutsu (jj)

“Everything I do is basically the same as with branches, just that I get randomly generated tip names rather than naming them myself”

“one advantage of using the same storage on disk as Git and exposing it in the same way is that git-based tools still work”

“One of the other features I use quite heavily is that, in JJ, you can essentially check out multiple branches at the same time”

“hardly worth using more of the precious LLM context with jj instructions when git does the job and is mandatory anyways”

“The ability to undo anything with the one 'jj undo' command is awesome in the agent coding world when it makes a mistake.”

“this fact does not diminish the usefulness of Jujutsu. There are valid use cases for the rebase and stacking operations”

“Only difference my teammates see is that my commits are much tidier and scoped in a way that's easy to review and think about.”

“it's easier if you give up choosing the name of your branch, and instead rely on finding things by description or your workspace name.”

“can't fathom for the life of me why i have to run another command that updates the branch to the next commit”

“Having to list all the bookmarks you would list to auto-advance in your jj config.toml is a hassle and easy to forget.”

“jj does not require you to resolve merge conflicts in a timely manner; it simply records the fact that there are conflicts in the file”

“jj allows concentrating on developing while leaving things for vcs alone, as well as solving vcs things (conflicts) at very beginning”

“Almost everyone I've shown jj to at work has converted because it solves the same problems for them as it did for myself.”

“to the extent that you would never bother doing half the things with git that you can do with Jujutsu because it's such a pain”

“Turns out these two differences combined with tracking change identity over multiple snapshots allow for ergonomic workflows”

“Probably my favourite thing that has really changed my workflow is being able to write empty commits in advance then just switch between them.”

“Great tool. Roughly this workflow is how I convinced a few friends to finally loosen their death grip on git and try something new.”

“`jj undo` and the jj architecture generally make it difficult for agents to screw something up in a way that cannot be recovered.”

“That sounds a bit faffy. With jj you have to fetch, start new space off a bookmark, edit code, commit it, update the bookmark and finally push?”

“There's one thing that's a bit annoying, the commit is there but the head of the branch hasn't been moved, you have to move it manually”

“the working tree being a commit has wide ranging implications as all the commands that work with commits start working with the working tree by default”

“jj undo and the jj architecture generally make it difficult for agents to screw something up in a way that cannot be recovered.”

“JJ can save conflict related state with the change so that you don't need to resolve a conflict in the middle of a stack of changes”

“Deferred conflict resolution is amazing in jj because I may never return to some of the branches that are in conflict”

“already supports 3-way merges and history-preserving rebases, and does so with data structures that are trivially representable in a standard git repo”

“jj represents a massive step forward from git in terms of usability, usefulness, and solving problems I actually have”

“it turns out to be really useful not to be stuck inside an aberrant state while conflicts are in the process of being resolved”

“It is just dozens and dozens of small quality of life improvements that culminate in a significantly better overall experience.”

“That inability to push the really useful jj state upstream for pulling from any machine seems like a major pain point in jj right now”

“We are using jj with great success but tools like auto claude are designed around git and git worktrees.”

“Only unfortunate thing with jujutsu is because it is trying to be a git overlay, you lose state that a mercurial clone on another machine would have.”

“This is the post that made jj click for me, and not coincidentally it is about a rebase operation that feels complicated in git but trivial in jj.”

“it's mostly a bunch of small things that jj does nicer, that cumulatively add up to a significantly nicer experience”

“jj doesn't force you to resolve the conflicts immediately, so it'll just show that they're conflicted until you decide you want to go fix them.”

“The descendant commits (E through J) then get automatically rebased and the feature bookmarks/branches get updated.”

“I think jj is generally more useful for people like me who often have lots of independent and dependent work in progress.”

“automatic rebasing, i.e. that all descendant commits and bookmarks (branches) are automatically updated when you rewrite a commit”

“I tried it once co-locating with Git and you definitely can't use both at the same time, even if it can use a `.git` directory.”

“bookmarks don't float, unlike git branches, so if your pattern is to produce a lot of commits, you'll want something to keep your jj bookmarks pointing to the top”

“jj's interaction model makes these things simple, straightforward, and obvious in the overwhelming majority of cases.”