Jujutsu v0.38.0
https://github.com/jj-vcs/jj/releases/tag/v0.38.0
Release highlights:
- Per-repo and per-workspace config is now stored outside the repo, for security reasons. This is not a breaking change because legacy repos are automatically migrated to this new format. `.jj/repo/config.toml` and `.jj/workspace-config.toml` should no longer be used.
I'm really glad I moved over to Jujutsu VCS (from Git). The idea of anonymous branches was a bit of a head scratcher at first but now I don't think I could go back to without. It makes experimentation and exploration of code changes so much simpler. #jujutsuvcs #programming
Jujutsu v0.37.0
https://github.com/jj-vcs/jj/releases/tag/v0.37.0
Release highlights:
- A new syntax for referring to hidden and divergent change IDs is available: xyz/n where n is a number. For instance, xyz/0 refers to the latest version of xyz, while xyz/1 refers to the previous version of xyz. This allows you to perform actions like jj restore --from xyz/1 --to xyz to restore xyz to its previous contents, if you made a mistake.
Jujutsu v0.36.0
https://github.com/jj-vcs/jj/releases/tag/v0.36.0
Release highlights:
- The documentation has moved from https://jj-vcs.github.io/jj/ to
https://docs.jj-vcs.dev/.
- It is now safe to
continuously run e.g. jj log without --ignore-working-copy in one
terminal while you're running other commands in another terminal.
- jj now ignores $PAGER set in the environment and uses less -FRX on most
platforms (:builtin on Windows).
Tiens, j’avais raté, Korben a écrit un petit article de présentation de Jujutsu.
Il a bien raison de dire que « vos collègues peuvent continuer avec Git classique sans même savoir que vous utilisez jj ».
Par contre, la référence à Google dès le titre peut rebuter. À la base c’est un projet perso de Martin von Zweigbergk, qui est maintenant payé à plein temps par Google pour développer son idée.
https://korben.info/jj-jujutsu-version-control-alternative.html
@AugierLe42e J'utilise de plus en plus `jj` par-dessus git, et le `jj undo` est miraculeux !
J'apprécie de plus en plus cet outil (il demande aussi un peu d'adaptation, mais je retrouve une UX à la mercurial qui est tellement plus simple).
#jujutsuvcs
Here’s a nice little workflow that’s possible with #jujutsuvcs but not #git: I can create future empty TODO commits as reminders to implement some logic
If you haven't tried it yet, I definitely recommend checking Jujutsu Version Control System.
I literally heard about it two days ago, started reading through some tutorials, and already feel like this is something exciting and new in the VCS world. You can use it locally on any git repository you already have, since it uses git as the backend.
Anyone else in the team can keep on using git, and if you feel like it you can switch back to use git at any time.
`jj` feels intuitive, and makes rebasing less of a hassle; actually there is no hassle! How many times have you done `git rebase --abort`, when you're halfway through fixing the conflicts using git rebase? I have quite many times. I hate it.
With jj it's no problem, it won't stop you to fix your conflicts, but lets you continue your work, and fix the conflicts later. And when you do that, it automatically rebases the fix to the child changes. It also lets you do any changes anywhere in the history. If you feel like some change is better to be done in another commit, you can just insert the commit after/before another, and squash the changes. Then continue working as usual.
This is yet another rabbit-hole for me, and I love it! Of course, I still need to use it in my day-to-day work, and I'll probably be going back to the tutorials, and asking stupid questions, but I have a feeling it'll be all right.
Here's a couple of resources I've been reading through:
https://steveklabnik.github.io/jujutsu-tutorial/
https://zerowidth.com/2025/what-ive-learned-from-jj/
Ooooooh! First #JujutsuVCS integration in @kaleidoscope.app dropped in their 6.1 release! #jj
Ooooooh! First #JujutsuVCS integration into @KaleidoscopeApp dropped in their 6.1 release!#jj
For the tiny overlap between the circles that are “people who use BBEdit” and “people who use #jjVCS”: syntax highlighting for #JujutsuVCS commit messages in BBEdit! 🎉 https://github.com/chriskrycho/bbedit-jj-syntax
For the tiny overlap between the circles that are “people who use BBEdit” and “people who use #jjVCS”: syntax highlighting for #JujutsuVCS commit messages in BBEdit! 🎉 github.com/chriskrycho/...
GitHub - chriskrycho/bbedit-jj...
Toying with the idea of trying #jj for Spades. I don't really work on a team, but I still try to not break things for other people nonetheless (like links). The key is I want my Git commit messages in Codeberg to remain clean, readable, and conventional, and I want to not break links (but have them point to the most relevant whatever). I'm very used to Git, so learning a new workflow isn't really appealing.
With Git my biggest frustration is having to force-push all the time (and also how you can only get so minute with staging diffs), and since that's because the commit chain is different, the links don't update to refer to the rebased version of that commit (which I guess is fine, but tracking them and providing a link at the top would be nice). Maybe jj kinda has a better system with change-ids but it doesn't play nice with Git web UIs like Forgejo.
Another Git frustration is just how rebasing works in general, which does tie in to the rest. Conflict resolution for me is fine, though I know this is something jj specializes in.
One thing that I really like so far reading about jj is that it has me write the commit message before committing, so that while I'm coding, that guides me. I'm not sure what the jj solution is for when I make various other changes in the pursuit of whatever end goal (fixing bugs I encountered while trying to diagnose another, for example). I'll occasionally go back and want to use those commit messages to find where I made what change, so those need to have commit messages associated with them.
#jj-vcs #jj_vcs #jjvcs #jujutsuvcs #git
Forcing myself to unfuck some commits with Jujutsu and slowly getting the hang of it.
The "reverse commit" workflow I have is feeling like I have to be more deliberate and focused with my changes, which I see as a good thing - I often pull too many things apart at once. (Don't let me near your home electronics, the putting back together is not my stronger side)
Integrating jj-fzf into Emacs
https://testbit.eu/2025/jj-fzf-in-emacs
“Built on jj and fzf, jj-fzf offers a text-based user interface (TUI) that simplifies complex versioning control operations like rebasing, squashing, and merging commits. This post will guide you through integrating jj-fzf into your Emacs workflow, allowing to switch between emacs and jj-fzf with a simple key combination.”
JJ-FZF 0.25.0: Major New Features
https://testbit.eu/2025/jj-fzf-0.25.0
“For the uninitiated, jj-fzf is a feature-rich command-line tool that integrates jj and fzf, offering fast commit navigation with previews and very quick commit history manipulation through keybindings.”
I wrote this up in a slightly longer blog post to show off a few cool examples, including describing all the commits on top of trunk with no description, or all the commits which touch a given file, and so on: https://v5.chriskrycho.com/notes/jj-tip-describe-multiple-revisions-at-once/
Another great #JujutsuVCS trick I learned this morning: you can use #jj squash with a revset and a fileset to move changes out of a whole set of commits into another commit. 🤯 https://v5.chriskrycho.com/notes/jj-tip-squash-changes-from-across-a-revset/
I used the JJ version control utility (aka jujutsu) a lot in the last couple of weeks. I really like some parts of it. It has some fresh ideas, but some of it does not fit my normal git workflow. Having "git add --patch" and using bash completion for git add is something I use daily. But I could get used to this.
However, the big showstopper for me is jj's lack of support for git submodules that I heavily rely on. All of my vagrant test setups use them, for example.
The good news is that support is being worked on. Looking forward to this...
An introduction to #JujutsuVCS (From a Git user's perspective), by @chriskrycho
https://www.youtube.com/watch?v=2otjrTzRfVk
This video would be even better with a sequel😉.
(Note : “jj obslog” is now called “jj evolog”.)
