#jujutsuvcs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jujutsuvcs, aggregated by home.social.
-
Finally rebased some branches for #BitRitter (thanks jujutsu) to get translations and XDG spec working.
When i have inserted all strings, i will tag another release.Would have given me headaches with plain git.
Nextvon the list is (still) flatpak bundling, then 2 minor issues.
-
Jujutsu v0.41.0
https://github.com/jj-vcs/jj/releases/tag/v0.41.0Release highlights:
* `jj fix` now supports formatting specific line ranges (allowing you to format
only modified lines); see the configuration manual and notes below for more.
* The new global flag `--no-integrate-operation` will let you run a command without impacting the repo state or the working copy, which is useful when automated tools may create snapshots in the background. -
Jujutsu v0.39.0
https://github.com/jj-vcs/jj/releases/tag/v0.39.0Release highlights:
* `jj arrange` command brings up a TUI where you can reorder and abandon revisions.
* `jj bookmark advance` automatically moves bookmarks forward to a target revision (defaults to @) using customization points revsets.bookmark-advance-from and revsets.bookmark-advance-to. It is heavily inspired by the longstanding community alias jj tug. -
Jujutsu is just nice to work with.
I do not often have to do complex rebasing/merging/squashing work, but i can always undo. Don't worry chfkch, it will be okay.
-
Jujutsu PSA:
Running `jj st` ¹ may change the state of your repository, even though it looks like it should be a read-only command. Consider the following steps:
1. Create a file xyz in your repository
2. Run `jj st`
3. Add xyz to .gitignoreIf you omit step 2., the outcome changes. Namely, `jj st` causes file xyz to be tracked, and it keeps being tracked even after you have added it to .gitignore. If you don't run `jj st`, xyz is ignored, as you would probably expect.
Caused me a headache today 😅
¹ And probably other commands which you would expect to be read-only
-
Jujutsu v0.38.0
https://github.com/jj-vcs/jj/releases/tag/v0.38.0Release 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.0Release 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.0Release 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
-
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 -
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 -
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 -
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 -
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 -
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/
-
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: v5.chriskrycho.com/notes/jj-tip... #jjVCS #jujutsuVCS #jj
RE: https://bsky.app/profile/did:plc:i55fkgcwrczbj7edpucwl5mz/post/3lgdrwiugbk2s
jj tip: describe multiple revi... -
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. 🤯 *Super* handy when you want to split out changes into multiple PRs. v5.chriskrycho.com/notes/jj-ti...
jj tip: Squash Changes From Ac... -
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=2otjrTzRfVkThis video would be even better with a sequel😉.
(Note : “jj obslog” is now called “jj evolog”.)
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
I’m calling it now: this is the year a bunch of you are going to switch to using #JujutsuVCS, because it’s awesome. I’m going to keep doing my best to make #jj happen—hopefully lots more posts/videos/etc.
Some of you are hacking on side projects on vacation. Try it out! https://jj-vcs.github.io/jj/latest/
-
I’m calling it now: this is the year a bunch of you are going to switch to using #JujutsuVCS, because it’s awesome. I’m going to keep doing my best to make #jj happen—hopefully lots more posts/videos/etc. Some of you are hacking on side projects on vacation. Try it out! jj-vcs.github.io/jj/latest/
Jujutsu docs -
I wrote yesterday a bit about how deferred conflict resolution works in #JujutsuVCS – a thing that leaves a lot of new #jj users (including me when I first started!) asking, “Wait, why would I even want that?!? Isn’t that *worse*?” Spoilers: actually it’s better! v5.chriskrycho.com/journal/def...
Deferred Conflict Resolution i... -
I wrote yesterday a bit about how deferred conflict resolution works in #JujutsuVCS – a thing that leaves a lot of new #jj users (including me when I first started!) asking, “Wait, why would I even want that?!? Isn’t that *worse*?” Spoilers: actually it’s better! https://v5.chriskrycho.com/journal/deferred-conflict-resolution-in-jujutsu/
-
I wrote about why all the posts about #JujutsuVCS are all differences from Git, and how this relates to a more general issue when talking about new tools/ideas/etc. v5.chriskrycho.com/notes/why-t...
Why the Jujutsu posts are all ...