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"'`

#jj-vcs

RE: https://bsky.app/profile/did:plc:insbupaifkwqqhuzffblowym/post/3lrzkmy2jfs2x

@chiborg if they form a linear sequence, rebase --update-refs can be a worthy addition. Git-replay is also a built in command with low documentation + polish but more flexible. Unfortunately replay didn't support commit signatures last time I tried it.

This kind of toil was also a huge motivator for my adopting #jjvcs which I felt handled this scenario wonderfully, and it's Git-compatible, so if you'd like to hear more about that one just holler.

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

Decided to work with #jjvcs on a small project to get to know it. So far so enjoyable 🙂

So excited to hear about ersc.io #jj-vcs

East River Source Control

#jj-vcs 0.30.0 is out! github.com/jj-vcs/jj/re...

Release v0.30.0 · jj-vcs/jj

blog.tangled.sh/stacking @oppi.li wrote a great post on stacking (and reviewing!) pull requests using #jj-vcs on tangled!

jujutsu on tangled

i'm finding that the #jj-vcs squash workflow works well with claude code. the repl-style development means that checking just the part of the diff from the current step is easier; this could be emulated in git with more commits + squash at the end, of course

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 on my machine -- it's marked private so jj won't let me push it -- so that it'll use my local copy of moxxmpp so I can develop it too; the third Parent Commit is the "actual" commit I'm working on, and where I'll squash my changes from the Working Copy once I'm done with them (and figuring out what, exactly, I changed/fixed...).

¹ This specific commit is a small override to StartTlsNegotiator to say it's okay to skip it on localhost (for testing & development). My last push to this branch includes that commit.

#jjvcs #jj-vcs

RE: infosec.town/notes/a8dotda7f37m9hsl

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

Any #jj-vcs fans have suggestions for Noah?

RE: https://bsky.app/profile/did:plc:qbidoe2gpkfelnurqod37ikr/post/3lq62rat6zc26

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

Configuring #jj-vcs oppi.li/posts/config...

Configuring Jujutsu

gm tanglers, we have got an assortment of updates for y'all! first up: native support for stacked PRs with #jj-vcs! what this means: - you can break down that mega PR into smaller ones - reviewers can review/comment/merge each one individually - ✨nobody is blocked✨

oh hey martin is talking about #jj-vcs right now www.youtube.com/watch?v=vJDB...

GerritMeets - May 2025 - Sunn...

do you love #jj-vcs? fill out this survey for jjcon 2025 github.com/jj-vcs/jj/di...

jjcon 2025 prospective attende...

I'm a #jjvcs convert, after only a few weeks of using it. If you are already proficient at git, it will be a joy to use.

I started with https://steveklabnik.github.io/jujutsu-tutorial/introduction/introduction.html which puts you in the right mindset.

Then keep trying it on a git-based project, colocated so you can use both jj and git in it. Use jj in the simplest possible modes. Then at some point soon it will "click" and your be fluent in it.
For me the killer feature is never having to worry about a rebase ever again.

#jj-vcs is the best

RE: https://bsky.app/profile/did:plc:qfpnj4og54vl56wngdriaxug/post/3lotgdvwv322c