#jjvcs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jjvcs, aggregated by home.social.
-
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. -
okay you #jjvcs nerds. talk to me - if I wanted to start from the bottom as a Git user; where do I start?
-
An update on @[email protected] availability #jj-vcs ersc.io/blog/ersc-av...
An update on ERSC availability... -
“That moment when you realize that a tool simply fixes all the UI issues that you had and that you have been developing for the last 20 years was not exactly great." lwn.net/Articles/105... I’m glad git is leaning from #jj-vcs
RE: https://bsky.app/profile/did:plc:gttrfs4hfmrclyxvwkwcgpj7/post/3mjyyxr4oak2y
Evolving Git for the next deca... -
Version 0.40 is out! Go get your monthly fix of new #jj-vcs features at github.com/jj-vcs/jj/re...
Release v0.40.0 · jj-vcs/jj -
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. -
So Jujutsu now has a `jj b a` command.
Focusing on the otaku market, I see
#jjVCS -
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. -
hey everyone please welcome #jj-vcs to bluesky :)
RE: https://bsky.app/profile/did:plc:r7xcwfouzmwigjxjobxo7y4k/post/3me2rv6ycjc2j -
jj absorbis amazingIf you haven't tried out Jujutsu VCS yet, I strongly recommend giving it a go. IMO, the best time to try it out is when you have some really difficult Git conflicts to navigate -- you can import everything into jj and try resolving them from there. I've introduced friends to it when they were stuck like this, and it's when jj shines the most.
-
@jnunemaker trying it now. I would much prefer `jj` integration, but I can work with Git. Under #jjvcs, I frequently rewrite commits, and now I feel limited. I also forgot much of my #Git experience because before jj, I was using #sapling. I think I haven't used git in day-to-day since 2-3 years ago!
Anyway, submitted a couple of feedback items to the Conductor team. We'll see how it evolves. I too am finding #conductor productive at the moment.
-
I'm going to be at @[email protected] ! Giving a talk about #jj-vcs www.tokioconf.com/speakers Hope to see you there!
Meet the Speakers — TokioConf ... -
What I *really* want is the stuff the good folks at https://ersc.io are cooking up for #jjvcs, but that’ll have to wait a bit longer yet.
-
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. -
#jj-vcs 0.37.0 came out yesterday! im intrigued by the new divergent change syntax, seems very neat github.com/jj-vcs/jj/re...
Release v0.37.0 · jj-vcs/jj -
-
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). -
"why i think #jj-vcs is worth your time" schpet.com/note/why-i-t...
why i think jj-vcs is worth yo... -
#jj-vcs 0.36.0 us out! Including finally moving the documentation to our own domain, docs.jj-vcs.dev github.com/jj-vcs/jj/re...
Release v0.36.0 · jj-vcs/jj -
From Zero to GitHub: Starting A New #jj-vcs Repo www.visualmode.dev/from-zero-to...
From Zero to GitHub: Starting ... -
-
-
One that I was particularly interested in: #jj-vcs at google www.youtube.com/watch?v=v9Ob...
JJ Con • JJ at Google -
All of the videos from the first #jj-vcs conference are out! www.youtube.com/playlist?lis...
JJ Con 2025 - YouTube -
-
Any other #jj-vcs fans have thoughts/advice here?
RE: https://bsky.app/profile/did:plc:dsmywy3zgfhcsjobdrhe52zx/post/3m444xmwwgc2w -
Maybe restarting the #jjvcs tutorial on my new #freebsd install will kill 3 birds with one stone: jj, freebsd, rust , my lazyvim.
4, 4 birds with one stone!
Wait, i'll start again....
#nobodyexpectsit -
Maybe restarting the #jjvcs tutorial on my new #freebsd install will kill 3 birds with one stone: jj, freebsd, rust , my lazyvim.
4, 4 birds with one stone!
Wait, i'll start again....
#nobodyexpectsit -
Maybe restarting the #jjvcs tutorial on my new #freebsd install will kill 3 birds with one stone: jj, freebsd, rust , my lazyvim.
4, 4 birds with one stone!
Wait, i'll start again....
#nobodyexpectsit -
Maybe restarting the #jjvcs tutorial on my new #freebsd install will kill 3 birds with one stone: jj, freebsd, rust , my lazyvim.
4, 4 birds with one stone!
Wait, i'll start again....
#nobodyexpectsit -
Maybe restarting the #jjvcs tutorial on my new #freebsd install will kill 3 birds with one stone: jj, freebsd, rust , my lazyvim.
4, 4 birds with one stone!
Wait, i'll start again....
#nobodyexpectsit -
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 -
@steveklabnik.com yes, I experienced this as well. Not as many commits beyond the conflict, but I find conflict resolution in #jjvcs to be superior to #sapling.
On the other hand, I much prefer Sapling's GitHub integration than jj's. Sapling maintains the PR title and description from the first commit's message when `sl push`, and I really liked that.
-
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...
