3 ms·
Yeah, my solution to this problem has been to get Claude to use jj to create a clean commit history. Each commit serves a single purpose and includes what drove
by ncphillips 16d ago
Yeah, my solution to this problem has been to get Claude to use jj to create a clean commit history. Each commit serves a single purpose and includes what drove the decisions we made. You lose the noise and still have the meaning.
So I'm a little unclear as to benefit of this. It sounds...wasteful?
- anamexis 15d agoWhat does jj specifically enable for that workflow?
- ncphillips 15d agoIt drastically simplifies the process. Redescribe, reorder, split, squash, abandon commits is trivial. Auto-rebasing is fantastic, fix a conflict once and not have to keep correcting. You can rebase individual commits, ranges of commits, etc. You can also rebase trees I.e. forking branches with a common ancestor, with a single command. The operation log also makes it feel super safe. You can always undo a jj operation or restore to a past state