#jjvcs mention in www.youtube.com/watch?v=f3u5... (it isn't all about Jujutsu)

So Jujutsu now has a `jj b a` command.

Focusing on the otaku market, I see
#jjVCS

The good part: I'm slowly starting to understand the bits of jj.
The bad part: I'm still not sure what was the hype about it.
#jjvcs

What I *really* want is the stuff the good folks at ersc.io are cooking up for #jjvcs, but that’ll have to wait a bit longer yet.

introducing spindle tangled's new CI runner is now generally available

And #tangled has a #nix based ci system. Which also supports #jjvcs... How have I not learned of this before!? I think I'm going to have run this thing for a while. Too much to learn alone. 😅

Jujutsu Version Control: Change Basics When using Jujutsu you spend a lot of time working with changes. A change in a Jujutsu repository involves the following steps: Create a new change. Make changes to your project. Describe the change. Creating a Change #Run the jj new command to create a change. jj new After creating a change, you can make changes in your project, such as adding, editing, and removing code.

The following article covers the basics of working with changes in Jujutsu repos:

https://www.meandmark.com/posts/jj-changes/

#jjVCS

Jujutsu Version Control: Repositories In this article, you will learn how to create a Jujutsu repository, view the contents of a repository, and view the current repository status. Creating a Jujutsu Repository #To use Jujutsu you must create a repository to track the files in your project. Run the jj git init command to create a repository. Currently Jujutsu uses git as the backend for repos so you have to include git in the command.

The following article shows how to work with Jujutsu version control repositories:

https://www.meandmark.com/posts/jj-repos/

#jj-vcs

Jujutsu Version Control: Setup This article is the first in a series of articles introducing the Jujutsu version control system. This article covers the following topics involved with setting up Jujutsu: Installing Jujutsu Setting the author for commits Setting the text editor to use for commit messages Installing Jujutsu #The first step to using Jujutsu is to install it. The Jujutsu documentation lists ways to install Jujutsu.

I started writing some articles introducing the Jujutsu version control system. The first article covers setup.

https://www.meandmark.com/posts/jj-setup/

#jj-vcs

jj seriously saved my bacon today by allowing me to recover the individual commits from a squash-merged PR.

A single commit in that PR introduced a weird bug and I would’ve had to manually recreate and test each change from scratch if not for jj!

#jjvcs #jj-vcs

The Next Generation of Version Control The current state of affairs with version control is a mess. Things we can get right next time around.

I’m nothing if not consistent. I was reading through old posts on an archived version of my blog and found this old gem in which I laid out my views on 2014-era VCS options, and basically begged for someone to build #jjVCS. 😂 v4.chriskrycho.com/2014/next-ge...

Command to get a list of tags from #jjVCS in reverse chronological order (recent first):

`jj log -r 'tags()' --no-graph -T 'commit_timestamp(self).local().format("%Y-%m-%d") ++ " " ++ tags.map(|t| t.name()).join(", ") ++ "\n"'`

GitHub - chriskrycho/bbedit-jj-syntax Contribute to chriskrycho/bbedit-jj-syntax development by creating an account on GitHub.

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/...

Here's where #jj starts getting quite powerful: this is a "merge commit" with its own contents (the Working Copy), merging from three other commits: the first Parent Commit is the tip of the xmpp-sdk branch¹; the second Parent Commit overrides dependencies just […]

[Original post on infosec.town]

What I’ve learned from jj Comments

This is, by far, the best and most comprehensive, single overview of various aspects of #jj that I’ve come to understand and appreciate as part of my workflow

https://zerowidth.com/2025/what-ive-learned-from-jj/

#jjvcs

Original post on infosec.town

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 […]

I'm so ridiculously happy with the bash completion improvements landing in #jjVCS 0.29

Original post on hachyderm.io

OK, so in case of divergent changes in #jjVCS (i.e. two sources disagree on the current state of a change ID), you're supposed to use the commit ID to disambiguate. So commit IDs must be unique.

If you're like me, you'd wonder if it isn't also possible for multiple changes to refer to the same […]

Original post on hachyderm.io

I'm finally giving #jj-vcs a try. Things are going great, and the only thing more magical than automatic rebasing is resolving conflicts in changes that aren't even checked out.

The conflict markers threw me off on the first day, but now I see they are far superior to zdiff3 style for solving […]

Open Source Summit North America 2025: Call for Papers CHOOSE ONE (1) TRACKOpen Source Summit North America is an umbrella event for open source projects and developer communities to come together under on...

Just submitted a session on #jjVCS to Open Source Summit North America 2025—it’s right in my back yard and I couldn’t resist the chance to try to get more people talking about Jujutsu. They’re still taking submissions for the next 10 days—would love to see you there! sessionize.com/open-source-...

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

#jjVCS 🤯 moment: `jj desc` takes a revset. That means you can, for example, launch an editor to describe *all* the changes between your repo’s “trunk” and your current commit at the same time by writing `jj desc -r "trunk()..@"`.